Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Heidelberg <markus.heidelberg@web.de>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package: audio/libogg audio/libvorbis docker edit etc...
Date: Mon, 27 Oct 2008 07:59:27 +0100	[thread overview]
Message-ID: <200810270759.28374.markus.heidelberg@web.de> (raw)
In-Reply-To: <87r663f91t.fsf@macbook.be.48ers.dk>

Peter Korsgaard, 26.10.2008:
> >>>>> "Markus" == Markus Heidelberg <markus.heidelberg@web.de> writes:
> 
> Hi,
> 
>  >> -					PKGCONFIG="$(STAGING_DIR)/usr/bin/pkg-config" \
>  >> -					PKG_CONFIG_SYSROOT="$(STAGING_DIR)" \
>  >> -					PKG_CONFIG_PATH="$(STAGING_DIR)/usr/lib/pkgconfig"
>  >> +					LDFLAGS="-L$(STAGING_DIR)/usr/lib -L$(STAGING_DIR)/lib"
> 
>  Markus> I think this will break docker, because MAKE_OPT is affected,
>  Markus> not CONF_OPT.  And I just noticed that docker doesn't use
>  Markus> autotools at all.
> 
> Yes, I re-added PKG_CONFIG=.. in r23796 - With that, it works for me.

After looking into it again, the package seems a bit broken. `$(PKG_CONFIG)
--cflags glib-2.0` evaluates to "-I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include", not the ones in staging_dir, so it uses the
system include files. PKG_CONFIG_PATH has to be defined and
PKG_CONFIG_SYSROOT_DIR, too. But it also uses the staging files hardcoded in
the Makefile. Then have a look at XLIBPATH in the Makefile, which points to
the system files. And LDFLAGS is never used.

Markus

  reply	other threads:[~2008-10-27  6:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-26  6:19 [Buildroot] svn commit: trunk/buildroot/package: audio/libogg audio/libvorbis docker edit etc jacmet at uclibc.org
2008-10-26 12:57 ` Markus Heidelberg
2008-10-26 12:13   ` Peter Korsgaard
2008-10-26 13:37 ` Markus Heidelberg
2008-10-26 18:10   ` Markus Heidelberg
2008-10-26 19:30   ` Peter Korsgaard
2008-10-27  6:59     ` Markus Heidelberg [this message]
2008-10-27  9:12       ` Peter Korsgaard

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=200810270759.28374.markus.heidelberg@web.de \
    --to=markus.heidelberg@web.de \
    --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