ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltib] what is the need for the autoconf tools in /opt/ltib/usr/bin?


From: Stuart Hughes
Subject: Re: [Ltib] what is the need for the autoconf tools in /opt/ltib/usr/bin?
Date: Fri, 28 Oct 2011 08:54:16 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110922 Lightning/1.0b2 Thunderbird/3.1.15

Hi  Peter,

Many questions, see inline:

On 27/10/11 16:02, Peter Barada wrote:
On 10/27/2011 04:13 AM, Stuart Hughes wrote:
Hi  Jurgen,

I think in your case you may need to adjust your PATH variable in the
.spec file when running configure so that you pick up your hosts
autotools for this package.

Unfortunately there is a need for the autotools in /opt/ltib/...
although I can't recall which package needs it (I do have notes
somewhere though).

Is there any chance of updating git in LTIB? The version in git is really old compared to current versions distributed with Ubuntu, and it causes problems when trying to use git to pull out branches of a packages while building (i.e. building a package from an SCM as opposed to from tarball/patches).


Yes, I don't think that would break anything.

Also bison and flex in LTIB are also quite old and cause problems when building hostapd and libnl-2.0 to bring up soft AP wireless systems...

Unfortunately from what I remember, there are other packages that need these versions, which is why they got put into /opt/ltib. Can't completely remember if both has package dependencies or not.

Granted I know I'm in a breadline begging for toast, but how can I teach ltib to remove a host package if its no longer called out for in config/userspace/ltib.preconfig? Then it should be relatively easy to disable flex/bison and add them to pre_install_deps, remove .host_wait_warning* and the next "./ltib" should clean things up in /opt/ltib/user/bin...


You can run ./ltib --hostcf --configure and that will let you configure what goes into the host support packages without having to touch .host_wait_*

Be warned though that because it goes through the config system, the dependencies for packages get evaluated, so some other packages you didn't expect may get pulled in.

Note: with --hostcf, you can do all the normal ltib stuff, with a few provisos.

Thanks in advance!

Regards, Stuart



reply via email to

[Prev in Thread] Current Thread [Next in Thread]