qt4-mac: internal compiler error

[thomas.weiss@…]

updating via $ sudo port -uc upgrade outdated returned "Error: Target org.macports.build returned: shell command failed" as requested by Michael Dickens <michaelld@…> I#m filing this ticket.

I'm using Mac OS 10.6.4, Xcode 3.2.3 (1688) 64-bit.

Thanks for the help!

[thomas.weiss@…]

Cropped qt4-mac buildlog. The original is 10MB.

[ryandesign (Ryan Carsten Schmidt)]

OK, looks like the relevant error is:

:info:build qdbuscpp2xml.cpp: In function 'int main(int, char**)':
:info:build qdbuscpp2xml.cpp:370: internal compiler error: in get_expr_operands, at tree-ssa-operands.c:2093
:info:build Please submit a full bug report,
:info:build with preprocessed source if appropriate.
:info:build See <URL:http://developer.apple.com/bugreporter> for instructions.
:info:build make[3]: *** [.obj/release-shared/qdbuscpp2xml.o] Error 1
:info:build make[2]: *** [sub-qdbuscpp2xml-make_default] Error 2

I have not seen that error before, and I am also running Mac OS X 10.6.4 on a 64-bit Mac with Xcode 3.2.3.

There was a previous report of an internal compiler error with qt4-mac in #22082 which was closed before any particular resolution was reached.

[michaelld (Michael Dickens)]

Hmm ... I'm using 10.5 i386 on a MacBook Pro. I've never had a compiler internal error before & I do a -lot- of programming for a variety of projects including MacPorts. Suggestions:

1. If you do the upgrade again (without cleaning), does it give the same error?

2. Using the debug output, can you go into the correct build directory & recreate the error by hand? If so, can you have gcc/g++ keep temporary files. Might be useful to parse through those even though it'll be painful (yes, I will do it if you attach them to this ticket).

3. If you do "clean" then "upgrade", do you get the error again?

4. If you deactivate the current qt4-mac, "clean" the upgrade, and then "install" do you again get the error?

I'm going to go ahead and checkin the changes to qt4-mac*; maybe that will help.

[thomas.weiss@…]

Strange. I started with the upgrade again and even after the error the update went on and it seems qt4-mac 4.6.3_5 is installed. Unfortunately the process cleaned the logs right after install, so I can't give you information on the second error. As I run KILE right now, I think my qt4-mac is operating. This ticket can be closed. Thanks for your help.

$ sudo port -uc upgrade outdated
Password:
--->  Computing dependencies for libpixman
--->  Fetching libpixman
--->  Attempting to fetch pixman-0.18.4.tar.bz2 from http://lil.fr.distfiles.macports.org/libpixman
--->  Verifying checksum(s) for libpixman
--->  Extracting libpixman
--->  Configuring libpixman
--->  Building libpixman
--->  Staging libpixman into destroot
--->  Computing dependencies for libpixman
--->  Installing libpixman @0.18.4_0
--->  Deactivating libpixman @0.18.2_0
--->  Cleaning libpixman
--->  Activating libpixman @0.18.4_0
--->  Cleaning libpixman
--->  Uninstalling libpixman @0.18.2_0
--->  Cleaning libpixman
--->  Computing dependencies for qt4-mac
--->  Building qt4-mac
--->  Staging qt4-mac into destroot
--->  Computing dependencies for qt4-mac
--->  Installing qt4-mac @4.6.3_5
Error: Target org.macports.deactivate returned: shell command failed
Log for qt4-mac is at: /opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_qt4-mac_4.6.3_4/main.log
Warning: Failed to execute portfile from registry for qt4-mac @4.6.3_4
--->  Deactivating qt4-mac @4.6.3_4
--->  Activating qt4-mac @4.6.3_5
--->  Cleaning qt4-mac
--->  Uninstalling qt4-mac @4.6.3_4
--->  Cleaning qt4-mac

$ port installed qt4-mac
The following ports are currently installed:
  qt4-mac @4.6.3_5 (active)

[michaelld (Michael Dickens)]

You're welcome, and I'm glad it worked for you; thanks for reporting back.