Shachar Shemesh wrote:
Does anyone have any idea how to make sure the standard search paths are
simply not looked at?
Recompile the GCC you are using from scratch and give it a fixed
library/include patgh which is different from the system one.
The only problem you'll have left is with pac
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
On Tue, Sep 20, 2005 at 12:01:17PM +0300, Shachar Shemesh wrote:
> David D wrote:
>
> >Just shooting in the dark: chroot and gcc -L ?
> >
> >
> Chroot would require me to build another environment, just for the
> building. No thanks.
As was mentioned, there is a tool to do this - debian packag
David D wrote:
>Just shooting in the dark: chroot and gcc -L ?
>
>
Chroot would require me to build another environment, just for the
building. No thanks.
Shachar
=
To unsubscribe, send mail to [EMAIL PROTECTED] with
th
Just shooting in the dark: chroot and gcc -L ?
--- Shachar Shemesh <[EMAIL PROTECTED]> 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 w
On 9/20/05, Shachar Shemesh <[EMAIL PROTECTED]> 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 :-)
Hi Shachar,
There is this
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 belo
