[MacPorts] #31689: Boost 1.47 won't compile

MacPorts noreply at macports.org
Thu Oct 20 04:54:48 PDT 2011


#31689: Boost 1.47 won't compile
-------------------------------------+--------------------------------------
 Reporter:  akim.demaille@…          |       Owner:  macports-tickets@…                   
     Type:  defect                   |      Status:  new                                  
 Priority:  Normal                   |   Milestone:                                       
Component:  ports                    |     Version:  2.0.3                                
 Keywords:                           |        Port:  Boost                                
-------------------------------------+--------------------------------------
 On neither this machine (Lion), nor the other at work (Snow Leopard) the
 Boost 1.47 package manages to complete its compilation.  Actually, it
 doesn't even finish its bootstrap:

 {{{
 akim at padam ..ts_devel_boost/boost/work/boost_1_47_0 $ pwd
 13:50:18
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_boost/boost/work/boost_1_47_0
 akim at padam ..ts_devel_boost/boost/work/boost_1_47_0 $ cat bootstrap.log
 13:50:21
 ###
 ### Using 'darwin' toolset.
 ###
 rm -rf bootstrap
 mkdir bootstrap
 /Developer/usr/bin/llvm-gcc-4.2 -o bootstrap/jam0 command.c compile.c
 debug.c expand.c glob.c hash.c hdrmacro.c headers.c jam.c jambase.c
 jamgram.c lists.c make.c make1.c newstr.c option.c output.c parse.c
 pathunix.c pathvms.c regexp.c rules.c scan.c search.c subst.c timestamp.c
 variable.c modules.c strings.c filesys.c builtins.c pwd.c class.c native.c
 md5.c w32_getreg.c modules/set.c modules/path.c modules/regex.c modules
 /property-set.c modules/sequence.c modules/order.c execunix.c fileunix.c
 expand.c: In function ‘var_expand’:
 expand.c:85: warning: field precision should have type ‘int’, but argument
 2 has type ‘long int’
 expand.c:85: warning: field precision should have type ‘int’, but argument
 2 has type ‘long int’
 fileunix.c: In function ‘file_archscan’:
 fileunix.c:300: error: ‘struct ar_hdr’ has no member named ‘ar_fmag’
 fileunix.c:316: error: ‘struct ar_hdr’ has no member named ‘ar_name’
 fileunix.c:316: error: ‘struct ar_hdr’ has no member named ‘ar_name’
 fileunix.c:316: error: ‘struct ar_hdr’ has no member named ‘ar_name’
 fileunix.c:316: error: ‘struct ar_hdr’ has no member named ‘ar_name’
 fileunix.c:318: error: ‘struct ar_hdr’ has no member named ‘ar_date’
 fileunix.c:319: error: ‘struct ar_hdr’ has no member named ‘ar_size’
 fileunix.c:321: error: ‘struct ar_hdr’ has no member named ‘ar_name’
 fileunix.c:323: error: ‘struct ar_hdr’ has no member named ‘ar_name’
 fileunix.c:335: error: ‘struct ar_hdr’ has no member named ‘ar_name’
 }}}

 I had not looked into the details on the SL machine, of course the error
 can be different.

 Cheers!

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


More information about the macports-tickets mailing list