Try running pkg-config with PKG_CONFIG_DEBUG_SPEW=1 set in your environ.
I get:
:; env PKG_CONFIG_DEBUG_SPEW=1 pkg-config --cflags xproto
, env PKG_CONFIG_DEBUG_SPEW=1 pkg-config --cflags xproto
| === many lines elided ===
| Path position of 'Xproto' is 2
| Package Xproto has
On Sat, Feb 21, 2009 at 10:42 AM, James Cloos cl...@jhcloos.com wrote:
(I had to compile pkg-config with -ggdb -O0 and try tracing thru to
discover the existance of PKG_CONFIG_DEBUG_SPEW.)
pkg-config(1):
...
ENVIRONMENT VARIABLES
...
PKG_CONFIG_DEBUG_SPEW
If set, causes
In libX11-6.2.1:
The configure piece below is wrong, (or pkg-config is buggy) because
pkg-config --cflags xproto
prints a line-feed only and keysymdef.h exists in my system and it is in
the right place.
I'm using pkg-config --version 0.23
#
# Find keysymdef.h
#
KEYSYMDEF=
for flag in
Pedro Izecksohn wrote:
pkg-config --cflags xproto
prints a line-feed only and keysymdef.h exists in my system and it is in
the right place.
Same here, on my local system (gentoo + X11 overlay). In my git tree it
gives a good-looking -I arg.
Though I never had problems building anything.
Simon Thum wrote:
Pedro Izecksohn wrote:
pkg-config --cflags xproto
prints a line-feed only and keysymdef.h exists in my system and it is in
the right place.
Same here, on my local system (gentoo + X11 overlay). In my git tree it
gives a good-looking -I arg.
Sorry for the noise. I haven't
On Thursday 19 February 2009 12:09:30 Simon Thum wrote:
Sorry for the noise. I haven't found the issue, but a majority of .pc's
in my system doesn't output cflags. So it's something configuration- or
pkc-config related.
In theory a lot of them shouldn't need to, because they're installed in a
Bill Crawford wrote:
In theory a lot of them shouldn't need to, because they're installed in a
subdirectory of /usr/include, and you're intended to include
libfoo/blah.h ...
I guessed that also, but couldn' get it nailed down. Anyway, it looks
more like the OP's script is broken.
On Thu, Feb 19, 2009 at 12:21 AM, Pedro Izecksohn
pedro.izecks...@gmail.com wrote:
In libX11-6.2.1:
The configure piece below is wrong, (or pkg-config is buggy) because
pkg-config --cflags xproto
prints a line-feed only and keysymdef.h exists in my system and it is in
the right place.
Who will fix it up there? Who has git write permission?
How none saw this before me? The original developers did not try configure?
This bugs affects thousands advanced users.
On 2/19/09, Dan Nicholson dbn.li...@gmail.com wrote:
On Thu, Feb 19, 2009 at 12:21 AM, Pedro Izecksohn
On Thu, Feb 19, 2009 at 10:45 AM, Pedro Izecksohn
pedro.izecks...@gmail.com wrote:
Who will fix it up there? Who has git write permission?
How none saw this before me? The original developers did not try configure?
Oh, I just looked in git and it's already been fixed for a while. It
should
It came from http://xlibs.freedesktop.org/release/
BTW: What is the logic behind xlibs version numbers?
On 2/19/09, Dan Nicholson dbn.li...@gmail.com wrote:
On Thu, Feb 19, 2009 at 10:45 AM, Pedro Izecksohn
pedro.izecks...@gmail.com wrote:
Who will fix it up there? Who has git write
On Thu, Feb 19, 2009 at 10:58 AM, Pedro Izecksohn
pedro.izecks...@gmail.com wrote:
It came from http://xlibs.freedesktop.org/release/
BTW: What is the logic behind xlibs version numbers?
Right, the old xlibs releases. You want the newer xorg releases. You
can find them all here:
Pedro Izecksohn wrote:
It came from http://xlibs.freedesktop.org/release/
BTW: What is the logic behind xlibs version numbers?
xlibs hasn't been used in many years - it was a brief experiment,
long ago abandoned.The libraries that are currently maintained
and relased are at:
13 matches
Mail list logo
