| msg16241 - (view) |
Author: Martin Mokrejs (mmokrejs) |
Date: 2003-06-04 15:25 |
| In current cvs, -pthread and -ieee is properly set for OSF1/Tru64Unix. Unfortunately, -ieee is somewhat passed to linker: building '_curses' extension cc -pthread -DNDEBUG -O -ieee -std -Olimit 1500 -I. -I/mnt/python/dist/src/./Include -I/software/@sys/usr/include -I/usr/local/include -I/mnt/python/dist/src/Include -I/mnt/python/dist/src -c /mnt/python/dist/src/Modules/_cursesmodule.c -o build/temp.osf1-V5.1-alpha-2.3/_cursesmodule.o ld -shared -expect_unresolved * -ieee -std -Olimit 1500 -DNDEBUG -O -I. -I./Include build/temp.osf1-V5.1-alpha-2.3/_cursesmodule.o -L/software/@sys/usr/lib -L/usr/local/lib -lncurses -o build/lib.osf1-V5.1-alpha-2.3/_curses.so ld: -ieee: Unknown flag ld: Usage: ld [options] file [...] building '_curses_panel' extension |
|
|
| msg16242 - (view) |
Author: Martin v. Löwis (loewis) *  |
Date: 2003-06-14 06:40 |
| Logged In: YES user_id=21627 Is it not the case that cc(1) supports -ieee? If so, why does it then pass the option to ld? Perhaps it depends on the cc version whether -ieee is supported? Perhaps the compiler should be invoked with a different name? Please don't make us guess as to how your operating system works. If you can contribute to a solution, that would be much appreciated. |
|
|
| msg16243 - (view) |
Author: Martin Mokrejs (mmokrejs) |
Date: 2003-06-17 13:29 |
| Logged In: YES user_id=696559 Actually, I don't know why -ieee is needed, I'm not a programmer, sorry. The manpage cc(1) says: -ieee Ensure support of all portable features of the IEEE Standard for Binary Floating-Point Arithmetic (ANSI/IEEE Std 754-1985), including the treatment of denormalized numbers, NaNs, and infinities and the han- dling of error cases. This option also sets the _IEEE_FP C preprocessor macro. If your program must use IEEE signaling features that are not portable across different IEEE implementations, see the ieee(3) reference page for a discussion of how to access them under the Tru64 UNIX operating system. Yes, -ieee is not listed in mapage for ld(1). I do not have an access to that machine probably for a whole week, but are you sure the -ieee is not in teh generated Makefiles passed inside some variable to linker directly? |
|
|
| msg16244 - (view) |
Author: Martin v. Löwis (loewis) * |
Date: 2003-06-17 20:38 |
| Logged In: YES user_id=21627 I see; -ieee is indeed passed to ld. I am a programmer, but I cannot develop on Tru64. So we have to wait until a programmer with access to Tru64 shows up. |
|
|
| msg16245 - (view) |
Author: Martin Mokrejs (mmokrejs) |
Date: 2003-06-17 21:30 |
| Logged In: YES user_id=696559 Get free account on testing machine at http://www.testdrive.compaq.com/ |
|
|
| msg16246 - (view) |
Author: Neal Norwitz (nnorwitz) * |
Date: 2003-06-30 04:29 |
| Logged In: YES user_id=33168 Is this still a problem? When I test with the current CVS (2.3b2) on Tru64 5.1, I don't get many flags passed to ld, but my cc line looks the same. Can you make sure you have a clean copy of configure from CVS? Also, do a make clean and ./configure. cc -pthread -DNDEBUG -O -ieee -std -Olimit 1500 -I. -I/net/boa/scratch1/nnorwitz/python/dist/src/./Include -I/usr/local/include -I/net/boa/scratch1/nnorwitz/python/dist/src/Include -I/net/boa/scratch1/nnorwitz/python/dist/src -c /net/boa/scratch1/nnorwitz/python/dist/src/Modules/_cursesmodule.c -o build/temp.osf1-V5.1-alpha-2.3/_cursesmodule.o ld -shared -expect_unresolved * build/temp.osf1-V5.1-alpha-2.3/_cursesmodule.o -L/usr/local/lib -lcurses -ltermcap -o build/lib.osf1-V5.1-alpha-2.3/_curses.so |
|
|
| msg16247 - (view) |
Author: Martin Mokrejs (mmokrejs) |
Date: 2003-06-30 16:48 |
| Logged In: YES user_id=696559 So, for me the problem with -ieee is fixed in current cvs too. I still do have problems building the ncurses part(I use ncurses 5.3). But the ncurses I've reported as another bug report. So this report can be closed. Thanks. |
|
|