Re: [Ltib] Ubuntu 11.10 install issues (was Re: LTIB build error: lkc package build errors with unresolved symbols)

[Stuart Hughes]

Hi everyone,

I've checked-in changes that make a number of fixes needed for Ubuntu
11.10.  To get these, do:

cvs up -dP

If you have a failed install, you'll need to do:

sudo rm -rf /opt/ltib/usr/src/rpm/BUILLD/*

and then re-try the build with:

./ltib

It works for me.

Regards, Stuart

On 01/11/11 17:30, Mike Goins wrote:
> On Tue, Nov 1, 2011 at 1:19 PM, Stuart Hughes <address@hidden> wrote:
>> Hi Andrew,
>>
>> Good catch, that looks like the issue.  I'll poke around in lkc and see if I
>> can move -lncurses to the right place.
> 
> 
> Can you stomp over it with something like?
> CFLAGS="$CFLAGS -Wl,--no-as-needed"
> 
> 
> Though this may not guarantee that --no-as-needed would be later in
> the arg list than --as-needed.
> 
> 
>> Regards, Stuart
>>
>> On 01/11/11 14:49, Andrew Craig wrote:
>>>
>>> I am getting the same errors here in 11.10 as well.  After a bit of
>>> looking around perhaps this explains the cause?
>>>
>>> http://ubuntuforums.org/archive/index.php/t-1833136.html
>>>
>>> Quote:
>>> "just for future reference as this is a common problem:
>>>
>>> oneiric uses the linker flag --as-needed by default. With this flag
>>> correct ordering of libraries and objects on the commandline is important.
>>> objects needing symbols must be placed before libraries providing them.
>>> E.g. file.o and staticlib.a need symbols from libm:
>>> wrong:
>>> gcc -lm file.o staticlib.a
>>> gcc will think libm is not needed and drops it, when it later encounters
>>> the objects needing it you will get undefined references
>>> right:
>>> gcc file.o staticlib.a -lm
>>>
>>> Important for autotools makefiles. Place libraries into LIBS or LDADD
>>> variables, not in LDFLAGS"
>>>
>>> So moving where -lncurses is in the command might fix the problem?
>>>
>>> -------------
>>> Andrew
>>>
>>> On 31/10/2011 6:48 PM, Stuart Hughes wrote:
>>>>
>>>> Hi Guys,
>>>>
>>>> I've checked-in a fix for the --force-debian flag.  It seems to be
>>>> something they put in for a while and removed later (but using it as a
>>>> test does not return an error, sigh).
>>>>
>>>> As far as the lkc missing symbol errors go, I can repeat this too, but
>>>> have not yet had time to look at (and likely won't have time for several
>>>> days).  If anyone else has time to dig into this I'd appreciate it.
>>>>
>>>> Regards, Stuart
>>>>
>>>> On 31/10/11 09:37, Stuart Hughes wrote:
>>>>>
>>>>> Hi Guys,
>>>>>
>>>>> I've installed 11.10 and I'm looking into this on the train this evening
>>>>> while commuting.  I'll let you know what I find.
>>>>>
>>>>> Regards, Stuart
>>>>>
>>>>> On 30/10/11 20:12, Fritz Mueller wrote:
>>>>>>
>>>>>> I am seeing exactly the same thing on Ubuntu 11.10, but haven't had a
>>>>>> chance to investigate.  The failing gcc line includes "-lncurses", and
>>>>>> a readelf on /usr/lib/libncurses.a shows defs for the unresolved
>>>>>> symbols.  Haven't had time to investigate it further than that yet.
>>>>>>
>>>>>> There is some evidence of this having happened to folks on previous
>>>>>> releases of Ubuntu, also; a google turned up, for
>>>>>> example
>>>>>> http://www.linuxquestions.org/questions/linux-software-2/failure-to-install-ltib-on-jaunty-jackalope-9-04-a-771464/
>>>>>>
>>>>>> I also ran into the rpmdb --force-debian problem under Ubuntu that was
>>>>>> reported here previously.  It's strange that the script explicitly
>>>>>> checks for this, but still falls over (I hardwired the test to fail in
>>>>>> the script to work around it temporarily, then ran into the lkc/curses
>>>>>> problem.)
>>>>>>
>>>>>> cheers,
>>>>>>   --FritzM.
>>>>>>
>>>>>> On Oct 30, 2011, at 8:27 AM, Stuart Hughes wrote:
>>>>>>
>>>>>>> Hi Nagesh,
>>>>>>>
>>>>>>> I've not seen this before, what host platform are you on?
>>>>>>>
>>>>>>> Regards, Stuart
>>>>>>>
>>>>>>> On 30/10/11 06:09, Nagesh A wrote:
>>>>>>>>
>>>>>>>> Hi all,
>>>>>>>> I am new to ltib and trying to configure LTIB for the first time.
>>>>>>>> I am facing below error.
>>>>>>>>
>>>>>>>> It seems that the errors are because of "unresolved symbols" while
>>>>>>>> linking lkc build.
>>>>>>>>
>>>>>>>> Please find attached host_config.log.
>>>>>>>>
>>>>>>>> regards,
>>>>>>>> -Nagesh A
>>>>>>>>
>>>> _______________________________________________
>>>> LTIB home page: http://ltib.org
>>>>
>>>> Ltib mailing list
>>>> address@hidden
>>>> https://lists.nongnu.org/mailman/listinfo/ltib
>>>>
>>>
>>>
>>> _______________________________________________
>>> LTIB home page: http://ltib.org
>>>
>>> Ltib mailing list
>>> address@hidden
>>> https://lists.nongnu.org/mailman/listinfo/ltib
>>
>>
>> _______________________________________________
>> LTIB home page: http://ltib.org
>>
>> Ltib mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/ltib
>>
> 
> _______________________________________________
> LTIB home page: http://ltib.org
> 
> Ltib mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/ltib
>