This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Toolchain has UID dependency


>  the WORKING user:
>
>  ignoring nonexistent directory
> "/home/bomr/x-tools/arm-unknown-linux-gnu/lib/gcc/arm-unknown-linux-gnu/4.1.2/include"
>  ignoring nonexistent directory
> "/home/bomr/x-tools/arm-unknown-linux-gnu/arm-unknown-linux-gnu/include"
>
>  ...then, the compilation and linkage completes.
>
>  the NON-WORKING user:
>
>  cc1: error:
> /home/bomr/x-tools/arm-unknown-linux-gnu/lib/gcc/arm-unknown-linux-gnu/4.1.2/include:
> Permission denied
>  cc1: error:
> /home/bomr/x-tools/arm-unknown-linux-gnu/arm-unknown-linux-gnu/include:
> Permission denied
>
>  Compilation quits with error.

Let me guess... /home/bomr exists and is not accessible to anyone
other than bomr,
so bomr can follow the long path and fails when it can see that a
certain directory does not exist, while any other user can't look in
/home/bomr, so can't see whether the dir exists or not, hence 2
different errors, one of which is trapped and ignored, the other of
which is considered fatal.

>  So, is there a way to make the cross compiler NOT look there?

Your answer is to get the /home/bomr stuff out of the toolchain you
are installing.
It has no business being in there - you should be installing in
/usr/local or /opt or somewhere like that.

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]