From: Axel S. <Axe...@en...> - 2008-05-17 09:02:30
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On May 17, 2008, at 10:28, Joachim Breitner wrote: > Tracing back this file was generated by this call: > $ gcc -x c glib/System/Glib/GTypeConstants_hsc_make.c -o > glib/System/Glib/GTypeConstants_hsc_make.s -v -S -Wimplicit -O > -D__GLASGOW_HASKELL__=608 -DNO_REGS -DUSE_MINIINTERPRETER -Wall -g -O2 > -include gtk2hs-config.h -I /usr/include/glib-2.0 > -I /usr/lib/glib-2.0/include > -I /usr/lib/ghc-6.8.2/lib/base-3.0.1.0/include > -I /usr/lib/ghc-6.8.2/include > > With the attached .c file as input, which is rather small. Compiling > this program directly with gcc, using the command line > $ gcc glib/System/Glib/GTypeConstants_hsc_make.c -o /tmp/make -v > -Wimplicit -O -D__GLASGOW_HASKELL__=608 -DNO_REGS - > DUSE_MINIINTERPRETER > -Wall -g -O2 -include gtk2hs-config.h -I /usr/include/glib-2.0 > -I /usr/lib/glib-2.0/include > -I /usr/lib/ghc-6.8.2/lib/base-3.0.1.0/include > -I /usr/lib/ghc-6.8.2/include > You also don't pass the -x c flag in the manual invocation. I think this might be more of a culprit. The -x c flag tells the CPP preprocessor that the input is C which is wrong since it's assembler and the preprocessor shouldn't be run (or should it?). Can you add -v to the former invocation to see what's happening? We use this flag since otherwise the CPP preprocessor is in a very ambitious mode when pre-processing Haskell files and it falls over. The -g flag tells the compiler to include debug information. I'm amazed that this should have an effect when on calling the assembler. Axel. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFILp8YA+OhltVdZ9oRAjJqAJ9UHRur9k0udv3BI+/qqojDZtamKwCeIkeP XINoHc2qb6VaDxMUQzRoZrk= =89X4 -----END PGP SIGNATURE----- |