Compilation error of Buildroot with X server
Hi.
First I have to explain that I'm new on this mailing list, beginner on Buildroot, and not a great specialist of Linux.
The situation : we use Buildroot to create a embedded distribution for a device with Touchscreen and a beautiful GUI.
We've just changed the hardware for the same model has before, but with a larger screen. So now it's seems impossible to manage display with only the framebuffer and Vesa drivers. So I must create a new version of the distribution which will allow me to install the specific driver of the graphic chipset.
As it's the same hardware (except screen, which only change size anyway), I took the old configurations file (for Kernel, Busybox, and Buildroot). I only add the option "Enable loadable module support" in Kernel configuration, so I'll can install my drivers.
In Buildroot configuration, I'm a bit lost but I only have to active X server. So I choose X Window system server "tinyX" instead of "none". Then I check "Xorg X window system X11r7 release 7.4" options, and choose xorg-server. And, that's all for a first test.
Here comes the problem. During compiling, I got the following error log. I think it is strange that it is searching for a file with a long path like this, which doesn't exists of course. The file /usr/local/toolchain/i486-twa-linux-gnu//usr/lib//libXau.la exists. I search for long hours but didn't found something really interesting. All I know is Libtool sometimes need to the librairies to be installed on the host to compile them successfully, so I just installed libXau but nothing changes.
I really think the path is the problem, but I don't know how to change it as I'm not familiar at all with Libtool.
Some advices for me?
libtool: link: warning: library
`/usr/local/toolchain/i486-twa-linux-gnu/usr/lib/libxcb-xlib.la' was moved.
grep:/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu//usr/lib//libXau.la:
No such file or directory/home/labo/matrice5/buildroot/toolchain_build_i486/bin/sed: can't read /usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu//usr/lib//libXau.la:
No such file or directory
libtool: link:
`/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu/usr/local/toolchain/i486-twa-linux-gnu//usr/lib//libXau.la' is not a valid libtool archive
make[4]: *** [libX11.la] Erreur 1
make[4]: quittant le r?pertoire ?/home/labo/matrice5/buildroot/build_i486/xlib_libX11-1.1.5/src ?
make[3]: *** [all-recursive] Erreur 1
make[3]: quittant le r?pertoire ?/home/labo/matrice5/buildroot/build_i486/xlib_libX11-1.1.5/src ?
make[2]: *** [all] Erreur 2
make[2]: quittant le r?pertoire ?/home/labo/matrice5/buildroot/build_i486/xlib_libX11-1.1.5/src ?
make[1]: *** [all-recursive] Erreur 1
make[1]: quittant le r?pertoire ?/home/labo/matrice5/buildroot/build_i486/xlib_libX11-1.1.5 ?
make: ***
[/home/labo/matrice5/buildroot/build_i486/xlib_libX11-1.1.5/.stamp_built]
Erreur 2
Thanks,
Damien Borie.
Hello Damien,
Quoted 7 lines · On Fri, 05 Mar 2010 16:36:20 +0100 Damien Borie <[email protected]> wrote:
The situation : we use Buildroot to create a embedded distribution for a device with Touchscreen and a beautiful GUI.
We've just changed the hardware for the same model has before, but with a larger screen. So now it's seems impossible to manage display with only the framebuffer and Vesa drivers. So I must create a new version of the distribution which will allow me to install the specific driver of the graphic chipset.
Ok.
Quoted 8 lines
As it's the same hardware (except screen, which only change size anyway), I took the old configurations file (for Kernel, Busybox, and Buildroot). I only add the option "Enable loadable module support" in Kernel configuration, so I'll can install my drivers.
In Buildroot configuration, I'm a bit lost but I only have to active X server. So I choose X Window system server "tinyX" instead of "none". Then I check "Xorg X window system X11r7 release 7.4" options, and choose xorg-server. And, that's all for a first test.
I think you're using an old version of Buildroot, because the options are now organized in a different way (I've cleaned them up because they were quite messy).
Now, we have a top-level option
[ ] X.org X Window System, X11R7, release 7.4
Inside this options, we have :
X Window System server type (TinyX) --->
X11R7 Servers --->
X11R7 Libraries --->
X11R7 Applications -->
X11R7 Fonts -->
X11R7 X Protocols -->
X11R7 Utilities -->
X11R7 Other data -->
So, once you've enabled X.org X Window System, X11R7, release 7.4, you are able to choose the server type, and there you have two choices :
* TinyX, which is in fact now known as Kdrive. It is a standalone X server, which only supports a few hardware access solutions:
framebuffer, VESA, etc. If you want video-card specific drivers, then, from my understanding, you cannot use TinyX/Kdrive
* The modular X.org, which is similar to the one you have in any Linux distro, which allows you to compile hardware-specific drivers. If you select this type, a new entry "X11R7 Drivers --->" will appear.
In your case, you probably want the modular X.org.
Quoted 8 lines
Here comes the problem. During compiling, I got the following error log. I think it is strange that it is searching for a file with a long path like this, which doesn't exists of course. The file
/usr/local/toolchain/i486-twa-linux-gnu//usr/lib//libXau.laexists. I search for long hours but didn't found something really interesting. All I know is Libtool sometimes need to the librairies to be installed on the host to compile them successfully, so I just installed libXau but nothing changes.
No, libtool doesn't need the libraries to be installed on the host. It might work-around some Buildroot issue, but it shouldn't be needed.
Quoted 3 lines
I really think the path is the problem, but I don't know how to change it as I'm not familiar at all with Libtool. Some advices for me?
Could you try with Buildroot 2010.02, and if it still doesn't work, send us your .config ?
Thanks!
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
OK. So I have restarted everything with the new buildroot version. I have started configuration from the beginning, but based on my old .config. Compilation has been long (QT...). Now I got a cleaner project! But finally, I have the same error exactly.
I forgot a detail : I use a external toolchain made with Crosstool, and, as it was working for the precedent target (and it's the same target), I used the same toolchain.
I join the .config. For all X11 parameters, I kept default.
Thanks.
Damien.
Thomas Petazzoni a ?crit :
Quoted 82 lines
Hello Damien,
Quoted 8 lines · On Fri, 05 Mar 2010 16:36:20 +0100 Damien Borie <[email protected]> wrote:
The situation : we use Buildroot to create a embedded distribution for a device with Touchscreen and a beautiful GUI.
We've just changed the hardware for the same model has before, but with a larger screen. So now it's seems impossible to manage display with only the framebuffer and Vesa drivers. So I must create a new version of the distribution which will allow me to install the specific driver of the graphic chipset.Ok.
Quoted 9 lines
As it's the same hardware (except screen, which only change size anyway), I took the old configurations file (for Kernel, Busybox, and Buildroot). I only add the option "Enable loadable module support" in Kernel configuration, so I'll can install my drivers.
In Buildroot configuration, I'm a bit lost but I only have to active X server. So I choose X Window system server "tinyX" instead of "none". Then I check "Xorg X window system X11r7 release 7.4" options, and choose xorg-server. And, that's all for a first test.I think you're using an old version of Buildroot, because the options are now organized in a different way (I've cleaned them up because they were quite messy).
Now, we have a top-level option
[ ] X.org X Window System, X11R7, release 7.4
Inside this options, we have :
X Window System server type (TinyX) --->
X11R7 Servers --->
X11R7 Libraries --->
X11R7 Applications -->
X11R7 Fonts -->
X11R7 X Protocols -->
X11R7 Utilities -->
X11R7 Other data -->So, once you've enabled X.org X Window System, X11R7, release 7.4, you are able to choose the server type, and there you have two choices :
* TinyX, which is in fact now known as Kdrive. It is a standalone X server, which only supports a few hardware access solutions:
framebuffer, VESA, etc. If you want video-card specific drivers, then, from my understanding, you cannot use TinyX/Kdrive* The modular X.org, which is similar to the one you have in any Linux distro, which allows you to compile hardware-specific drivers. If you select this type, a new entry "X11R7 Drivers --->" will appear.
In your case, you probably want the modular X.org.
Quoted 9 lines
Here comes the problem. During compiling, I got the following error log. I think it is strange that it is searching for a file with a long path like this, which doesn't exists of course. The file
/usr/local/toolchain/i486-twa-linux-gnu//usr/lib//libXau.laexists. I search for long hours but didn't found something really interesting. All I know is Libtool sometimes need to the librairies to be installed on the host to compile them successfully, so I just installed libXau but nothing changes.No, libtool doesn't need the libraries to be installed on the host. It might work-around some Buildroot issue, but it shouldn't be needed.
Quoted 4 lines
I really think the path is the problem, but I don't know how to change it as I'm not familiar at all with Libtool. Some advices for me?
Quoted 7 lines
Could you try with Buildroot 2010.02, and if it still doesn't work, send us your .config ?
Thanks!
Thomas
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: .config
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100309/46a04d45/attachment-0001.diff>
Oups, sorry, here is the correct .config.
Damien.
Damien Borie a ?crit :
Quoted 103 lines
OK. So I have restarted everything with the new buildroot version. I have started configuration from the beginning, but based on my old .config. Compilation has been long (QT...). Now I got a cleaner project! But finally, I have the same error exactly.
I forgot a detail : I use a external toolchain made with Crosstool, and, as it was working for the precedent target (and it's the same target), I used the same toolchain.
I join the .config. For all X11 parameters, I kept default.Thanks.
Damien.Thomas Petazzoni a ?crit :
Quoted 82 lines
Hello Damien,
Quoted 8 lines · On Fri, 05 Mar 2010 16:36:20 +0100 Damien Borie <[email protected]> wrote:
The situation : we use Buildroot to create a embedded distribution for a device with Touchscreen and a beautiful GUI.
We've just changed the hardware for the same model has before, but with a larger screen. So now it's seems impossible to manage display with only the framebuffer and Vesa drivers. So I must create a new version of the distribution which will allow me to install the specific driver of the graphic chipset.Ok.
Quoted 9 lines
As it's the same hardware (except screen, which only change size anyway), I took the old configurations file (for Kernel, Busybox, and Buildroot). I only add the option "Enable loadable module support" in Kernel configuration, so I'll can install my drivers. In Buildroot configuration, I'm a bit lost but I only have to active X server. So I choose X Window system server "tinyX" instead of "none". Then I check "Xorg X window system X11r7 release 7.4" options, and choose xorg-server. And, that's all for a first test.
I think you're using an old version of Buildroot, because the options are now organized in a different way (I've cleaned them up because they were quite messy).
Now, we have a top-level option
[ ] X.org X Window System, X11R7, release 7.4
Inside this options, we have :
X Window System server type (TinyX) --->
X11R7 Servers --->
X11R7 Libraries --->
X11R7 Applications -->
X11R7 Fonts -->
X11R7 X Protocols -->
X11R7 Utilities -->
X11R7 Other data -->So, once you've enabled X.org X Window System, X11R7, release 7.4, you are able to choose the server type, and there you have two choices :
* TinyX, which is in fact now known as Kdrive. It is a standalone X server, which only supports a few hardware access solutions:
framebuffer, VESA, etc. If you want video-card specific drivers, then, from my understanding, you cannot use TinyX/Kdrive* The modular X.org, which is similar to the one you have in any Linux distro, which allows you to compile hardware-specific drivers. If you select this type, a new entry "X11R7 Drivers --->" will appear.
In your case, you probably want the modular X.org.
Quoted 9 lines
Here comes the problem. During compiling, I got the following error log. I think it is strange that it is searching for a file with a long path like this, which doesn't exists of course. The file
/usr/local/toolchain/i486-twa-linux-gnu//usr/lib//libXau.laexists. I search for long hours but didn't found something really interesting. All I know is Libtool sometimes need to the librairies to be installed on the host to compile them successfully, so I just installed libXau but nothing changes.No, libtool doesn't need the libraries to be installed on the host. It might work-around some Buildroot issue, but it shouldn't be needed.
Quoted 4 lines
I really think the path is the problem, but I don't know how to change it as I'm not familiar at all with Libtool. Some advices for me?
Quoted 7 lines
Could you try with Buildroot 2010.02, and if it still doesn't work, send us your .config ?
Thanks!
Thomas
Quoted 6 lines
------------------------------------------------------------------------
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: .config
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100309/3e4a50e5/attachment-0001.diff>
I tried some changes in the configuration but with no results. But I think it must be a problem with my toolchain. So I made a new toolchain with latest version of Crosstool-ng. It's very long (about 18h). Unfortunately, when I've try a "make clean" in buildroot directory, to restart compilation at beginning, it deleted my newly created toolchain, whereas it's an external toolchain. I report this since I don't know if it's normal.
Here we go again for the toolchain compilation :(
If nothing changes with the new toolchain, I will need some help as I'm a bit lost in Buildroot Xorg/X11 configuration. So, if anybody has an idea to solve my problem...
Thanks.
Damien.
Damien Borie a ?crit :
Quoted 121 lines
Oups, sorry, here is the correct .config.
Damien.
Damien Borie a ?crit :
Quoted 103 lines
OK. So I have restarted everything with the new buildroot version. I have started configuration from the beginning, but based on my old .config. Compilation has been long (QT...). Now I got a cleaner project! But finally, I have the same error exactly.
I forgot a detail : I use a external toolchain made with Crosstool, and, as it was working for the precedent target (and it's the same target), I used the same toolchain.
I join the .config. For all X11 parameters, I kept default.Thanks.
Damien.Thomas Petazzoni a ?crit :
Quoted 82 lines
Hello Damien,
Quoted 8 lines · On Fri, 05 Mar 2010 16:36:20 +0100 Damien Borie <[email protected]> wrote:
The situation : we use Buildroot to create a embedded distribution for a device with Touchscreen and a beautiful GUI.
We've just changed the hardware for the same model has before, but with a larger screen. So now it's seems impossible to manage display with only the framebuffer and Vesa drivers. So I must create a new version of the distribution which will allow me to install the specific driver of the graphic chipset.Ok.
Quoted 9 lines
As it's the same hardware (except screen, which only change size anyway), I took the old configurations file (for Kernel, Busybox, and Buildroot). I only add the option "Enable loadable module support" in Kernel configuration, so I'll can install my drivers. In Buildroot configuration, I'm a bit lost but I only have to active X server. So I choose X Window system server "tinyX" instead of "none". Then I check "Xorg X window system X11r7 release 7.4" options, and choose xorg-server. And, that's all for a first test.
I think you're using an old version of Buildroot, because the options are now organized in a different way (I've cleaned them up because they were quite messy).
Now, we have a top-level option
[ ] X.org X Window System, X11R7, release 7.4
Inside this options, we have :
X Window System server type (TinyX) --->
X11R7 Servers --->
X11R7 Libraries --->
X11R7 Applications -->
X11R7 Fonts -->
X11R7 X Protocols -->
X11R7 Utilities -->
X11R7 Other data -->So, once you've enabled X.org X Window System, X11R7, release 7.4, you are able to choose the server type, and there you have two choices :
* TinyX, which is in fact now known as Kdrive. It is a standalone X server, which only supports a few hardware access solutions:
framebuffer, VESA, etc. If you want video-card specific drivers, then, from my understanding, you cannot use TinyX/Kdrive* The modular X.org, which is similar to the one you have in any Linux distro, which allows you to compile hardware-specific drivers. If you select this type, a new entry "X11R7 Drivers --->" will appear.
In your case, you probably want the modular X.org.
Quoted 9 lines
Here comes the problem. During compiling, I got the following error log. I think it is strange that it is searching for a file with a long path like this, which doesn't exists of course. The file
/usr/local/toolchain/i486-twa-linux-gnu//usr/lib//libXau.laexists. I search for long hours but didn't found something really interesting. All I know is Libtool sometimes need to the librairies to be installed on the host to compile them successfully, so I just installed libXau but nothing changes.No, libtool doesn't need the libraries to be installed on the host. It might work-around some Buildroot issue, but it shouldn't be needed.
Quoted 4 lines
I really think the path is the problem, but I don't know how to change it as I'm not familiar at all with Libtool. Some advices for me?
Quoted 7 lines
Could you try with Buildroot 2010.02, and if it still doesn't work, send us your .config ?
Thanks!
Thomas
Quoted 6 lines
------------------------------------------------------------------------
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot------------------------------------------------------------------------
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
Hi,
So, I finally successfully created my distribution. So if anybody encounter the same problems, I send my solution here.
In fact, the .la files, used by Libtool for linking libraries, were filled with bad paths. The error was to define the same path for the External Toolchain Location option and the Toolchain Header Location option. The second is where libraries are copied by Buildroot, and must be in the Buildroot tree. I don't know why, in my configuration, it was the path to my Toolchain (the 2 options had the same value). I never understood why the problem only comes with X libraries compilation and no with other libraries.
I reset this option to the default value (output/staging or something like that), and, it's work fine. I encountered some errors during Vesa drivers and XGI drivers compilation, but I resolved them (some include to modify in some .h files).
So now I got a working distribution.
Thanks,
Damien.
Damien Borie a ?crit :
Quoted 150 lines
I tried some changes in the configuration but with no results. But I think it must be a problem with my toolchain. So I made a new toolchain with latest version of Crosstool-ng. It's very long (about 18h).
Unfortunately, when I've try a "make clean" in buildroot directory, to restart compilation at beginning, it deleted my newly created toolchain, whereas it's an external toolchain. I report this since I don't know if it's normal.
Here we go again for the toolchain compilation :(
If nothing changes with the new toolchain, I will need some help as I'm a bit lost in Buildroot Xorg/X11 configuration. So, if anybody has an idea to solve my problem...Thanks.
Damien.Damien Borie a ?crit :
Quoted 118 lines
Oups, sorry, here is the correct .config.
Damien.
Damien Borie a ?crit :
Quoted 105 lines
OK. So I have restarted everything with the new buildroot version. I have started configuration from the beginning, but based on my old .config. Compilation has been long (QT...). Now I got a cleaner project!
But finally, I have the same error exactly.
I forgot a detail : I use a external toolchain made with Crosstool, and, as it was working for the precedent target (and it's the same target), I used the same toolchain.
I join the .config. For all X11 parameters, I kept default.Thanks.
Damien.Thomas Petazzoni a ?crit :
Quoted 83 lines
Hello Damien,
Quoted 8 lines · On Fri, 05 Mar 2010 16:36:20 +0100 Damien Borie <[email protected]> wrote:
The situation : we use Buildroot to create a embedded distribution for a device with Touchscreen and a beautiful GUI.
We've just changed the hardware for the same model has before, but with a larger screen. So now it's seems impossible to manage display with only the framebuffer and Vesa drivers. So I must create a new version of the distribution which will allow me to install the specific driver of the graphic chipset.Ok.
Quoted 9 lines
As it's the same hardware (except screen, which only change size anyway), I took the old configurations file (for Kernel, Busybox, and Buildroot). I only add the option "Enable loadable module support" in Kernel configuration, so I'll can install my drivers. In Buildroot configuration, I'm a bit lost but I only have to active X server. So I choose X Window system server "tinyX" instead of "none". Then I check "Xorg X window system X11r7 release 7.4" options, and choose xorg-server. And, that's all for a first test.
I think you're using an old version of Buildroot, because the options are now organized in a different way (I've cleaned them up because they were quite messy).
Now, we have a top-level option
[ ] X.org X Window System, X11R7, release 7.4
Inside this options, we have :
X Window System server type (TinyX) --->
X11R7 Servers --->
X11R7 Libraries --->
X11R7 Applications -->
X11R7 Fonts -->
X11R7 X Protocols -->
X11R7 Utilities -->
X11R7 Other data -->So, once you've enabled X.org X Window System, X11R7, release 7.4, you are able to choose the server type, and there you have two choices :
* TinyX, which is in fact now known as Kdrive. It is a standalone X server, which only supports a few hardware access solutions:
framebuffer, VESA, etc. If you want video-card specific drivers, then, from my understanding, you cannot use TinyX/Kdrive* The modular X.org, which is similar to the one you have in any Linux distro, which allows you to compile hardware-specific
drivers.
If you select this type, a new entry "X11R7 Drivers --->" will appear.In your case, you probably want the modular X.org.
Quoted 9 lines
Here comes the problem. During compiling, I got the following error log. I think it is strange that it is searching for a file with a long path like this, which doesn't exists of course. The file
/usr/local/toolchain/i486-twa-linux-gnu//usr/lib//libXau.laexists. I search for long hours but didn't found something really interesting. All I know is Libtool sometimes need to the librairies to be installed on the host to compile them successfully, so I just installed libXau but nothing changes.No, libtool doesn't need the libraries to be installed on the host. It might work-around some Buildroot issue, but it shouldn't be needed.
Quoted 4 lines
I really think the path is the problem, but I don't know how to change it as I'm not familiar at all with Libtool. Some advices for me?
Quoted 7 lines
Could you try with Buildroot 2010.02, and if it still doesn't work, send us your .config ?
Thanks!
Thomas
Quoted 7 lines
------------------------------------------------------------------------
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildrootQuoted 6 lines
------------------------------------------------------------------------
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
Hello,
Quoted 4 lines · On Thu, 18 Mar 2010 17:41:08 +0100 Damien Borie <[email protected]> wrote:
So, I finally successfully created my distribution. So if anybody encounter the same problems, I send my solution here.
In fact, the .la files, used by Libtool for linking libraries, were filled with bad paths. The error was to define the same path for the
Quoted 8 lines
External Toolchain Location option and the Toolchain Header Location option. The second is where libraries are copied by Buildroot, and must be in the Buildroot tree. I don't know why, in my configuration, it was the path to my Toolchain (the 2 options had the same value). I never understood why the problem only comes with X libraries compilation and no with other libraries.
I reset this option to the default value (output/staging or something like that), and, it's work fine.
Oh, yes, these are two very different things. The location were your external toolchain is installed could be read-only. We use this location for the cross-tools binaries (that we keep in this directory) and for the C library and headers (that we copy into the staging directory).
Maybe I should check that they are different ?
Quoted 3 lines
I encountered some errors during Vesa drivers and XGI drivers compilation, but I resolved them (some include to modify in some .h files). So now I got a working distribution.
Ok. After the 2010.02 release there has been a big update of all the X11-related packages, so maybe these issues are already solved.
Regards,
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com