On Jun 29, Yann Dirson ([EMAIL PROTECTED]) wrote:
Despite the build-essential list and gcc-defaults package pointing to
gcc 3.3, at least 6 archs still used 3.2 this week (alpha ia64 powerpc
m68k mips mipsel) and buildds on s390 and hppa still do not print the
toolchain versions, so I
Neil Roeth wrote:
I'd like to know this, too. I recently fixed some bugs on
m68k (a painful experience) and the most recent bug reports are basically
the bug you closed is reoccurring. If the compiler I'm using to test my
fixes is different than the one used to build the package, that
On Jun 29, Yann Dirson ([EMAIL PROTECTED]) wrote:
Despite the build-essential list and gcc-defaults package pointing to
gcc 3.3, at least 6 archs still used 3.2 this week (alpha ia64 powerpc
m68k mips mipsel) and buildds on s390 and hppa still do not print the
toolchain versions,
Despite the build-essential list and gcc-defaults package pointing to
gcc 3.3, at least 6 archs still used 3.2 this week (alpha ia64 powerpc
m68k mips mipsel) and buildds on s390 and hppa still do not print the
toolchain versions, so I can't tell for those 2 ones.
That's half of our archs
4 matches
Mail list logo