On Thu, Oct 26, 2000 at 03:10:33PM -0500, Skip Montanaro wrote: > Short term workaround is to run configure with TMPDIR set somewhere else. > Perhaps this is something to put in a gcc-specific or Unix-specific section > of the README file. I didn't see anything, and the message emitted by > configure gave no hint at the cause of the problem. I realized what it was > because I've been scratching my head about this problem for a couple weeks. > If this is deemed useful I'll modify README and check it in. If not, no big > deal. If you start adding things like that, also consider all the other possibilities of configure being wrong. I hinted at one of them a couple of weeks back, I think. (Somehow, 'last saturday', when I headed for London for the Apachecon, feels like about two months ago :P) It's perfectly possible for configure to be able to run gcc, gcc to be able to create working binaries, but every check for a function or datatype failing because the more 'involved' include files are missing. This is easy to do on Linux, (removing /usr/src/linux, for instance) but not impossible on other systems either. -- Thomas Wouters <thomas@xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4