--- Comment #11 from martin dot drab at fjfi dot cvut dot cz 2008-05-23
16:05 ---
Alright, and I think I know what causes the rest of the path problem. The
GCC_EXEC_PREFIX environment variable has to lead to the .../lib/gcc/ and not
the .../lib/gcc/x86_64-pc-linux-gnu/4.4.0 and IT HAS T
--- Comment #10 from Ralf dot Wildenhues at gmx dot de 2008-05-23 15:25
---
The --enable-version-specific-runtime-libs bit of this bug report is
a duplicate of PR32415
--
Ralf dot Wildenhues at gmx dot de changed:
What|Removed |Added
-
--- Comment #9 from martin dot drab at fjfi dot cvut dot cz 2008-05-23
11:09 ---
OK, so I tried to compile with autogenerated paths just from the prefix, and
with the --enable-version-specific-runtime-libs option. The path no longer
seems corrupted. It searches all its internal include
--- Comment #8 from martin dot drab at fjfi dot cvut dot cz 2008-05-23
01:09 ---
But I have been using the prefixes like these for ages and it used to work with
4.3 and older versions just fine.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36213
--- Comment #7 from martin dot drab at fjfi dot cvut dot cz 2008-05-23
01:00 ---
(In reply to comment #5)
> Is there a reason why you are supplying all these weird configure options?
>
> --exec-prefix=/usr/local/opt/MDL/opt/gcc-4.4 --sysconfdir=/etc
> --libdir=/usr/local/opt/MDL/opt/gc
--- Comment #6 from martin dot drab at fjfi dot cvut dot cz 2008-05-23
00:49 ---
One more thing I've forgotten to mention is that (no matter if the
--enable-version-specific-runtime-libs is there or not) files limits.h and
syslimits.h are not generated into the internal "include" direct
--- Comment #5 from pinskia at gcc dot gnu dot org 2008-05-23 00:44 ---
Is there a reason why you are supplying all these weird configure options?
--exec-prefix=/usr/local/opt/MDL/opt/gcc-4.4 --sysconfdir=/etc
--libdir=/usr/local/opt/MDL/opt/gcc-4.4/lib64
--libexecdir=/usr/local/opt/MDL
--- Comment #4 from martin dot drab at fjfi dot cvut dot cz 2008-05-23
00:40 ---
OK, tried current snapshot without the --enable-version-specific-runtime-libs
and no change. :-( So, that was probably not the problem.
---
$ gcc -v
Using built-in specs.
Target: x86_64-pc-linu
--- Comment #3 from martin dot drab at fjfi dot cvut dot cz 2008-05-22
21:51 ---
Is using --enable-version-specific-runtime-libs the problem?
Should it not be used? I use it because from time to time I have more than one
version installed at the same time. Do you say that it should not
--- Comment #2 from pinskia at gcc dot gnu dot org 2008-05-22 20:07 ---
Is there a reason why you use --enable-version-specific-runtime-libs ?
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--
10 matches
Mail list logo
