From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0003734]: dbus-glib fails to compile for a i686 platform
Date: Fri, 13 Jun 2008 08:53:39 -0700 [thread overview]
Message-ID: <5dff5ebcb4fe2ebd338e4e803faad0f2@bugs.uclibc.org> (raw)
The following issue has been SUBMITTED.
======================================================================
http://busybox.net/bugs/view.php?id=3734
======================================================================
Reported By: KHAksnes
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 3734
Category: Shared Library Support
Reproducibility: always
Severity: block
Priority: normal
Status: assigned
======================================================================
Date Submitted: 06-13-2008 08:53 PDT
Last Modified: 06-13-2008 08:53 PDT
======================================================================
Summary: dbus-glib fails to compile for a i686 platform
Description:
The build of dbus-glib seems to look for several libraries in
build_i686/staging_dir/lib instead of build_i6i6/staging_dir/usr/lib
This is the case for recent svn versions of buildroot Explicit paths to
files
on the form lib*.so is used instead of -L and -l
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
06-13-08 08:53 KHAksnes New Issue
06-13-08 08:53 KHAksnes Status new => assigned
06-13-08 08:53 KHAksnes Assigned To => buildroot
======================================================================
next reply other threads:[~2008-06-13 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 15:53 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-26 9:43 [Buildroot] [buildroot 0003734]: dbus-glib fails to compile for a i686 platform bugs at busybox.net
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=5dff5ebcb4fe2ebd338e4e803faad0f2@bugs.uclibc.org \
--to=bugs@busybox.net \
--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