Opened 11 years ago
Closed 11 years ago
#40385 closed defect (duplicate)
boost +universal: build failure on Leopard x86
Reported by: | lubodiakov@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.2.0 |
Keywords: | Cc: | cooljeanius (Eric Gallager), mdbecque@… | |
Port: | boost |
Description (last modified by larryv (Lawrence Velázquez))
I attempted to run:
sudo port install boost +universal
It managed to install some of the dependencies like icu, but then crashed and burned.
---> Configuring boost ---> Building boost Error: org.macports.build for port boost returned: command execution failed To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port boost failed
Reran with: sudo port install -d boost +universal
I'm attaching the main.log (/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_boost/boost/main.log)
Attachments (3)
Change History (10)
comment:1 Changed 11 years ago by larryv (Lawrence Velázquez)
Description: | modified (diff) |
---|---|
Keywords: | universal removed |
Summary: | boost universal variant fails to compile on Leopard x86 → boost +universal: build failure on Leopard x86 |
Changed 11 years ago by lubodiakov@…
Log of sudo port install -d boost +universal on Leopard x86
comment:4 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Your log says:
:info:build Performing configuration checks :info:build :info:build - has_icu builds : no :info:build warning: Graph library does not contain MPI-based parallel components. :info:build note: to enable them, add "using mpi ;" to your user-config.jam :info:build - zlib : no :info:build - iconv (libc) : no :info:build - iconv (separate) : no :info:build - icu : no :info:build - icu (lib64) : no :info:build - Boost.Locale needs either iconv or ICU library to be built. :info:build - Boost.Locale needs either iconv or ICU library to be built. :info:build - Boost.Locale needs either iconv or ICU library to be built. :info:build - Boost.Locale needs either iconv or ICU library to be built. :info:build - Boost.Locale needs either iconv or ICU library to be built. :info:build - Boost.Locale needs either iconv or ICU library to be built. :info:build - gcc visibility : no :info:build - long double support : no :info:build - zlib : no :info:build - Boost.Locale needs either iconv or ICU library to be built. :info:build - Boost.Locale needs either iconv or ICU library to be built. :info:build - Boost.Locale needs either iconv or ICU library to be built. :info:build - Boost.Locale needs either iconv or ICU library to be built. :info:build - Boost.Locale needs either iconv or ICU library to be built. :info:build - Boost.Locale needs either iconv or ICU library to be built.
On my Leopard i386 system without the universal variant I have:
Performing configuration checks - has_icu builds : yes warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam - zlib : yes - iconv (libc) : no - iconv (separate) : yes - icu : yes - compiler-supports-ssse3 : no - compiler-supports-avx2 : no - gcc visibility : yes - long double support : yes - zlib : yes
I'll try with the universal variant after all the dependencies finish upgrading to universal.
Why do you need universal anyway? Do you really need to run this software on both an Intel Mac and on a PowerPC Mac?
comment:5 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
With universal it still says:
Performing configuration checks - has_icu builds : yes warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam - zlib : yes - iconv (libc) : no - iconv (separate) : yes - icu : yes - compiler-supports-ssse3 : no - compiler-supports-avx2 : no - gcc visibility : yes - long double support : yes - zlib : yes
So something is wrong on your system that's causing boost to not find any of its dependencies. We need to figure out what that is. Autotools-based configuration systems record that information in a file called config.log, but boost does not use autotools and I don't know where it records this information, if indeed it does at all.
Changed 11 years ago by mdbecque@…
boost log: configure failure: command execution failed, on leopard ppc
Changed 11 years ago by mdbecque@…
Attachment: | bootstrap.log added |
---|
comment:7 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Duplicate of #39809.
This log is incomplete.
As per the Guide, please clean, try again, and reattach the new main.log.