Debugging Compiler Issues

[Gavin Kavanaugh]

Arnaud,
Thank you for the quick reply.  I had not even tried linking statically 
so I am doing that now.

I have tried LD_LIBRARY_PATH unsuccessfully.  When I set it to my new 
library path, suddenly my commands stop working (i.e. ls, cd ). I end up 
with problems since my system needs the existing libraries, but I want 
the application to run with the new ones. I hope that the static linking 
will resolve this.

Thanks,
Gavin

On 8/6/2010 10:09 AM, Arnaud Lacombe wrote:
> Hi,
>
> On Fri, Aug 6, 2010 at 12:47 PM, Gavin Kavanaugh<zeddicus76@gmail.com>  wrote:
>    
>> First of all I love the crosstool-NG. I used the original one years ago and
>> I didn't have any idea it was being updated and maintained. Nice work.
>>
>> I ran across the update because I am trying to dig into an issue and it
>> seems like I should be able to do it with crosstool-NG. If anyone can help
>> me out I would greatly appreciate it.
>>
>> The problem is that I have an application that is running on many different
>> distributions. But when I run it on the latest openSUSE 11.3 release I get
>> an assert at start up. After some local debugging I find that this assert is
>> showing up before I even get to the main function of my app. I have done
>> enough debugging to be fairly certain that this issue is in glibc, or gcc.
>>   So what I wanted to do was set up a build so I could build gcc, glibc, and
>> whatever else I needed to a specific version and see if the issue
>> reproduces. Then I can tweak the library versions to help me determine the
>> root cause.
>>
>> I think what I want is to use crosstool-NG to generate a native compiler,
>> but that is not supported(?). Instead I have generated a cross-compiler
>> which is for my host machine. I am able to compile my application using this
>> new cross-compiler, but running it just leads to problems because of library
>> dependency. I thought about setting up a chroot environment for my new
>> toolchain but I have not done this before and I'm not sure it's the best
>> solution either.
>>
>> Hopefully that is enough detail to get my point across. Does anyone know how
>> to set this up?
>>
>>      
> did you try to link your application statically to avoid using any
> system library ? Alternatively, you can override the standard system
> library with your own (provided by the test compiler) with
> LD_LIBRARY_PATH/LD_PRELOAD.
>
>   - Arnaud
>    

--
For unsubscribe information see http://sourceware.org/lists.html#faq