Accepted:
chill_2.95.4-16_i386.deb
to pool/main/g/gcc-defaults/chill_2.95.4-16_i386.deb
cpp_2.95.4-16_i386.deb
to pool/main/g/gcc-defaults/cpp_2.95.4-16_i386.deb
g++_2.95.4-16_i386.deb
to pool/main/g/gcc-defaults/g++_2.95.4-16_i386.deb
g77_2.95.4-16_i386.deb
to pool/main/g/gcc-defaults/g77
Hi,
In the article <[EMAIL PROTECTED]>,
NIIBE Yutaka <[EMAIL PROTECTED]> wrote:
> In 3.0.4, we have no Fortran because of nasty reload bugs of SuperH,
> we have no Java because of lack of runtime support. Those two are
> already have been worked done nicely for 3.1.
>
> Forthcoming 3.2 has ABI
In the article <[EMAIL PROTECTED]>,
YAEGASHI Takeshi <[EMAIL PROTECTED]> wrote:
> Niibe, could you make patches agaist gcc sources in current gcc-3.1
> package (1:3.1.1ds2-0pre3)? You can leave other trivial deb packaging
> tasks to me.
Sorry the latest version seems 1:3.1.1ds3-1 now.
--
YAEGAS
Well it doesn't look like its binutils so far. I tried building
the current gcc-3.1-3.1.1-ds3 source package against current debian
sid and my local 2.12.90.0.15 binutils and it fails in the same
manner. I am now rebuilding my local gcc-3.1.1 package which is based
on the debian rules/patches d
YAEGASHI Takeshi writes:
> Hi,
>
> In the article <[EMAIL PROTECTED]>,
> NIIBE Yutaka <[EMAIL PROTECTED]> wrote:
>
> > In 3.0.4, we have no Fortran because of nasty reload bugs of SuperH,
> > we have no Java because of lack of runtime support. Those two are
> > already have been worked done nice
Chris and Matthias,
It appears that binutils is definitely not the culprit with
gcc-3.1-3.1.1ds3-1's failure on debian ppc sid. I see the same
failure with the build of gcc-3.1-3.1.1ds3-1 on my machine with
a locally built binutils 2.12.90.0.15 installed as we do on
voltaire. However, I still am
6 matches
Mail list logo