Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Make problem on 64-bit linux with CS 2009q1
Date: Fri, 9 Dec 2011 19:37:29 +0100	[thread overview]
Message-ID: <20111209193729.0cc88e6e@skate> (raw)
In-Reply-To: <4EE1CB14.9010802@free.fr>

Hello Guillaume,

Le Fri, 09 Dec 2011 09:47:16 +0100,
Guillaume Gardet <guillaume.gardet@free.fr> a ?crit :

> I tried a simple build (.config in attachment) on a 64-bit Linux
> (openSUSE 12.1) with CS 2009q1 toolchain (and last buildroot trunk)
> and some libs are built to output/target/usr/lib64/ so they are not
> found as dependencies. With the .config in attachment, you can try a
> build and check directfb config.log file and PNG lib and others are
> not found, so directfb is built without support for them. In the
> final image, they are also in usr/lib64 folder. It may be a problem
> for other packages.
> 
> What could be the problem and how to solve it?

Yeah, we had report of issues with openSUSE. I guess it's the multilib
implementation in openSUSE that confuses Buildroot somehow. I need to
get my hand on an openSUSE system to debug this.

Can you easily provide me a basic chroot environment with openSUSE
installed in it, or point me to the documentation to set it up
(knowing, of course, that I don't have openSUSE installed here, so I
can't use openSUSE specific utilities to build the openSUSE chroot) ?

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2011-12-09 18:37 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-09  8:47 [Buildroot] Make problem on 64-bit linux with CS 2009q1 Guillaume Gardet
2011-12-09 18:37 ` Thomas Petazzoni [this message]
2011-12-09 21:40   ` Peter Korsgaard
2011-12-09 22:45     ` Peter Korsgaard
2011-12-09 23:27       ` Trevor Woerner
2011-12-10 10:06         ` Guillaume Gardet
2011-12-10 19:27           ` Peter Korsgaard
2011-12-12  8:23         ` Guillaume Gardet
2011-12-12  9:15           ` Peter Korsgaard
2011-12-12 10:13             ` Guillaume Gardet
2011-12-12 10:17               ` Thomas Petazzoni
2011-12-12 10:26                 ` Guillaume Gardet
2011-12-12 17:52                 ` Trevor Woerner
2011-12-12 19:43                   ` Peter Korsgaard
2011-12-14  7:08                     ` Arnout Vandecappelle
2011-12-14  8:31                       ` Thomas Petazzoni
2011-12-14  8:41                         ` Peter Korsgaard
2011-12-14  8:42                       ` Peter Korsgaard
2011-12-12 10:35               ` Peter Korsgaard
2011-12-12 10:42                 ` Guillaume Gardet
2011-12-12 12:19           ` Trevor Woerner
2011-12-10 10:01     ` Guillaume Gardet
2011-12-10 19:28       ` Peter Korsgaard
2011-12-12  8:25         ` Guillaume Gardet
2011-12-10 10:28   ` Guillaume Gardet

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=20111209193729.0cc88e6e@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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