Re: [ptxdist] Testing 1.0.1
Juergen Beisert wrote: Gary, On Friday 02 November 2007 17:53, Gary Thomas wrote: 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:2 7: 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-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 Has anyone successfully built an i586 toolchain and then used it to build ptxdist-1.0.1 (OSELAS.BSP-Pengutronix-GenericI586Glibc-3)? Attached my toolchain I'm using for my x86 terminal projects. But it has to be built with ptxdist-0.10.6! And note: All OSELAS.Toolchains in 1.1.0 are tested with ptxdist-0.10.6 only. I took your toolchain setup and rebuilt using 0.10.6, then I tried my [default] configuration on 1.0.1 and got the same result :-( /opt/OSELAS.Toolchain-1.1.0/i586-pmmx-linux-gnu/gcc-4.1.2-glibc-2.5-kernel-2.6.18/sysroot-i586-pmmx-linux-gnu/usr/include/sys/syscall.h:32:27: error: bits/syscall.h: No such file or directory Juergen - perhaps you could put your actual toolchain on my FTP site? -- Gary Thomas | Consulting for the MLB Associates |Embedded world -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] Testing 1.0.1
Hi Gary, On Sunday 04 November 2007 18:41, Gary Thomas wrote: Juergen Beisert wrote: On Friday 02 November 2007 17:53, Gary Thomas wrote: 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 :2 7: 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-k ern 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 Has anyone successfully built an i586 toolchain and then used it to build ptxdist-1.0.1 (OSELAS.BSP-Pengutronix-GenericI586Glibc-3)? Attached my toolchain I'm using for my x86 terminal projects. But it has to be built with ptxdist-0.10.6! And note: All OSELAS.Toolchains in 1.1.0 are tested with ptxdist-0.10.6 only. I took your toolchain setup and rebuilt using 0.10.6, then I tried my [default] configuration on 1.0.1 and got the same result :-( /opt/OSELAS.Toolchain-1.1.0/i586-pmmx-linux-gnu/gcc-4.1.2-glibc-2.5-kernel- 2.6.18/sysroot-i586-pmmx-linux-gnu/usr/include/sys/syscall.h:32:27: error: bits/syscall.h: No such file or directory Does this directory exists on your host? /opt/OSELAS.Toolchain-1.1.0/i586-pmmx-linux-gnu/gcc-4.1.2-glibc-2.5-kernel-2.6.18/sysroot-i586-pmmx-linux-gnu/usr/include/bits Can you send me your logfile (should exists in the root directory of your project when you are trying to build it). And the logfile from the toolchain build. Maybe it could help to find the mistake in your environment. What kind of linux system do you use? Juergen - perhaps you could put your actual toolchain on my FTP site? Yes. On the way... Juergen -- Dipl.-Ing. Juergen Beisert | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Handelsregister: Amtsgericht Hildesheim, HRA 2686 Vertretung Sued/Muenchen, Germany Phone: +49-8766-939 228 | Fax: +49-5121-206917-9 -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] Testing 1.0.1
Juergen Beisert wrote: Hi Gary, On Sunday 04 November 2007 18:41, Gary Thomas wrote: Juergen Beisert wrote: On Friday 02 November 2007 17:53, Gary Thomas wrote: 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 :2 7: 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-k ern 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 Has anyone successfully built an i586 toolchain and then used it to build ptxdist-1.0.1 (OSELAS.BSP-Pengutronix-GenericI586Glibc-3)? Attached my toolchain I'm using for my x86 terminal projects. But it has to be built with ptxdist-0.10.6! And note: All OSELAS.Toolchains in 1.1.0 are tested with ptxdist-0.10.6 only. I took your toolchain setup and rebuilt using 0.10.6, then I tried my [default] configuration on 1.0.1 and got the same result :-( /opt/OSELAS.Toolchain-1.1.0/i586-pmmx-linux-gnu/gcc-4.1.2-glibc-2.5-kernel- 2.6.18/sysroot-i586-pmmx-linux-gnu/usr/include/sys/syscall.h:32:27: error: bits/syscall.h: No such file or directory Does this directory exists on your host? /opt/OSELAS.Toolchain-1.1.0/i586-pmmx-linux-gnu/gcc-4.1.2-glibc-2.5-kernel-2.6.18/sysroot-i586-pmmx-linux-gnu/usr/include/bits Can you send me your logfile (should exists in the root directory of your project when you are trying to build it). And the logfile from the toolchain build. Maybe it could help to find the mistake in your environment. What kind of linux system do you use? Logfile(s) attached. I'm using Fedora Core 7 That file definitely exists - at least for other toolchains that I have built (even ones using ptxdist!) Juergen - perhaps you could put your actual toolchain on my FTP site? Yes. On the way... Thanks, I'll try this tomorrow and see if this works. -- Gary Thomas | Consulting for the MLB Associates |Embedded world -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] Testing 1.0.1
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. 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
Re: [ptxdist] Testing 1.0.1
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
Re: [ptxdist] Testing 1.0.1
Hi Gary, On Thursday 01 November 2007 16:26, Gary Thomas wrote: Gary Thomas wrote: I'm interested in testing 1.0.1, using a stand-alone PC as a WWW kiosk for an example. It's unclear to me all the steps I need to follow. I've downloaded the 1.0.1 release, along with the patches and I'm using the 1.0.0 projects (there is no 1.0.1 project set although the install notes said there would be). I also downloaded the CrossTool project (http://www.pengutronix.de/oselas/crosstool/download/OSELAS.Crosstool-1.0 .1.tar.gz) Better use the OSELAS.Toolchain-Project. It supports more recent toolchains, the crosstool part is outdated. Here are the steps I think I need to take: * Build a set of cross-tools (I know that for a standard PC as the target this isn't strictly necessary) * Configure my target - Basic, simple, stand-alone environment - Including X + firefox * Build * Deploy - Initially using an NFS root file system for testing Correct. Did you download one of the OSELAS.BSPs from our website? Their quickstart guide you through the steps how to get a toolchain, get the project to be built and get the target up and running. These steps are always required and they do not depend on the architecture. I've downloaded all of the application notes. While these are useful, they don't quite give me enough to complete the task above. n.b. I've been using ptxdist since 0.6 days and deploy it on my embedded targets (PPC) all the time, but I have limited experience with the new version (1.0.1) and never anything as ambitious as what I've outlined above. Any help/pointers/guidance graciously accepted. Thanks BTW, once I get this all figured out, I'm planning on writing a tutorial/guide which I'll be glad to donate/publish. Sounds great. I wrote most of the other app notes and I need some help to keep them up to date and add some useful information into them. So please write down your questions to create some kind of FAQ or generic quickstart. Juergen -- Dipl.-Ing. Juergen Beisert | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Handelsregister: Amtsgericht Hildesheim, HRA 2686 Vertretung Sued/Muenchen, Germany Phone: +49-8766-939 228 | Fax: +49-5121-206917-9 -- ptxdist mailing list ptxdist@pengutronix.de
