[gentoo-dev] gcc-3.3.6 for x86 stable

[gentoo-dev] gcc-3.3.6 for x86 stable

[Mike Frysinger]

any known/standing issues people wish to get out before we move gcc-3.3.6 to 
x86 stable ?

for those brave, please emerge gcc-3.3.6 on your stable x86 box and give it a 
twirl
-mike
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] gcc-3.3.6 for x86 stable

[Mike Doty]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mike Frysinger wrote:
| any known/standing issues people wish to get out before we move
gcc-3.3.6 to
| x86 stable ?
|
| for those brave, please emerge gcc-3.3.6 on your stable x86 box and
give it a
| twirl
| -mike
I've had issues compiling 3.3.6 with the hardened toolchain(cc1 dies
with a try_split error), but I hear that this is specific to hardened.
Other than that, I was able to emerge -e world using 3.3.6 without issue.

- --
=======================================================
Mike Doty                           kingtaco@gentoo.org
Gentoo/AMD64 Strategic Lead         PGP Key: 0xA797C7A7
Gentoo Developer Relations
~                 ===GPG Fingerprint===
~   0094 7F06 913E 78D6 F1BB  06BA D0AD D125 A797 C7A7
=======================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDGEhQ0K3RJaeXx6cRAr9dAKClgXu3MJr8sZHtFDfiQa4x06Eo2QCgnc67
aKgjNvV8s3A+NrRZCr9V0XE=
=S/Fs
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] gcc-3.3.6 for x86 stable

[Mike Frysinger]

On Friday 02 September 2005 08:40 am, Mike Doty wrote:
> I've had issues compiling 3.3.6 with the hardened toolchain(cc1 dies
> with a try_split error), but I hear that this is specific to hardened.

that, unfortunately, is both specific to hardened and unspecific to 
gcc-3.3.6 ... 3.3.5 and 3.4.x suffer to varying degrees atm :/
-mike
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] gcc-3.3.6 for x86 stable

[Gustavo Zacarias]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mike Frysinger wrote:

> any known/standing issues people wish to get out before we move gcc-3.3.6 to 
> x86 stable ?

You'll also need a matching dev-libs/libffi, otherwise it'll go all
circular for people using GNUstep.

- --
Gustavo Zacarias
Gentoo/SPARC monkey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDGHTYV3G/IBCn/JARAhY/AJ9QKUqcbTXn0prkt5ynGKhwprrdtwCaAyp2
a+g/RS8FVhcxxRCOFs7aPRY=
=Zyu/
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] gcc-3.3.6 for x86 stable

[Mike Frysinger]

On Friday 02 September 2005 11:50 am, Gustavo Zacarias wrote:
> Mike Frysinger wrote:
> > any known/standing issues people wish to get out before we move gcc-3.3.6
> > to x86 stable ?
>
> You'll also need a matching dev-libs/libffi, otherwise it'll go all
> circular for people using GNUstep.

toolchain doesnt maintain libffi, the gnustep peeps do ...
-mike
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] gcc-3.3.6 for x86 stable

[Ciaran McCreesh]

[-- Attachment #1: Type: text/plain, Size: 684 bytes --]

On Fri, 2 Sep 2005 12:05:38 -0400 Mike Frysinger <vapier@gentoo.org>
wrote:
| On Friday 02 September 2005 11:50 am, Gustavo Zacarias wrote:
| > Mike Frysinger wrote:
| > > any known/standing issues people wish to get out before we move
| > > gcc-3.3.6 to x86 stable ?
| >
| > You'll also need a matching dev-libs/libffi, otherwise it'll go all
| > circular for people using GNUstep.
| 
| toolchain doesnt maintain libffi, the gnustep peeps do ...

*cough* needs coordination from an arch team *cough*

-- 
Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] gcc-3.3.6 for x86 stable

[Armando Di Cianno]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2005-09-02 12:05:38 -0400 Mike Frysinger <vapier@gentoo.org> wrote:

