From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] sdkdir in xorg-server.pc
Date: Sun, 17 Feb 2013 23:08:54 +0100 [thread overview]
Message-ID: <87ehgemw3t.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <511D7A62.1040004@mind.be> (Arnout Vandecappelle's message of "Fri, 15 Feb 2013 00:59:30 +0100")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Arnout> Hi all,
Arnout> xorg-server.pc has the variables sdkdir=${prefix}/include/xorg and
Arnout> moduledir=${exec_prefix}/lib/xorg/modules. These are used by some Xorg
Arnout> packages to add to the include and library search path.
Arnout> We patch pkgconf to add the sysroot to the variables includedir,
Arnout> mapdir and libdir. Should we do something similar for sdkdir and
Arnout> moduledir? But of course, there's no end to that...
Indeed :/ I guess we have to..
Arnout> By the way, Peter, Thomas, do the autobuilders ever compile
Arnout> the full Xorg server? I don't see how
Arnout> xdriver_xf86-input-synaptics can ever build with this issue...
They should as long as the needed toolchain dependencies are
available (wchar/largefile/c++).
gcc10.fsffrance.org uses:
BR2_TOOLCHAIN_BUILDROOT_LARGEFILE=y
BR2_TOOLCHAIN_BUILDROOT_INET_IPV6=y
BR2_TOOLCHAIN_BUILDROOT_INET_RPC=y
BR2_TOOLCHAIN_BUILDROOT_WCHAR=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
So that should be sufficient. Gcc14/114 don't have C++. Thomas' glibc
toolchains should also catch it.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-02-17 22:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 23:59 [Buildroot] sdkdir in xorg-server.pc Arnout Vandecappelle
2013-02-17 22:08 ` Peter Korsgaard [this message]
2013-02-24 4:14 ` Thomas Petazzoni
2013-02-24 4:13 ` 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=87ehgemw3t.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.