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.
Neil Booth <[EMAIL PROTECTED]> writes:
> If it's a system header, why are you lying to the compiler?
I'm not lying, I use
> Maybe a real-life example and not "a.h" would help.
Ok, here is the real-life example. Consider
#include
int main(){}
which is compiled with
g++-3.1 -MM -I/opt/JBuil
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
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.
Hi ...
since this is my first time to get a distribution to a newer standard
compiler and I have no experiance with it, I want to ask, what is the
way to switch over to gcc-3.2?
A completely relaunch of debian or a slowly step step by step upload of
recompiled packages?
Just for informations :)
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 h
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 pool/main/g
Accepted:
cpp-3.2-doc_3.2-0pre3_all.deb
to pool/main/g/gcc-3.2/cpp-3.2-doc_3.2-0pre3_all.deb
cpp-3.2_3.2-0pre3_i386.deb
to pool/main/g/gcc-3.2/cpp-3.2_3.2-0pre3_i386.deb
fastjar_3.2-0pre3_i386.deb
to pool/main/g/gcc-3.2/fastjar_3.2-0pre3_i386.deb
fixincludes_3.2-0pre3_i386.deb
to pool/main
Jan-Hendrik Palic <[EMAIL PROTECTED]> writes:
> since this is my first time to get a distribution to a newer standard
> compiler and I have no experiance with it, I want to ask, what is the
> way to switch over to gcc-3.2?
>
> A completely relaunch of debian or a slowly step step by step upload o
Hi ...
On Sun, Aug 11, 2002 at 07:31:16PM +0200, Martin v. Loewis wrote:
>> A completely relaunch of debian or a slowly step step by step upload of
>> recompiled packages?
>For C++, it appears that all packages will be recompiled and uploaded
>in NMUs. For C packages, no action is needed.
Hmm ok
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,
Greetings! One other piece of information on my mind on this subject
which I'd like to share before going on to other things. gcl's
garbage collector relies on setjmp to put register contents on the C
stack, which is then walked to mark live objects. This works on all
platforms except hppa, wher
11 matches
Mail list logo
