From: Raphael Manfredi <ram@hptnos02.grenoble.hp.com>
>
> Quoting Paul Marquess:
> :Figuring out host name...
> :Maybe "hostname" will work...
> :Your host name appears to be "claudius". Right? [y]
> :(You do not have fully-qualified names in /etc/hosts)
> :(No help from resolv.conf either -- attempting clever guess)
> :
> :What is your domain name? [.bfsec]
> :
> :Here is the entry from my /etc/hosts file:
> :
> : 132.146.76.3 claudius claudius.bfsec.bt.co.uk loghost
> :
> :I would have expected Configure to have used bfsec.bt.co.uk
>
> Indeed, it should have.
oops, false alarm. I was testing Configure on two machines at the same
time. One is running yp, the other isn't. I accidentally got them mixed
up.
> As for the non-blocking I/O not being in perl's Configure, the unit
> is now part of the standard metaconfig release. So it must be that
> the right symbols are not scanned by Andy's metaconfig. He may have
> omitted the relevant files from the MANIFEST.new?
Can this get added next time Andy?
Paul
>
> Quoting Paul Marquess:
> :Figuring out host name...
> :Maybe "hostname" will work...
> :Your host name appears to be "claudius". Right? [y]
> :(You do not have fully-qualified names in /etc/hosts)
> :(No help from resolv.conf either -- attempting clever guess)
> :
> :What is your domain name? [.bfsec]
> :
> :Here is the entry from my /etc/hosts file:
> :
> : 132.146.76.3 claudius claudius.bfsec.bt.co.uk loghost
> :
> :I would have expected Configure to have used bfsec.bt.co.uk
>
> Indeed, it should have.
oops, false alarm. I was testing Configure on two machines at the same
time. One is running yp, the other isn't. I accidentally got them mixed
up.
> As for the non-blocking I/O not being in perl's Configure, the unit
> is now part of the standard metaconfig release. So it must be that
> the right symbols are not scanned by Andy's metaconfig. He may have
> omitted the relevant files from the MANIFEST.new?
Can this get added next time Andy?
Paul