Opened 13 years ago

Closed 13 years ago

#33620 closed defect (duplicate)

Boost 1.49 Configure fails during "sudo port upgrade outdated" stopping process cold

Reported by: cc70458@… Owned by: adfernandes (Andrew Fernandes)
Priority: Normal Milestone:
Component: ports Version: 2.0.4
Keywords: Cc:
Port: boost

Description (last modified by skymoo (Adam Mercer))

Gentlepersons (and violent persons too...),

I find myself unable to do an update outdated, or update boost, individual packages can be done individually but I cannot locate the root cause for the sudden error. I even tried setting the xcode source and reinstalling the 10.7.3 update just in case. Stil no joy on this particular issue. I have attached all the relevant information I could think of below.

Thank you in advance for your assistance, and the assured gentle reminder of my IQ moving in the inverse direction of my age,

Colin Corcoran cc70458@…

Screen output is as follows:

Colins-MacBook-Pro:~ cc70458$ sudo port upgrade outdated
--->  Computing dependencies for boost
--->  Fetching archive for boost
--->  Attempting to fetch boost-1.49.0_0.darwin_11.x86_64.tbz2 from http://packages.macports.org/boost
--->  Configuring boost
Error: Target org.macports.configure returned: configure failure: shell command failed (see log for details)
Log for boost is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_boost/boost/main.log
Error: Unable to upgrade port: 1
To report a bug, see <http://guide.macports.org/#project.tickets>

* Tail of ...bost/main.log:

Colins-MacBook-Pro:~ cc70458$ tail -f /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_boost/boost/main.log
:info:configure 
:info:configure Failed to build Boost.Build build engine
:info:configure Consult 'bootstrap.log' for more details
:info:configure shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_boost/boost/work/boost_1_49_0" && ./bootstrap.sh --prefix=/opt/local --without-libraries=python --without-libraries=mpi --with-icu=/opt/local " returned error 1
:error:configure Target org.macports.configure returned: configure failure: shell command failed (see log for details)
:debug:configure Backtrace: configure failure: shell command failed (see log for details)
    while executing
"$procedure $targetname"
:info:configure Warning: the following items did not execute (for boost): org.macports.install org.macports.configure org.macports.build org.macports.destroot
:notice:configure Log for boost is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_boost/boost/main.log

Tail of ....boost_1_49_0/bootstrap.log:

Colins-MacBook-Pro:~ cc70458$ tail -f /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_boost/boost/work/boost_1_49_0/bootstrap.log
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’

Change History (3)

comment:1 Changed 13 years ago by cc70458@…

Cc: cc70458@… added

Cc Me!

comment:2 Changed 13 years ago by skymoo (Adam Mercer)

Cc: cc70458@… removed
Description: modified (diff)
Owner: changed from macports-tickets@… to adfernandes@…
Port: boost added

comment:3 Changed 13 years ago by adfernandes (Andrew Fernandes)

Resolution: duplicate
Status: newclosed

This crops up every once in a while.

The problem is the go port (see #30203 and #31689, for example). The go port installs a header it shouldn't in A Bad Place.

The solution is to either uninstall go, deactivate it, or (possibly) upgrade the go port to the latest; I think the problem is fixed in the latest go port.

Note: See TracTickets for help on using tickets.