|
Home > Archive > Debian Developers > June 2007 > [Help] Autoconf problems when trying to build WordNet 3.0 package
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
[Help] Autoconf problems when trying to build WordNet 3.0 package
|
|
| Andreas Tille 2007-06-27, 1:22 pm |
| Hi,
I have some trouble building the new version of WordNet. For
reasons I do not want to discuss here I had to build a composite
source tarball from two different upstream tarballs and had
to adjust the autoconf stuff - which obviousely failed. I
putted the relevant files to
http://people.debian.org/~tille/packages/wordnet/
where you can see in the end of the pbuilder build log the lines:
cc -DHAVE_CONFIG_H -I. -I.. -I../include -I/include -I../include -I/include -g -Wall -O2 -c -o wishwn-tkAppInit.o `test -f 'tkAppInit.c' || echo './'`tkAppInit.c
tkAppInit.c:16:16: error: tk.h: No such file or directory
the relevant line in src/Makefile.am is
INCLUDES = -I$(top_srcdir)/include $(TCL_INCLUDE_SPEC) -I$(TK_PREFIX)/include
I have no idea why TCL_INCLUDE_SPEC which is not propagated
correctly to Makefile.in and thus cc has not the correct path
to the needed includes.
Any help would be welcome
Andreas.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Ben Pfaff 2007-06-27, 1:22 pm |
| Andreas Tille <tillea@rki.de> writes:
> the relevant line in src/Makefile.am is
>
> INCLUDES = -I$(top_srcdir)/include $(TCL_INCLUDE_SPEC) -I$(TK_PREFIX)/include
>
> I have no idea why TCL_INCLUDE_SPEC which is not propagated
> correctly to Makefile.in and thus cc has not the correct path
> to the needed includes.
The puzzling thing to me about this situation is what is expected
to set TK_PREFIX. "grep TK_PREFIX" in the wordnet directory
shows TK_PREFIX being used, but never defined anywhere. "grep
TK_PREFIX" in /usr/share/aclocal shows no hits at all.
Ditto for TCL_INCLUDE_SPEC.
What do you expect to set TK_PREFIX and TCL_INCLUDE_SPEC?
--
Ben Pfaff
http://benpfaff.org
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Sergei Golovan 2007-06-27, 1:22 pm |
| On 6/27/07, Ben Pfaff <blp@cs.stanford.edu> wrote:
> The puzzling thing to me about this situation is what is expected
> to set TK_PREFIX. "grep TK_PREFIX" in the wordnet directory
> shows TK_PREFIX being used, but never defined anywhere. "grep
> TK_PREFIX" in /usr/share/aclocal shows no hits at all.
>
> Ditto for TCL_INCLUDE_SPEC.
>
> What do you expect to set TK_PREFIX and TCL_INCLUDE_SPEC?
They are to be set by /usr/lib/tcl8.4/tclConfig.sh and
/usr/bin/tk8.4/tkConfig.sh. But something in configure process went
wrong.
--
Sergei Golovan
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Sergei Golovan 2007-06-27, 1:22 pm |
| On 6/27/07, Ben Pfaff <blp@cs.stanford.edu> wrote:
> The puzzling thing to me about this situation is what is expected
> to set TK_PREFIX. "grep TK_PREFIX" in the wordnet directory
> shows TK_PREFIX being used, but never defined anywhere. "grep
> TK_PREFIX" in /usr/share/aclocal shows no hits at all.
>
> Ditto for TCL_INCLUDE_SPEC.
>
> What do you expect to set TK_PREFIX and TCL_INCLUDE_SPEC?
If you look at line 20547 (and below) of configure script you'll see
that both tclConfig.sh and tkConfig.sh are sourced, but only few
variables defined in them are actually used. I think there's something
wrong with wordnet autoconf stuff.
--
Sergei Golovan
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Ben Pfaff 2007-06-27, 1:22 pm |
| "Sergei Golovan" <sgolovan@gmail.com> writes:
> On 6/27/07, Ben Pfaff <blp@cs.stanford.edu> wrote:
>
> They are to be set by /usr/lib/tcl8.4/tclConfig.sh and
> /usr/bin/tk8.4/tkConfig.sh. But something in configure process went
> wrong.
OK, I can see now that /usr/lib/tk8.4/tkConfig.sh sets TK_PREFIX
in the environment of "configure". But what is meant to
propagate this environment variable into the Makefile? I don't
see anything intended to do that. Autoconf does not
automatically propagate all environment variables from
"configure" into Makefiles (nor should it).
It looks to me like there's a missing piece in the build system.
--
Ben Pfaff
http://benpfaff.org
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Andreas Tille 2007-06-27, 7:20 pm |
| On Wed, 27 Jun 2007, Ben Pfaff wrote:
> OK, I can see now that /usr/lib/tk8.4/tkConfig.sh sets TK_PREFIX
> in the environment of "configure". But what is meant to
> propagate this environment variable into the Makefile? I don't
> see anything intended to do that. Autoconf does not
> automatically propagate all environment variables from
> "configure" into Makefiles (nor should it).
>
> It looks to me like there's a missing piece in the build system.
Yes, you both seem to come to the same conclusion as I myself - but
I have no idea how to fix this. There must be some trick to propagate
these variables, but how? I've got no clue out of reading the
texinfo docs.
Kind regards
Andreas.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Ben Pfaff 2007-06-27, 7:20 pm |
| Andreas Tille <tillea@rki.de> writes:
> Yes, you both seem to come to the same conclusion as I myself - but
> I have no idea how to fix this. There must be some trick to propagate
> these variables, but how? I've got no clue out of reading the
> texinfo docs.
That part is easy: just add
AC_SUBST([TK_PREFIX])
AC_SUBST([TCL_INCLUDE_SPEC])
to configure.ac and rerun autoconf and automake. I assumed you
were trying to figure out why it didn't work out-of-the-box.
Now the build fails at a link step on missing Tk symbols, but I
haven't looked into why. Quite possibly there's another missing
substitution.
(By the way, it also appears that
AC_LANGINFO_CODESET
in configure.ac should actually be
AM_LANGINFO_CODESET
although I'm not 100% certain.)
--
Ben Pfaff
http://benpfaff.org
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Azazel 2007-06-27, 7:20 pm |
| | |
| Daniel Schepler 2007-06-27, 7:20 pm |
| On Wednesday 27 June 2007 16:45:06 pm Andreas Tille wrote:
> On Wed, 27 Jun 2007, Ben Pfaff wrote:
>
> Yes, you both seem to come to the same conclusion as I myself - but
> I have no idea how to fix this. There must be some trick to propagate
> these variables, but how? I've got no clue out of reading the
> texinfo docs.
For example, AC_SUBST(TK_PREFIX), then make sure Makefile.in has a line
TK_PREFIX = @TK_PREFIX@
-- unless it's generated by automake, which will put in lines like that
automatically.
--
Daniel Schepler
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
|
|
|
|
|