Opened 10 years ago

Closed 9 years ago

#36611 closed defect (fixed)

libstdcxx fails to build

Reported by: roffe@… Owned by: mww@…
Priority: Normal Milestone:
Component: ports Version: 2.1.2
Keywords: Cc: jeremyhu (Jeremy Huddleston Sequoia), udbraumann
Port: libstdcxx

Description (last modified by ryandesign (Ryan Schmidt))

--->  Computing dependencies for libstdcxx
--->  Building libstdcxx
Error: org.macports.build for port libstdcxx returned: command execution failed
Please see the log file for port libstdcxx for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc47/libstdcxx/main.log
Error: Unable to upgrade port: 1
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets

Attachments (5)

main.log (89.6 KB) - added by ryandesign (Ryan Schmidt) 10 years ago.
roffe's main.log
main.2.log (19.7 MB) - added by roffe@… 10 years ago.
Log from clean build as per request.
main_gcc40.log (5.7 MB) - added by udbraumann 10 years ago.
main_gcc45.log (606.0 KB) - added by udbraumann 10 years ago.
config.log (15.1 KB) - added by udbraumann 10 years ago.
this config.log corresponds to the main.log of the gcc45 compiler run

Change History (19)

comment:1 Changed 10 years ago by ryandesign (Ryan Schmidt)

Cc: jeremyhu@… added
Description: modified (diff)
Owner: changed from macports-tickets@… to mww@…
Port: libstdcxx added

Please remember to use WikiFormatting, to fill in the Port field, and to Cc the maintainer of that port so that they see your ticket.

Huge output like a main.log is best attached not pasted. I've converted your paste into an attachment.

Your log is not from a clean attempt. Please run "sudo port clean libstdcxx", then try again, and attach the new main.log if it fails again. If it is large you may want to compress it before attaching it.

Changed 10 years ago by ryandesign (Ryan Schmidt)

Attachment: main.log added

roffe's main.log

comment:2 Changed 10 years ago by jeremyhu (Jeremy Huddleston Sequoia)

:info:build warning: gcc/cc1-checksum.o differs
:info:build warning: gcc/cc1plus-checksum.o differs
:info:build Bootstrap comparison failure!
:info:build x86_64-apple-darwin12/libstdc++-v3/libsupc++/vec.o differs
:info:build make[2]: *** [compare] Error 1

Changed 10 years ago by roffe@…

Attachment: main.2.log added

Log from clean build as per request.

Changed 10 years ago by udbraumann

Attachment: main_gcc40.log added

comment:3 Changed 10 years ago by udbraumann

I got a similar error on a 10.5.8 PPC using gcc4.0, see the few snipped lines below and my attachment main_gcc4.0.log

info:build warning: gcc/cc1-checksum.o differs
:info:build warning: gcc/cc1plus-checksum.o differs
:info:build Bootstrap comparison failure!
:info:build gcc/host-darwin.o differs
:info:build make[2]: *** [compare] Error 1

comment:4 Changed 10 years ago by udbraumann

After specifying a newer compiler on my 10.5.8 PPC, other errors could be seen (see below and the attachment main_gcc45.log):

info:build checking for suffix of object files... configure: error: in `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc47/libstdcxx/work/build/ppc-apple-darwin9/libgcc':
:info:build configure: error: cannot compute suffix of object files: cannot compile
:info:build See `config.log' for more details.
:info:build make[2]: *** [configure-stage1-target-libgcc] Error 1

Changed 10 years ago by udbraumann

Attachment: main_gcc45.log added

comment:5 Changed 10 years ago by udbraumann

Cc: braumann@… added

Cc Me!

comment:6 in reply to:  1 Changed 10 years ago by udbraumann

Replying to ryandesign@…:

Please remember to use WikiFormatting, to fill in the Port field, and to Cc the maintainer of that port so that they see your ticket.

Well, guys, this defect at the moment is blocking all major updates requiring gcc45 on my system, since for some reason gcc45 relies on gcc47 now, whereas building of libstdcxx-4.7.2_2 (on my system without intervention gcc40 is taken for this, but forcing gcc42 or gcc45 does not help) unfortunately fails at the moment. I would be glad, if this "Bootstrap comparison failure" (no idea what this really means) could be verified by some others. Perhaps there is some work-around? Thanks!

comment:7 Changed 10 years ago by jeremyhu (Jeremy Huddleston Sequoia)

:info:build checking for suffix of object files... configure: error: in `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc47/libstdcxx/work/build/ppc-apple-darwin9/libgcc':
:info:build configure: error: cannot compute suffix of object files: cannot compile
:info:build See `config.log' for more details.

Look at config.log (or provide it to us) for clues about what is going wrong.

