On Tue, Sep 20, 2005 at 11:07:56AM +0300, Shachar Shemesh wrote: > Hi all, > > I'm trying to set up a build environment for a self-contained Linux > system. This is not cross-compiling, but I want the new system to only > contain what I brought into it. I also want it to work :-) > > I'm already compiling everything I need, but now I want to make sure > that nothing that belongs to the build environment will be accidentally > used by the built programs. When a program does an "include", I want to > make sure it gets a file from my directories. Same goes for included > libraries. > > Now, I did find "-nostdinc" and "-i" for gcc. I'm hoping I'll manage to > get them to do what I want for the compile part of the program. What I'm > still trying to figure out, however, is whether there is any such thing > for the linker. I'm playing with "-Y", but it doesn't seem to be 100% > what I'm looking for. > > Does anyone have any idea how to make sure the standard search paths are > simply not looked at?
Hm. A simple solution would be to strace gcc and grep for any 'forbidden paths'. Should be quite definitive. Anyway, we did the exact same thing in one of our projects. ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
