ltib
[Top][All Lists]
Advanced

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

Re: [Ltib] NM revision in tool chain


From: Stuart Hughes
Subject: Re: [Ltib] NM revision in tool chain
Date: Tue, 09 Aug 2011 08:49:57 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.18) Gecko/20110617 Lightning/1.0b2 Thunderbird/3.1.11

Hi Chris,


Further up in the output (when configure ran) it probably had some output 
mentioning trying to detect nm (maybe for the target).  This will have failed, 
so  you need to look at the test and figure out why it failed and if it is 
fixable.


If it's not fixable, you can probably just add this to your configure line:

lt_cv_path_NM=nm \
./configure ....the.rest.of.your.configure.line

In the spoofed environment (i.e. %build) nm will be bound to the spoofed target 
nm by the adjusted search path.

Regards Stuart



On 08/08/11 20:17, Chris Westervelt wrote:
Stuart,

I forced the following as you mentioned and this works

lt_cv_path_NM=/opt/ltib/usr/spoof/nm \

So the real question (since i got this from 'which nm' in LTIP shell mode) is 
why wouldnt the auto detect  script in configure not work for nm?
________________________________________
From: Stuart Hughes address@hidden
Sent: Monday, August 08, 2011 2:55 PM
To: Chris Westervelt
Cc: address@hidden
Subject: Re: [Ltib] NM revision in tool chain

Hi Chris,

What you're doing is probably incorrect unless the nm is supposed to be
running against host architecture object files.

Normally I'd expect nm to be spoofed (e.g. intercepted to call the
arch-linux-nm version so it can munge (technical word) the object files
correctly for the target architecture.

If you could send some output from a failing build it may throw some
light on the issue.

Regards, Stuart

On 08/08/11 16:45, Chris Westervelt wrote:
Stuart,



I am in the process of producing an upgrade to Gstreamer and its plugins
to version 0.10.28.  I also have to upgrade other support libraries as
well.  The one common denominator I am running into that prevents
libtool from working is the current tool chains NM.  If I patch by
preempting the configure in the spec files with
“lt_cv_path_NM=/usr/bin/nm \” I can get the packages to build.  My
question is am I doing this the right way?  I want to submit all this
work to the project but I want to insure I have a solution that everyone
can benefit from.  I am building on Ubuntu 10.04.  This may not be the
best location for all platforms.  Your thoughts.



*Chris Westervelt*

*Senior Product Development Engineer*

*Infrasafe, Inc.
12612 Challenger Pkwy
Suite 300
Orlando, FL
32826*

*http://www.infrasafe.com<http://www.infrasafe.com/>
Office:   (407) 926-6983*

*Mobile: (407) 595-7023
Fax:    (407) 857-1635*
*Notice of Confidentiality:*
This e-mail communication and the attachments hereto, if any, are
intended solely for the information and use of the addressee(s)
identified above and may contain information which is legally privileged
and/or otherwise confidential. If a recipient of this e-mail
communication is not an addressee (or an authorized representative of an
addressee), such recipient is hereby advised that any review,
disclosure, reproduction, re-transmission or other dissemination or use
of this e-mail communication (or any information contained herein) is
strictly prohibited. If you are not an addressee and have received this
e-mail communication in error, please advise the sender of that
circumstance either by reply e-mail or by telephone at (800) 238-2686,
immediately delete this e-mail communication from any computer and
destroy all physical copies of same.**





_______________________________________________
LTIB home page: http://ltib.org

Ltib mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/ltib




reply via email to

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