Martin,
If it's a system header, why are you lying to the compiler?
Maybe a real-life example and not a.h would help.
Neil.
Martin v. Loewis wrote:-
Neil Booth [EMAIL PROTECTED] writes:
If it's a system header, why are you lying to the compiler?
I'm not lying, I use a.h
You've not told the compiler it's a system header, so it doesn't think
it is. Let me see what Zack thinks.
Neil.
Processing commands for [EMAIL PROTECTED]:
reassign 146070 gcc-3.1
Bug#146070: gcl_2.5.0.cvs20020429-2(hppa/unstable): doesn't recognize hppa-linux
Bug reassigned from package `gcl' to `gcc-3.1'.
reassign 151886 gcc-3.1
Bug#151886: maxima_5.6a-2(hppa/unstable): FTBFS: needs porting work for
Accepted:
cpp-3.2_3.2-0pre3_hppa.deb
to pool/main/g/gcc-3.2/cpp-3.2_3.2-0pre3_hppa.deb
fastjar_3.2-0pre3_hppa.deb
to pool/main/g/gcc-3.2/fastjar_3.2-0pre3_hppa.deb
fixincludes_3.2-0pre3_hppa.deb
to pool/main/g/gcc-3.2/fixincludes_3.2-0pre3_hppa.deb
g++-3.2_3.2-0pre3_hppa.deb
to
Jan,
There definitely will be an issue with rebuilding glibc against
either gcc 3.1.1 or 3.2 on at least two, if not more, arches. The
problems arise from the change in gcc 3.1 which makes libgcc symbols
.hidden now. This means that if you rebuild the current glibc
2.2.5-13 with gcc 3.1.1/3.2,
5 matches
Mail list logo