[MacPorts] #26538: Failed at building Boost

[MacPorts]

#26538: Failed at building Boost
--------------------------------+-------------------------------------------
 Reporter:  raramayo@…          |       Owner:  macports-tickets@…                   
     Type:  defect              |      Status:  new                                  
 Priority:  Normal              |   Milestone:                                       
Component:  ports               |     Version:  1.9.1                                
 Keywords:                      |        Port:                                       
--------------------------------+-------------------------------------------

Comment(by raramayo@…):

 Replying to [comment:4 ryandesign@…]:
 > The relevant error from the main.log might be:
 > {{{
 > :info:build ldld:: in in libinkscape.a , libinkscape.afile,  too
 filesmall
 > :info:build too small
 > }}}
 > That's the parallel build encountering the same error twice and
 intermingling the responses. If we clean that up, it should read:
 > {{{
 > :info:build ld: in libinkscape.a, file too small
 > :info:build ld: in libinkscape.a, file too small
 > }}}
 > What version of Xcode is installed? If you have a very old version of
 Xcode (i.e. earlier than the earliest supported by Snow Leopard, which is
 3.2), that might account for the very strange behavior you're seeing.
 [http://developer.apple.com/technologies/xcode.html The current version is
 3.2.4]. If you have less, you should upgrade.

 I have version 3.2.3. And I am using a "fresh" installation of 10.6.4.
 Now, very importantly, I installed the system using NetBoot. This is, I
 configured a computer, made a carboncopy cloner copy and then used my
 server to create a netrestore image of the hard disk. This is the only
 thing different from other MacPorts installation I made before.

 >
 > Is your hard disk ok? Run Disk Utility and verify the disk.

 OH Yes, my disks are OK and I run DK on them routinely

 >
 > It might be helpful if we would stop mixing problems from several
 different machines in one bug report, since you seem to be having
 different problems on each machine and we'll likely have to tackle each of
 them separately.

 I agree and I apologize. I have never seen MacPorts act like this
 before....

-- 
Ticket URL: <https://trac.macports.org/ticket/26538#comment:5>
MacPorts <http://www.macports.org/>
Ports system for Mac OS