Mail Archives: geda-user/2013/12/31/12:28:19
On Tue, 31 Dec 2013, al davis wrote:
> On Tuesday 31 December 2013, gavin bowlby wrote:
>> I see the following error message after doing a:
>>
>> ./configure --prefix=/usr
>
> This is typical behavior when the configure script finds
> something missing. Usually what you need to do is look in a
> file, I think it is something like "config.log". Look at the
> stuff near the end of the file, and try to make sense of it.
>
> There you will see the actual output of what the script did
> along the way. Usually this will hint at something missing.
> Now you need to find out what package provides that, if any, and
> install it. It is common to go through several iterations of
> this. Welcome to autoconf.
>
> On ubuntu and debian, you can use the "dpkg" and "apt-cache"
> tools to try to match up a file to a package containing it.
On Debian based systems:
apt-cache search pattern <- when you know (partial) package name (e.g. "tcl")
apt-file search pattern <- when you know a file name (e.g. "/usr/lib/libtcl")
dpkg -S pattern <- figure out which package installed a file on your system
once you know the package name:
apt-get install package
Most projects are split in multiple packages. The plain foo contains the
binary only, for when you want to run it; foo-dev contains the headers and
extras if you want to compile against a lib; there are sometimes foo-doc
for the documentation.
Major versions usually have different packages that can be installed in
parallel; tcl8.4, tcl8.6; install both or install the one the config
script is looking for.
TL;DR: apt-get install tcl8.4-dev most probably fixes the problem about a
missing libtcl.
Regards,
Tibor
- Raw text -