> On Friday 02 September 2005 11:50 am, Gustavo Zacarias wrote:
>> Mike Frysinger wrote:
>>> any known/standing issues people wish to get out before we move 
>>> gcc-3.3.6
>>> to x86 stable ?
>> 
>> You'll also need a matching dev-libs/libffi, otherwise it'll go all
>> circular for people using GNUstep.
> 
> toolchain doesnt maintain libffi, the gnustep peeps do ...
> -mike

The gnustep herd (me) isn't going to be able to do much until the
weekend...hey, the weekend starts in about 4 hours for me ...

I've been trying to phase out dev-libs/libffi for a long while...if
someone can figure out a patch for gcc-3.3 series that compiles and
installs libffi w/o building the entirety of gjc/java/etc, that would
be fantastic; gcc-3.4 series has had this for a long time, and the
patch is incredibly simple -- my one attempt at doing this for gcc-3.3
series proved fruitless.  (The little bit of monkeying I've done with
gcc-4 series has proved easy wrt to this.)

'objc' USE flag pushes the patch on, so one can have USE="-gcj +objc"
... if I, or someone else who knows GCC innards better than I, figures
out the patch for gcc-3.3, I'd suggest adding a 'libffi' USE flag (so
the 'objc' flag goes back to just enabling ObjC), so the few misc.
ebuilds that use it besides GNUstep (sablevm comes to mind), can
enable libffi to be built (w/o gcj or even objc).

__armando di cianno
aka fafhrd

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1-ecc0.1.6 (GNU/Linux)
Comment: Using the GPG bundle for GNUMail

iD8DBQFDGIU8wgiTPLI9xhcRAtowAJ0RwEgBLOAF+f+rSKR3RUVs+ezDPQCgiPiA
dTULkSYe0hXN8UNUD+KoV1U=
=lQaw
-----END PGP SIGNATURE-----

-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] gcc-3.3.6 for x86 stable

[Mike Frysinger]

On Friday 02 September 2005 01:00 pm, Armando Di Cianno wrote:
> On 2005-09-02 12:05:38 -0400 Mike Frysinger <vapier@gentoo.org> wrote:
> > On Friday 02 September 2005 11:50 am, Gustavo Zacarias wrote:
> >> Mike Frysinger wrote:
> >>> any known/standing issues people wish to get out before we move
> >>> gcc-3.3.6
> >>> to x86 stable ?
> >>
> >> You'll also need a matching dev-libs/libffi, otherwise it'll go all
> >> circular for people using GNUstep.
> >
> > toolchain doesnt maintain libffi, the gnustep peeps do ...
>
> The gnustep herd (me) isn't going to be able to do much until the
> weekend...hey, the weekend starts in about 4 hours for me ...

i'm not exactly in a rush to make this happen, so i dont mind waiting for you 
to get libffi sorted (assuming it wont take like a month :P)

> I've been trying to phase out dev-libs/libffi for a long while...if
> someone can figure out a patch for gcc-3.3 series that compiles and
> installs libffi w/o building the entirety of gjc/java/etc, that would
> be fantastic; gcc-3.4 series has had this for a long time, and the
> patch is incredibly simple -- my one attempt at doing this for gcc-3.3
> series proved fruitless.  (The little bit of monkeying I've done with
> gcc-4 series has proved easy wrt to this.)

so has this all been integrated into the gcc ebuilds or does it need to be 
or ... ?
-mike
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] gcc-3.3.6 for x86 stable

[Armando Di Cianno]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2005-09-02 13:07:23 -0400 Mike Frysinger <vapier@gentoo.org> wrote:
>> I've been trying to phase out dev-libs/libffi for a long while...if
>> someone can figure out a patch for gcc-3.3 series that compiles and
>> installs libffi w/o building the entirety of gjc/java/etc, that would
>> be fantastic; gcc-3.4 series has had this for a long time, and the
>> patch is incredibly simple -- my one attempt at doing this for 
>> gcc-3.3
>> series proved fruitless.  (The little bit of monkeying I've done with
>> gcc-4 series has proved easy wrt to this.)
> 
> so has this all been integrated into the gcc ebuilds or does it need 
> to be or 
> ... ?
> -mike

