On Wed, Aug 16, 2006 at 12:37:24PM +1000, Andrew Bartlett wrote:
> On Tue, 2006-08-15 at 19:43 +0200, Peter Eisentraut wrote:
> > Steve Langasek wrote:
> > > IIRC, the amd64 buildd runs in a vserver, which does nasty
> > > things to how interfaces are seen from userspace. This may be a
> > > symp
On Tue, 2006-08-15 at 19:43 +0200, Peter Eisentraut wrote:
> Steve Langasek wrote:
> > IIRC, the amd64 buildd runs in a vserver, which does nasty
> > things to how interfaces are seen from userspace. This may be a
> > symptom of that.
>
> It's possible to reproduce the problem locally if you shu
Steve Langasek wrote:
> IIRC, the amd64 buildd runs in a vserver, which does nasty
> things to how interfaces are seen from userspace. This may be a
> symptom of that.
It's possible to reproduce the problem locally if you shut down all your
interfaces (/sbin/ifconfig shows nothing) before build
On Tue, Aug 15, 2006 at 02:01:27PM +0200, Peter Eisentraut wrote:
> The problem is that the configure code that determines the method for
> getting the list of network interfaces mysteriously fails on the amd64
> buildd.
> Usual output:
> checking for iface AIX... no
> checking for iface ifconf
The problem is that the configure code that determines the method for
getting the list of network interfaces mysteriously fails on the amd64
buildd.
Usual output:
checking for iface AIX... no
checking for iface ifconf... got 2 interfaces:
eth0 IP=129.206.69.122 NETMASK=255.255.255.0
lo
5 matches
Mail list logo