Mario Charest wrote:
> 
>> -----Original Message-----
>> From: Neil Schellenberger [mailto:community-noreply@qnx.com]
>> Sent: May-13-09 12:40 PM
>> To: general-toolchain
>> Subject: Re: strip
>>
>> Strictly speaking that's the target strip, isn't it?  (Although I can't
>> think of anything NTO specific in it.)
>>
> Under host that's a host binary no?

It is a host binary that strips target binaries. We don't ship target 
binutils except for x86 self hosted.

>> On the host side, the Linux strip should work just fine (for host, i.e.
>> Linux, objects).
> 
> I tried but it corrupted nto executables.

I have a pretty good guess why this happens, but it's not really 
important. You should use the Neutrino binutils for Neutrino binaries.

Regards,

Ryan Mansfield

On Wed, 2009-05-13 at 13:05 -0400, Mario Charest wrote:
> 
> > -----Original Message-----
> > From: Neil Schellenberger [mailto:community-noreply@qnx.com]
> > Sent: May-13-09 12:40 PM
> > To: general-toolchain
> > Subject: Re: strip
> > 
> > Strictly speaking that's the target strip, isn't it?  (Although I can't
> > think of anything NTO specific in it.)
> > 
> Under host that's a host binary no?

Strictly speaking its a host binary which strips target objects (e.g.
the ntoppc-strip runs on the x86 Linux host but strips files meant for
NTO PPC targets; likewise ntox86-strip runs on the x86 Linux host but
strips files meant for NTO x86 targets).

> 
> > On the host side, the Linux strip should work just fine (for host, i.e.
> > Linux, objects).
> 
> I tried but it corrupted nto executables.

I'm not too surprised (there are a couple of NTO specific bits-n-pieces
in our binaries).  As I mentioned, the host (x86 Linux) strip will work
fine for host (x86 Linux) objects - but doesn't work for target (NTO
x86) objects.

Ah, the joys of cross compiling. ;-)