bug-hurd
[Top][All Lists]
Advanced

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

Re: 64bit startup


From: Samuel Thibault
Subject: Re: 64bit startup
Date: Wed, 25 Oct 2023 16:05:47 +0200
User-agent: NeoMutt/20170609 (1.8.3)

Sergey Bugaev, le mer. 25 oct. 2023 16:29:29 +0300, a ecrit:
> On Wed, Oct 25, 2023 at 2:52 PM <jbranso@dismail.de> wrote:
> >
> > October 25, 2023 3:43 AM, "Samuel Thibault" <samuel.thibault@gnu.org> wrote:
> >
> > > jbranso@dismail.de, le mer. 25 oct. 2023 03:40:16 +0000, a ecrit:
> > >
> > >> Or maybe GCC is partly at fault for the
> > >> Hurd's X86_64 building troubles?
> > >
> > > It's not at all. Nor is libtool.
> > >
> > > I occasionally had issues in ./configure, too.
> > >
> > > You'll say that's "yeah, it's all about auto-crap". No.
> > >
> > > It's *very* most probably about bash, simply.
> > >
> > > Samuel
> >
> > Hmmm. I guess in the long-term then, the bash issues should be fixed.
> >
> > Could we change the default shell on X86_64 Debian Hurd in the meantime,
> > as a temporary solution?
> 
> I would rather ask, would it not be possible to set up a continuous
> build server (buildd? I know next to nothing about the Debian infra)
> that itself runs on a more stable architecture (amd64, or hurd-i386)
> and cross-compiles the packages?

Cross-compiling *very* often produces slightly bogus packages. They are
enough to bootstrap something you can build upon, but you cannot hope
more.

We do have cross-compiling boot strap set up on
https://jenkins.debian.net/view/rebootstrap/
but we don't want to upload the result, since when cross-compiling
there are various ./configure tests that you cannot run (execution-time
results).

Samuel



reply via email to

[Prev in Thread] Current Thread [Next in Thread]