> =gcc-3.4.3-r1 and <gcc-4* compiles and installs libffi seperately if 
> 'objc' is used (regardless of 'gcj', which always installs it); i.e. 
> the patch is already in there for that stated range of versions.

For gcc-4*, from what I looked at, the patch will also be quite easy
to make.  I've talked to one of the gcc/objc maintainers, and 4.1.0
might already offer libffi as a sepate build target (i.e. no need for
a patch to make it one).

For gcc-3.3, I looked at it way back when, and gave up ... so it might
not be difficult, I suppose, just significantly different enough from
the patch that works with gcc-3.4.

The dev-libs/libffi ebuilds are based on early libstdc++-v3 ebuilds
... but unlike libstdc++-v3, there's really no reason to offer it as a
seperate package, especially since gcc offers it.

The most ideal scenario is, across all gcc versions, 'objc' only
installs objc support, 'gcj' keeps doing it's gcj thing, and a new
flag 'libffi' installs libffi regardless of 'objc' or 'gcj'.  As one
of the few foreign function interface libraries out there (ffcall
comes to mind as well), libffi may be useful to some outside of
objc+GNUstep or gcj.

__armando

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1-ecc0.1.6 (GNU/Linux)
Comment: Using the GPG bundle for GNUMail

iD8DBQFDGJYcwgiTPLI9xhcRAs28AKCG8i2jrko1UgDMWPgJUq/CCTFPHACgipZC
pGgqI67R3u8O8HgI6O62sJY=
=46E2
-----END PGP SIGNATURE-----

-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] gcc-3.3.6 for x86 stable

[Mike Frysinger]

On Friday 02 September 2005 02:12 pm, Armando Di Cianno wrote:
> > =gcc-3.4.3-r1 and <gcc-4* compiles and installs libffi seperately if
> > 'objc' is used (regardless of 'gcj', which always installs it); i.e.
> > the patch is already in there for that stated range of versions.

lemme rephrase

what needs to happen in the gcc ebuilds so that we can punt the libffi package
-mike
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] gcc-3.3.6 for x86 stable

[Armando Di Cianno]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2005-09-02 15:46:23 -0400 Mike Frysinger <vapier@gentoo.org> wrote:

> On Friday 02 September 2005 02:12 pm, Armando Di Cianno wrote:
>>> =gcc-3.4.3-r1 and <gcc-4* compiles and installs libffi seperately if
>>> 'objc' is used (regardless of 'gcj', which always installs it); i.e.
>>> the patch is already in there for that stated range of versions.
> 
> lemme rephrase
> 
> what needs to happen in the gcc ebuilds so that we can punt the 
> libffi package
> -mike

Ahh.

Assuming we don't care about gcc-4, for the meanwhile:
- - figure out a backport of
${PORTDIR}/sys-devel/gcc/files/3.4.3/libffi-without-libgcj.patch for
gcc-3.3 series
- --+ Maybe do some more QA concerning where libs get installed; IIRC,
${PORTDIR}/sys-devel/gcc/files/3.4.3/libffi-nogcj-lib-path-fix.patch
was an attempt to fix up some mis-path issues with the first patch on
some systems (amd64)
- - remove triggering the above patch on 'objc' USE flag (which was
never really correct, but "pragmatic")
- - add 'libffi' USE flag to trigger the above patches (if 'gcj' is not
on...)

__armando


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1-ecc0.1.6 (GNU/Linux)
Comment: Using the GPG bundle for GNUMail

iD8DBQFDGLflwgiTPLI9xhcRAhyaAJkBnhq23T3HTPaj7FH5N0vgJ5957wCgruWD
ilY6ErNrbd2M1QHnnEtFPQ8=
=aP1h
-----END PGP SIGNATURE-----

-- 
gentoo-dev@gentoo.org mailing list