On 4/22/12 2:35 PM, Jeremy Huntwork wrote:
> On 4/22/12 2:25 PM, Jeremy Huntwork wrote:
>> On 4/22/12 2:23 PM, DJ Lucas wrote:
>>> As it turns out, it was a problem with the host. /usr/lib64/libgpm.so is
>>> not a symlink, but rather a linker script that points to another linker
>>> script that points to an invalid destination (ie: no 64bit libgpm). I
>>> was going to close as invalid, but then I wondered if we want our
>>> chapter 5 ncurses linked to something that does not exist in the chroot
>>> environment?
>>
>> Yes, that's the point, we don't - and I don't think the chapter 5
>> toolchain should even be aware of what is in /usr so if it is, there's a
>> problem somewhere.
>
> I was just able to reproduce your issue. Going to dig in a bit more now
> and see if we can't find out why it's being found at all.

This is why it's seeing it:

checking if you want to link with the GPM mouse library... maybe
checking for gpm.h... yes

echo 'main(){}' | /tools/bin/gcc -x c - -v -Wl,--verbose

...
#include "..." search starts here:
#include <...> search starts here:
  /mnt/lfs/build/tools/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.7.0/include
 
/mnt/lfs/build/tools/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.7.0/include-fixed
  /tools/include
  /usr/include
End of search list.
...

JH
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to