Hi Randolph,
>>
>>> I am looking to rebuild gcc-3.3 64bits to rebuild the last kernel 2.4
>to
>>> conitnue my investigation about smp(64bits) [which failled to boot on
>a
>>N4000
>>> when compile d with gcc-3.2 get from unofficial-debs].
>>
>>If you are working on 64-bit, I would advise staying w
>>
>Ok I am gonna try to rebuild it with gcc-3.0.
>
Wel I just do it (in 32bits naturaly) and already encounter a problem :_)
:
`gcc -print-libgcc-file-name`
/usr/src/work/linux-2.4.20-pa28/arch/parisc/lib/lib.a
/usr/src/work/linux-2.4.20-pa28/lib/lib.a \
--end-group \
-o vmlinux
[EMAIL PROTECTED]
>Subject: Re: [parisc-linux] Re: gcc-3.2 -> gcc-3.3 transition on hppa
>Reply-To: Randolph Chung <[EMAIL PROTECTED]>
>
>
>> I am looking to rebuild gcc-3.3 64bits to rebuild the last kernel 2.4
to
>> conitnue my investigation about smp(64bits) [w
> I am looking to rebuild gcc-3.3 64bits to rebuild the last kernel 2.4 to
> conitnue my investigation about smp(64bits) [which failled to boot on a N4000
> when compile d with gcc-3.2 get from unofficial-debs].
If you are working on 64-bit, I would advise staying with 3.0.4 for
now no one has
>Subject: [parisc-linux] Re: gcc-3.2 -> gcc-3.3 transition on hppa
>Date: Sat, 1 Mar 2003 20:59:36 -0800
>
>
>In reference to a message from Matthias Klose, dated Mar 01:
>> Matthias Klose writes:
>> > AFAIK the transition from 3.2 to 3.3 requires recompilation of C++
&
> Did you configure 3.3 using "--enable-sjlj-exceptions=yes"? That way
> the 3.3 C++ library should be compatible with the previous 3.3 library.
> The switch to dwarf2 can be delayed until the next debian release.
yeah, i exchanged some mail with Matthias about this.
Anyway, I have the debs inst
> Randolph Chung writes:
> > In reference to a message from Matthias Klose, dated Mar 01:
> > > Matthias Klose writes:
> > > > AFAIK the transition from 3.2 to 3.3 requires recompilation of C++
> > > > code due to the changed exception handling (now DWARF2 based). As
> > > > libstdc++ in 3.2 and 3.
Randolph Chung writes:
> In reference to a message from Matthias Klose, dated Mar 01:
> > Matthias Klose writes:
> > > AFAIK the transition from 3.2 to 3.3 requires recompilation of C++
> > > code due to the changed exception handling (now DWARF2 based). As
> > > libstdc++ in 3.2 and 3.2 have the s
> Nice and is it also possible to produce a 64bits version of gcc?
Last time I tried (couple of weeks ago), it was possible to build
a 64-bit cross starting with 3.3. This still doesn't work with 3.2.
Dave
--
J. David Anglin [EMAIL PROTECTED]
National Research C
>-- Original Message --
>From: Randolph Chung <[EMAIL PROTECTED]>
>To: Matthias Klose <[EMAIL PROTECTED]>
>Cc: debian-hppa@lists.debian.org, debian-gcc@lists.debian.org,
> [EMAIL PROTECTED]
>Reply-To: Randolph Chung <[EMAIL PROTECTED]>
>Subject
> In reference to a message from Matthias Klose, dated Mar 01:
> > Matthias Klose writes:
> > > AFAIK the transition from 3.2 to 3.3 requires recompilation of C++
> > > code due to the changed exception handling (now DWARF2 based). As
> > > libstdc++ in 3.2 and 3.2 have the same soname, how to hand
In reference to a message from Matthias Klose, dated Mar 01:
> Matthias Klose writes:
> > AFAIK the transition from 3.2 to 3.3 requires recompilation of C++
> > code due to the changed exception handling (now DWARF2 based). As
> > libstdc++ in 3.2 and 3.2 have the same soname, how to handle it?
> >
Matthias Klose writes:
> AFAIK the transition from 3.2 to 3.3 requires recompilation of C++
> code due to the changed exception handling (now DWARF2 based). As
> libstdc++ in 3.2 and 3.2 have the same soname, how to handle it?
> Currently 3.2 is in unstable only. Would you want to start the
> recom
AFAIK the transition from 3.2 to 3.3 requires recompilation of C++
code due to the changed exception handling (now DWARF2 based). As
libstdc++ in 3.2 and 3.2 have the same soname, how to handle it?
Currently 3.2 is in unstable only. Would you want to start the
recompilation before 3.2 based binarie
14 matches
Mail list logo
