[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: How was compiled cssc on ia64, and other issues

Yann Dirson writes:
> Hi,
> The excuses file for cssc tells it's no promoted because it shows a
> dep on gcc-3.1, which I don't feel is normal.  I found out that the
> ia64 binary says:
> Depends: libc6.1 (>= 2.2.4-4), libgcc1 (>= 1:3.1), libstdc++3 (>= 1:3.0.3-1)
> Whereas I had put in the build-deps " g++-3.0 [ia64]", and the rules
> file contain code to use 3.0, not 3.1:

The shared libgcc1 is built by gcc-3.0 and gcc-3.1. The libgcc1
package is built from the gcc-3.1 sources.

> Is it that "gcc" now points to "gcc-3.1" by default on ia64 ?
Not yet.

> Should I remove the hack because g++ would also be g++-3.1 ?
Not before g++-3.2 becomes the default compiler.

> What's silly about that is that gcc-3.1 only seems to be held out of
> testing because an error in copyright file (and maybe because binutils
> is held, which seems to come from an arm-specific patch not being
> applicable any more)...  Are these issues to be settled in the near
> future ?

Maybe it's better to keep out 3.1 out of testing at all. gcc-3.2 will
be released soon (3.2 == 3.1.1 + g++ ABI changes).

the error in the copyright file is not the only reason, the build of
the sparc64 compiler currently fails.


To UNSUBSCRIBE, email to debian-ia64-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to: