Gary Thomas wrote:
> Juergen Beisert wrote:
>> Gary,
>>
>> On Friday 02 November 2007 14:27, Gary Thomas wrote:
>>>> Better use the OSELAS.Toolchain-Project. It supports more recent
>>>> toolchains, the crosstool part is outdated.
>>> I got started on this, but ran into some troubles.  The GCC snapshot
>>> gcc-4.2-20070207 is no longer available, so I tried to build the tools
>>> using the released version of gcc-4.2.2.  This went pretty well, until
>>> I tried to build busybox:
>>>
>>> /opt/OSELAS.Toolchain-1.1.0/i586-unknown-linux-gnu/gcc-4.2.2-glibc-2.5-kern
>>> el-2.6.18/sysroot-i586-unknown-linux-gnu/usr/include/sys/syscall.h:32:27:
>>> error: bits/syscall.h: No such file or directory
>> Hmm, GCC 4.2.2 in OSELAS.Toolchain-1.1.0? Did you select this version of gcc 
>> by your own? Perhaps you should start with GCC 4.1.2 from the 
>> OSELAS.Toolchain-1.1.0 project. Or wait for our next OSELAS.Toolchain 
>> release. This also should support GCC 4.2.
> 
> As mentioned, I tried to select the configuration which uses
> gcc-4.2-20070207, but that is no longer available, so I tried
> to use the released version gcc-4.2.2
> 
> I'm trying 4.1.2 now.
>

Sadly, I get the same error.

/opt/OSELAS.Toolchain-1.1.0/i586-unknown-linux-gnu/gcc-4.1.2-glibc-2.5-kernel-2.6.18/sysroot-i586-unknown-linux-gnu/usr/include/sys/syscall.h:32:27:
error: bits/syscall.h: No such file or directory

Has anyone successfully built an i586 toolchain and then used
it to build ptxdist-1.0.1 (OSELAS.BSP-Pengutronix-GenericI586Glibc-3)?

>>> So, it looks like some pieces are missing.
>>>
>>> Any ideas? help?
>> I guess GCC 4.2.2 misses some patches to work correctly in 
>> OSELAS.Toolchain-1.1.0.
> 
> I don't see any patches that deal with these [missing] include files.
> 
> Thanks
> 


-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Reply via email to