Ainsi parlait Stew Benedict :
[..]
> If it doesn't break gcc2.95, I don't mind if you add it, I suppose we could
> have a sub-package of your gpc which is for x86 with the pieces you need
> and exclude ppc so there is no overlap of files in the PPC install.
The current ppc gcc2.95 package and my own standalone gpc package have the
following common files:
/usr/lib/gcc-lib/%{arch}-mandrake-linux-gnu/2.95.3/SYSCALLS.c.X
/usr/lib/gcc-lib/%{arch}-mandrake-linux-gnu/2.95.3/cc1
/usr/lib/gcc-lib/%{arch}-mandrake-linux-gnu/2.95.3/collect2
/usr/lib/gcc-lib/%{arch}-mandrake-linux-gnu/2.95.3/crtbegin.o
/usr/lib/gcc-lib/%{arch}-mandrake-linux-gnu/2.95.3/crtbeginS.o
/usr/lib/gcc-lib/%{arch}-mandrake-linux-gnu/2.95.3/crtend.o
/usr/lib/gcc-lib/%{arch}-mandrake-linux-gnu/2.95.3/crtendS.o
/usr/lib/gcc-lib/%{arch}-mandrake-linux-gnu/2.95.3/libgcc.a
/usr/lib/gcc-lib/%{arch}-mandrake-linux-gnu/2.95.3/specs
/usr/lib/gcc-lib/%{arch}-mandrake-linux-gnu/2.95.3/include (directory)
I guess making the gcc2.95 to be no more ppc-only is not a valid option,
cause it would means more support for mdk peoples ? However, it would silent
many critics about use of 2.96, and offer a proper solution here.
Fo keeping with current situation, i would suggest to have a
multi-arch gcc2.95-base with the previous file list, a multi-arch gcc2.95-gpc
with only addional gpc files, and keep other gcc2.95 subpackage ppc-only.
Any other suggestion appreciated, as i'm a total newbie concerning
compilers...
> I'll know soon enough if it breaks it, as I'm building daily here.
Anyway, as the package is in main, i don't have necessary rights to commit
myself. Once we agree on how to do it, i'll send you a spec diff and let you
proceed.
--
Guillaume Rousse <[EMAIL PROTECTED]>
GPG key http://lis.snv.jussieu.fr/~rousse/gpgkey.html
