Hi all:
I haven't had any luck with this on vorbis-dev, so I thought I'd try
here.
Note that for those who have read this already, there's new stuff at the
bottom.
I'm getting the folowing when attempting to compile vorbis-tools from CVS:
Making all in intl
make[1]: Entering directory `/usr/src/cvs/vorbis-tools/intl'
make[1]: *** No rule to make target `all-no-@BUILD_INCLUDED_LIBINTL@',
needed by `all-no'. Stop.
make[1]: Leaving directory `/usr/src/cvs/vorbis-tools/intl'
make: *** [all-recursive] Error 1
This is after running ./autogen.sh with no options. I examined the output
of configure. Burried away in the output, not in the log btw, was the
following error:
ed: can't read ./intl/po2tbl.sed.in: No such file or directory
Here it is in context:
checking for xgettext... (cached) /usr/bin/xgettext
checking for catalogs to be installed... fr nl sv
sed: can't read ./intl/po2tbl.sed.in: No such file or directory
There's nothing at all to help in config.log, but grepping for po2tbl
reveals the following:
configure:3499: $srcdir/intl/po2tbl.sed.in > intl/po2tbl.sed
This line is also in aclocal.m4:
aclocal.m4:1490: dnl po2tbl.sed is always needed.
aclocal.m4:1492: $srcdir/intl/po2tbl.sed.in > intl/po2tbl.sed
Going right back to the start, doing a fresh checkout and searching for
po2tbl reveals that it only exists in one place:
intl/Makefile.in:79:DISTFILES.obsolete = xopen-msg.sed linux-msg.sed
po2tbl.sed.in cat-compat.c
I also tried './configure --with-included-gettext' with the same result.
This looks like an auto* issue to me, though I know very little about it.
The commands that reference po2tbl.sed.in only appear after running
./autogen.sh and I'm wondering if it's being found somewhere else on my
system? At any rate, configure should bomb if it hits this error
evidently, as it causes problems for the Makefile in intl.
My system configuration:
Debian GNU/Linux 2.2r6 (Potato)
kernel 2.2.20
gcc version 2.95.2 20000220 (Debian GNU/Linux)
GNU Make version 3.79.1, by Richard Stallman and Roland McGrath.
Autoconf version 2.13
automake (GNU automake) 1.4
gettext (GNU gettext) 0.10.35
Vorbis-tools is current CVS.
Let me know if you need any more information. I really want to try out CVS
and would like to help iron out any compilation bugs.
UPDATE: Ok, so I decided to try a newer gettext. I grabbed the latest
(0.11.2) from gnu.org and compiled and installed it. No difference, except
that autogen also gave me the following:
Generating configuration files for vorbis-tools, please wait....
aclocal
aclocal: configure.in: 23: macro `AM_GNU_GETTEXT' not found in library
Make still bombed as usual. I even tried running ./configure with
--disable-nls . Same deal.
So having beaten myself about the head with gettext to the greatest extent
possible given my limited knowlege in this area, I decided that maybe the
error message produced by configure and the problem that make was hitting
might actually not be related. so I re-examined the compilation error.
For those who've forgotten that part of the story, here it is again:
Making all in intl
make[1]: Entering directory `/usr/src/cvs/vorbis-tools/intl'
make[1]: *** No rule to make target `all-no-@BUILD_INCLUDED_LIBINTL@',
needed by `all-no'. Stop.
make[1]: Leaving directory `/usr/src/cvs/vorbis-tools/intl'
make: *** [all-recursive] Error 1
I know just about as little about make as I do about the auto tools, but
nevertheless, I took a look at intl/Makefile. These are the relevant
lines:
107:all: all-no
108:all-yes: libintl.$la libintl.h charset.alias ref-add.sed ref-del.sed
109:all-no: all-no-@BUILD_INCLUDED_LIBINTL@
110:all-no-yes: libgnuintl.$la
111:all-no-no:
Line 109 is obviously the key, being refered there by line 107. That is
the only place in the file where INCLUDED_LIBINTL appears. So I looked at
Makefile.in. Here's what's at the same place:
107:all: all-@USE_INCLUDED_LIBINTL@
108:all-yes: libintl.$la libintl.h charset.alias ref-add.sed ref-del.sed
109:all-no: all-no-@BUILD_INCLUDED_LIBINTL@
110:all-no-yes: libgnuintl.$la
111:all-no-no:
This sheds a little more light on things. Obviously the
@USE_INCLUDED_LIBINTL@ on line 107 is translated at 'yes' or
'no',
depending on its value, to generate the line 107 we find in Makefile.
Presumably then, @BUILD_INCLUDED_LIBINTL@ on line 109 should translate in
the same manner. so 109 should either read:
all-no: all-no-yes
or
all-no: all-no-no
Dependant on the value of some variable called, presumably, something other
than BUILD_INCLUDED_LIBINTL (since it's not being translated correctly).
hmmm..I appear to be solving my own problem as I go along. Anyway, digging
around in Makefile.in doesn't suggest to me what should be done to make
line 109 translate properly. It seems that I could just change it myself
in intl/Makefile and it should compile. However, the fact that it didn't
work out of the box, and the fact that it appears to for other users, leads
me to wonder whether there's some deeper build issue here that should be
sorted out prior to release.
I want to knock this one on the head, but I'm out of my depth. If you guys
who look after the build system need any more details, just ask.
hmmm...Modified the Makefile and it built.
Geoff.
<p><p>
--
Geoff Shang <gshang@uq.net.au>
ICQ number 43634701
Make sure your E-mail can be read by everyone!
http://www.betips.net/etc/evilmail.html
Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html
<p><p><p><p><p><p>--- >8 ----
List archives: http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to
'vorbis-request@xiph.org'
containing only the word 'unsubscribe' in the body. No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.