> *** PANIC *** The C compiler can no longer build working
executables.
> *** PANIC *** Please examine the tail of config.log for runtime errors.
vk> Hmm.. no config.log output that I can see, so I'm
vk> speculating here.
config.log is attached to this message.
vk> The *real* most common problems at this point
vk> are:
vk> 1) Check 'df' and 'df -i' to make sure that
vk> you've not run out of space (either on the
vk> filesystem you untarred XEmacs on, and/or
vk> /tmp,/var/tmp, or whatever your compiler uses for
vk> work space).
That possibility never even occurred to me. As a matter
of fact, yes, I just noticed for the first time ever a
little while ago that I was at 100% in /. I removed
what I confidently thought could be deleted, and got it
down to 94%, still a bit close for comfort, but that
leaves 300,000 blocks, which should be enough, at least
to get through configure, right?. How much should it
need? (There are plenty of inodes, BTW.)
However, it didn't. I reran configure and got the same
message.
I haven't run out of space in a file system in quite a
few years. (The file system I'm doing the build in has
4.8 million blocks available.)
vk> 2) You untarred and/or built XEmacs before as
vk> root, but are now building as a mortal user.
Not the case.
vk> 3) Less likely - bogon umask value and/or stray
vk> 'chmod -R' has whomped something in an
vk> interesting manner.
Nope. umask is 022. The source directory is fine, and
everything is owned by me ... files mostly 644,
directories 2755.
vk> If 'df', 'df -i', and 'ls -la' dont find
vk> something that explains it, let us know - this
vk> time with the corresponding config.log output...
Attached. Thank you for the quick response.
--
Lynn David Newton
Phoenix, AZ