Opened 9 years ago
Last modified 8 years ago
#89 new defect
automake: SYS0003
Reported by: | dmik | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | dev tools |
Component: | automake/autoconf | Version: | |
Severity: | medium | Keywords: | |
Cc: |
Description
When trying to autoconf pango with our latest automake RPM (1.14.1), I get the following after issuing autoreconf -fvi
:
autoreconf: failed to run automake: SYS0003=0x3: The system cannot find the path specified
As a result, some of the Makefile.am
files are not processed (no Makefile.in
is generated).
Change History (4)
comment:1 by , 9 years ago
Priority: | major → minor |
---|
comment:2 by , 8 years ago
Component: | → *none |
---|
yes this is a nasty automake error. When it can't create something it always spits this error. I had ton's of those until I fixed all binutils problems.
comment:3 by , 8 years ago
Component: | *none → automake/autoconf |
---|
comment:4 by , 8 years ago
Milestone: | → dev tools |
---|
Note:
See TracTickets
for help on using tickets.
Diving in automake/autoconf waters shows that this error comes from the
$!
Perl variable which keeps the last LIBC error (e.g. the value ofstrerror(errno)
). Analyzing the autoreconf output shows that automake actually fails with this error:and the
$!
value is either random (from some unrelated LIBC call that happens after the above error condition) or is a bug in the OS/2 perl implementation. To my taste, the former is more likely. If so, this is then a problem in autoconf logic (Autom4te/FileUtils.pm
,handle_exec_errors
, to be exact) which should perhaps not rely on$1
if$?
is not zero as there are good chances it's unrelated. Anyway, I have too little knowledge ATM to make the final decision so I will postpone it for a while, given that if I fix the original error (ENABLE_GTK_DOC thingy, see r1268), this problem goes away.