Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Borie <dbe@terawatt.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Compilation error of Buildroot with X server
Date: Thu, 18 Mar 2010 17:41:08 +0100	[thread overview]
Message-ID: <4BA257A4.6040009@terawatt.fr> (raw)
In-Reply-To: <4B978247.3030707@terawatt.fr>

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 :
> 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 :
>> Oups, sorry, here is the correct .config.
>>
>> Damien.
>>
>> Damien Borie a ?crit :
>>> 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 :
>>>> Hello Damien,
>>>>
>>>> On Fri, 05 Mar 2010 16:36:20 +0100
>>>> Damien Borie <dbe@terawatt.fr> 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.
>>>>
>>>>  
>>>>> 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.
>>>>
>>>>  
>>>>> 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.
>>>>>     
>>>>
>>>> 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.
>>>>
>>>>  
>>>>> 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
>>>>   
>>>
>>> ------------------------------------------------------------------------ 
>>>
>>>
>>> _______________________________________________
>>> 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
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
>

  reply	other threads:[~2010-03-18 16:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-05 15:36 [Buildroot] Compilation error of Buildroot with X server Damien Borie
2010-03-07 10:21 ` Thomas Petazzoni
2010-03-09 13:52   ` Damien Borie
2010-03-09 14:10     ` Damien Borie
2010-03-10 11:28       ` Damien Borie
2010-03-18 16:41         ` Damien Borie [this message]
2010-03-19  8:33           ` Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BA257A4.6040009@terawatt.fr \
    --to=dbe@terawatt.fr \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox