On Tue, 08 Feb 2005 11:50:33 +0100, Martin Costabel <[EMAIL PROTECTED]> wrote:
> Stephen Hocking wrote:
>
> > All,
> >
> > Did my usual fink selfupdate && fink update-all and discovered (after
> > I'd updated cc-tools as per the .dmg from the gnu site) that the
> > configure process for g95 removes /dev/null. Has anyone else seen
> > this?
>
> Yes. See the thread "Re: [Fink-devel] Re: cctools-gcc4.info" on this
> list. Recipes to recover /dev/null are given there (reboot as a last
> resort). No bug fix yet, because the precise cause is unknown.
>
OK, I think I have a workaround, which is pretty disgusting. In a
terminal window, do a "sudo -s", and then type the following -
while :
do
sleep 1
if [ ! -c /dev/null ]
then
mknod /dev/null c 3 2
chmod 666 /dev/null
fi
done
In another terminal window, do your "fink update-all". This should get
through the configure phase eventually and then go on to build the
package. Why g95 borks us, I don't know. I suspect there's either
something wrong with autoconf or the supplied configure scripts. It
might be worthwhile someone going through the tarball and doing these
steps manually. configure.log should give us a clue where things
started to go down the gurgler. Meanwhile, I'm off to bed.
Stephen
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
