Bug#1175: make diagnostics not shown / mystical error 126
> Example case:
> I have a system on which the dll tools (necessary for compiling librl)
> are not installed.
> When I ran 'make' in the readline subdir of librl-2.0.3-2, make appeared
> to call 'gcc' and then exits with 'Error 126', without either gcc or
> make giving any diagnostic message.
> When using 'strace', a child process of 'make' is seen to do a write(2)
> to stderr with a diagnostic message, but this message never shows up.
[...]
> I think this example case is easily reproducible.
I've been able to get nearly identical behaviour of 'make' on this case on the
following systems:
- SGI running IRIX 5.3, with GNU make 3.71:
gcc -S -c -O2 -DHAVE_UNISTD_H -DHAVE_VARARGS_H -DHAVE_STRING_H -DHAVE_DIRENT_H -DHAVE_STDLIB_H -DHAVE_ALLOCA_H -I. -I.. readline.c -o readline.s
make: *** [readline.o] Error 1
Exit 2
- HP running HP-UX A.09.05, with GNU make 3.71:
gcc -S -c -O2 -DHAVE_UNISTD_H -DHAVE_VARARGS_H -DHAVE_STRING_H -DHAVE_DIRENT_H -DHAVE_STDLIB_H -DHAVE_ALLOCA_H -I. -I.. readline.c -o readline.s
make: *** [readline.o] Error 1
Exit 2
- Pentium running FreeBSD 2.1-STABLE with GNU make 3.74:
gcc -S -c -O2 -DHAVE_UNISTD_H -DHAVE_VARARGS_H -DHAVE_STRING_H -DHAVE_DIRENT_H -DHAVE_STDLIB_H -DHAVE_ALLOCA_H -I. -I.. readline.c -o readline.s
make: *** [readline.o] Error 2
Unfortunately, I don't have access to 'strace' or an equivalent on
these systems.
I think it is now clear that this is a problem with 'make' itself, not
with the Debian 'make' package. Therefore I request that this bug be
reported to bug-gnu-utils.
Ray
--
PATRIOTISM A great British writer once said that if he had to choose
between betraying his country and betraying a friend he hoped he would
have the decency to betray his country.
- The Hipcrime Vocab by Chad C. Mulligan
Reply to: