pixman 0.21.6 missing configure
ptxmac opened this issue · comments
The current version of pixman (0.21.6) doesn't have a ./configure
script, instread is have a ./autogen.sh
script.
Also, this version requires autoconf 2.62 or higher.
Hello,
Can you try running: aclocal
and then autoreconf -f -i -Wall,no-obsolete
? I manage to run ./configure
afterwards.
No, are you using a newer verison of aclocal
?
==> aclocal
configure.ac:62: error: Autoconf version 2.62 or higher is required
Care to provide both $ brew doctor
and $ brew --config
?
I find this strange. I downloaded this: http://cgit.freedesktop.org/pixman/snapshot/pixman-0.21.6.tar.bz2 and could successfully use the commands above.
oh, I was using a wrong version of automake, now autoconf works, but the configure script fails:
./configure: line 13040: PKG_PROG_PKG_CONFIG: command not found
./configure: line 13114: syntax error near unexpected token GTK,' ./configure: line 13114:
PKG_CHECK_MODULES(GTK, gtk+-2.0 pixman-1)'
(I'm installing GTK as we speak)
Do you have pkg-config installed?
yes, from pixman: depends_on 'pkg-config' => :build
OK.
May I ask you to add depends_on 'glibc
? Reading over at Arch Linux: http://projects.archlinux.org/svntogit/packages.git/tree/pixman/trunk/PKGBUILD
They have set GLibc as dependency.
So, installing gtk didn't help (and it shouldn't as pixman.rb have --enable-gtk=no
in configure call.
There are no glibc package in homebrew...
Been trying to make it compile, but I'm not sure how to fix this.
Will look into more later. Care to try if the 0.20.x series it better: http://cgit.freedesktop.org/pixman/snapshot/pixman-0.20.2.tar.bz2
Unfortunately, the 0.20 series also use autoconf 2.62, so it's the same problem
I suspect this issue to be the cause #3209? Maybe try to include the path.
That solves the problem!
Unfortunately that means editing non-homebrew files.
Good.
Care to try 09dcaa7 however?
yes, that fixes it!
Should be obvious to use the stable version ;)
Good :) Then I will submit it for merge.
Great, maybe poke the person who updated the url in the first place?
That would be the almighty @adamv ;)