From: David Gaydou <dgaydou@gmail.com>
To: sid@sources.redhat.com
Subject: Re: Sid verbose trace reveals missing sid-control-tksm component - again
Date: Fri, 27 Feb 2009 13:59:00 -0000 [thread overview]
Message-ID: <loom.20090227T135554-625@post.gmane.org> (raw)
In-Reply-To: <y0mprh5nek5.fsf@ton.toronto.redhat.com>
hi,
> The config.log file should explain more about this problem.
I wasn't able to figure out what the problem is from this log-file.
> Another possibility is to remove the tcl & tk subdirectories
> from the sid tree (by renaming temporarily) to see if the
> system tcl libraries are deemed suitable.
to test this i made:
make distclean on /sid/component/tcl folder an then i repeted the process:
% cd /BUILDTREE
% /SOURCETREE/src/configure --prefix=/INSTALLTREE [OTHEROPTIONS]
% make all install
... still compiling... and it will be so for a long time.. :(
but in the meanwhile i found this:
--------------------------------------------------------------------------
dnl allow user to set this:
AC_ARG_WITH(tcl-lib, [ --with-tcl-lib=FLAG add FLAG to LIBS to find
tcl library])
AC_ARG_WITH(tcl-include, [ --with-tcl-include=FLAG add FLAG to CPPFLAGS to
find tcl headers])
AC_ARG_WITH(tk-lib, [ --with-tk-lib=FLAG add FLAG to LIBS to find tk
library])
AC_ARG_WITH(tk-include, [ --with-tk-include=FLAG add FLAG to CPPFLAGS to
find tk headers])
AC_ARG_WITH(blt-lib, [ --with-blt-lib=FLAG add FLAG to LIBS to find
blt library])
AC_ARG_WITH(blt-include, [ --with-blt-include=FLAG add FLAG to CPPFLAGS to
find blt headers])
--------------------------------------------------------------------------
in the configure.in file in the sid/component/tcl folder; since i don't kwon
much about auto-tools, i wanted to ask if that means that it is possible to pass
the path to tcl.h and tk.h files during configure or make steps.
Cheers.
prev parent reply other threads:[~2009-02-27 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 16:30 David Gaydou
2009-02-26 18:22 ` Frank Ch. Eigler
2009-02-26 18:58 ` David Gaydou
2009-02-26 20:12 ` Frank Ch. Eigler
2009-02-27 13:59 ` David Gaydou [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20090227T135554-625@post.gmane.org \
--to=dgaydou@gmail.com \
--cc=sid@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).