Why are you using gcc-4.0 on Leopard? You should be using gcc-4.2 by default.

Changed 10 years ago by udbraumann

Attachment: config.log added

this config.log corresponds to the main.log of the gcc45 compiler run

comment:8 in reply to:  7 Changed 10 years ago by udbraumann

Replying to jeremyhu@…:

Ok, I have uploaded the config.log as resulted from the gcc45 compiler run.

From config.log a series of problems of this type is visible: "xgcc: error: unrecognized command line option"

configure:3344: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc47/libstdcxx/work/build/./gcc/xgcc -B/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc47/libstdcxx/work/build/./gcc/ -B/opt/local/ppc-apple-darwin9/bin/ -B/opt/local/ppc-apple-darwin9/lib/ -isystem /opt/local/ppc-apple-darwin9/include -isystem /opt/local/ppc-apple-darwin9/sys-include    -V >&5
xgcc: error: unrecognized command line option '-V'
xgcc: fatal error: no input files
compilation terminated.
configure:3355: $? = 1
configure:3344: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc47/libstdcxx/work/build/./gcc/xgcc -B/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc47/libstdcxx/work/build/./gcc/ -B/opt/local/ppc-apple-darwin9/bin/ -B/opt/local/ppc-apple-darwin9/lib/ -isystem /opt/local/ppc-apple-darwin9/include -isystem /opt/local/ppc-apple-darwin9/sys-include    -qversion >&5
xgcc: error: unrecognized command line option '-qversion'
xgcc: fatal error: no input files
compilation terminated.
configure:3355: $? = 1
configure:3371: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc47/libstdcxx/work/build/./gcc/xgcc -B/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc47/libstdcxx/work/build/./gcc/ -B/opt/local/ppc-apple-darwin9/bin/ -B/opt/local/ppc-apple-darwin9/lib/ -isystem /opt/local/ppc-apple-darwin9/include -isystem /opt/local/ppc-apple-darwin9/sys-include    -o conftest -g -O2   conftest.c  >&5
xgcc: internal compiler error: Segmentation fault (program cc1)

Why are you using gcc-4.0 on Leopard? You should be using gcc-4.2 by default.

Well, I always thought the portfile should define which compiler is required. After getting in trouble with gcc40 (selected without a certain specification), using the configure.compiler option I tried various compilers installed on my 10.5.8. PPC, including apple-gcc-4.2. If you find gcc-4.2. should the preset standard compiler (for macports, or in general?), please let me know how to define this.

Thanks so far, and perhaps someone can have a look on the config,log, I hope especially the unrecognized options -V and -qversion will give someone a clue what is going wrong here.

comment:9 Changed 10 years ago by jeremyhu (Jeremy Huddleston Sequoia)

braumann, please open a new ticket for your issue as it is not related. Also, please attach the crash report.

comment:10 Changed 10 years ago by jeremyhu (Jeremy Huddleston Sequoia)

If you find gcc-4.2. should the preset standard compiler (for macports, or in general?), please let me know how to define this.

You don't do anything to define this. It is the default set by base.

comment:11 in reply to:  9 Changed 10 years ago by udbraumann

Replying to jeremyhu@…:

please open a new ticket for your issue as it is not related. Also, please attach the crash report.

I now have opened a fork in Ticket #36981: libstdcxx fails building on a 10.5.8 PPC documenting the problems using mp-gcc45

comment:12 in reply to:  7 ; Changed 10 years ago by ryandesign (Ryan Schmidt)

Replying to jeremyhu@…:

Why are you using gcc-4.0 on Leopard? You should be using gcc-4.2 by default.

gcc-4.0 is the default on Tiger and Leopard. gcc-4.2 is the default on Snow Leopard.

comment:13 in reply to:  12 Changed 10 years ago by udbraumann

Replying to ryandesign@…:

Replying to jeremyhu@…:

Why are you using gcc-4.0 on Leopard? You should be using gcc-4.2 by default.

gcc-4.0 is the default on Tiger and Leopard. gcc-4.2 is the default on Snow Leopard.

Thanks, for some presently unknown reason, now building libstdcxx works on my machine (as I already have reported in the forked Ticket #36981: libstdcxx fails building on a 10.5.8 PPC). In between the very first attempt building libstdcxx some weeks before (of course using the default gcc4.0), I only have made a disk maintenance plus have set gcc4.0 as default gcc using the select command of port. Anyway, now I no longer have these cc1-checksum.o-errors (see above). All other desperate attempts using e.g. gcc45 etc. (see above) seemingly have not been a good idea...

comment:14 Changed 9 years ago by jeremyhu (Jeremy Huddleston Sequoia)

Resolution: fixed
Status: newclosed

Ok, then closing as fixed.

Note: See TracTickets for help on using tickets.