On Wed, Jun 20, 2007 at 07:25:53AM -0500, Stephen R Marenka wrote:
> > For the time being I am using 'sbuild -d stable' and I edit the .changes
> > file manually.
>
> Do you have a chroot-etch-m68k? Does it have deb-src listed for
> etch-m68k? Also sbuild would need a minor patch to build etch-m6
This probably doesn't have any relevance, however it seems that fortran
segfaults when building r-base, except on akire, which may be the only
buildd still running a 2.4 kernel. I probably need to validate this with
aranym.
Unfortunately, -pie is still a problem.
--
Stephen R. Marenka If
> > Pick one, I guess.
>
> I'm currently rebuilding glibc on washi.
Chicken-or-egg, it seems:
configure:5857: checking for -fpie
configure:5868: gcc-4.1 -g -O2 -isystem
/build/mschmitz/glibc-2.5/debian/include -pie -fpie
-o conftest conftest.c 1>&5
/usr/lib/libc_no
> > So it would seem the latter error originates with glibc. The former I'm
> > unsure about. What is the more important error here - the undefined
> > reference or the nonrepresentable section?
>
> The __init_array_* error is blocking openssh, which we actually use.
But which does not block anyth
On Wed, Jun 20, 2007 at 03:30:24PM +0200, Michael Schmitz wrote:
> > Should we try building glibc with the latest gcc/binutils?
>
> Either that, or try building gcc with the latest glibc and binutils. I
> just downgraded gcc to 4.1.1-21 (old binutils and libc) and that didn't
> work either. Well
> > I cannot find a build log for glibc 2.5 later than -3 - that one was still
> > built using binutils 2.17-3, and does not declare a conflict on binutils
> > pre-cvs. What version of binutils were libc6 2.5-10 and -11 built with?
>
> glibc_2.5-11 was built on akire
>
> Toolchain package versions:
On Wed, Jun 20, 2007 at 10:26:58AM +0200, Bill Allombert wrote:
> On Tue, Jun 19, 2007 at 04:46:52PM +0100, Wouter Verhelst wrote:
> > regular dupload? You may need to target etch-m68k instead of etch, I
> > guess. ISTR sbuild having an option for that (specifying the release to
> > generate .chang
On Wed, Jun 20, 2007 at 11:19:54AM +0200, Michael Schmitz wrote:
> > > We can try to build a pre-2.17cvs version on sid, right? I'll try that on
> > > washi ...
> >
> > That's the conclusion I came to also.
>
> The gcc -pie problem also occurs with binutils 2.17-3 rebuilt against
> current sid.
>
> > We can try to build a pre-2.17cvs version on sid, right? I'll try that on
> > washi ...
>
> That's the conclusion I came to also.
The gcc -pie problem also occurs with binutils 2.17-3 rebuilt against
current sid.
I cannot find a build log for glibc 2.5 later than -3 - that one was still
built
On Tue, Jun 19, 2007 at 04:46:52PM +0100, Wouter Verhelst wrote:
> regular dupload? You may need to target etch-m68k instead of etch, I
> guess. ISTR sbuild having an option for that (specifying the release to
> generate .changes files for).
'sbuild -d etch-m68k' does not work. I added a priority
10 matches
Mail list logo
