Make cross-tc artificially incompatible w/ host system

[Enrico Weigelt]

Hi folks,


I'm running sysroot'ed cross-builds for x86 targets on x86 boxes.
So it's often possible (when libc+co match) that the built programs
might run on the host.

For QM reasons I'd like to have any build breaking, that ever tries 
to run the freshly built binaries later in the build process.
(yes, there are several packages doing such insane crap ;-o).

Is there a way to let the toolchain artificially produce binaries 
that wont run on the host system, even if they normally would ?
Maybe something like using a different libc.so name, etc ?


cu
-- 
----------------------------------------------------------------------
 Enrico Weigelt, metux IT service -- http://www.metux.de/

 phone:  +49 36207 519931  email: weigelt@metux.de
 mobile: +49 151 27565287  icq:   210169427         skype: nekrad666
----------------------------------------------------------------------
 Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------

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