[Fink-beginners] libxml2 build failure was Re: [gnome-core] qtiplot-qt4-mac 0.9.7.6-3 compiling failed

[Alexander H. <ale...@gm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 1/22/11 7:16 AM, Stefano Cappuzzo wrote:
> Hello,
> 
> I'm having some troubles compiling this programm: qtiplot-qt4-mac. I
> read the previous posts on fink-beginners, but I haven't found a
> solution that worked for me. I'm an absolute beginners, installed Fink
> for the first time the day before yesterday. 

Then let me educate you about what _not_ to post in bug reports as we go
along.  I accidentally approved your message on gnome-core because you
aren't subscribed there, which meant that we didn't get a message about
the contents being way over the desired length.

The fact that you eventually want qtiplot-qt4-mac is of no relevance to
the issue here.  libxml2 is the package which is failing to build, and
_that_ is what should be in the subject.

The first time I tried to
> compile qtiplot, it began downloading bunch of packets and then failed.
> The other times I tried it didn't download anything, 

That is because you have already downloaded the sources.

but failed anyhow.
> 
> Here's what I got from the first attempt. Following attempts didn't
> differ much, I guess...

The results of successive attempts are supposed to be identical,
provided that you don't change anything in between.  It probably would
have been better to send in the output of the _latest_ attempt.

> 
> 
> /Nautilus:~ ste$ fink install qtiplot-qt4-mac/
> /Password:/
> /Information about 9898 packages read in 0 seconds./
> /
> /
> /fink needs help picking an alternative to satisfy a virtual dependency.
> The candidates:/
> /
> /
> /(1)////db48-aes-shlibs: Shared Libraries for db48-aes/
> /(2)////db48-shlibs: Shared Libraries for db48/
> /
> /
> /Pick one: [1] /
> /The following package will be installed or updated:/
> / qtiplot-qt4-mac/
> /The following 118 additional packages will be installed:/
> / autoconf autoconf2.6 automake1.11 blt-dev blt-shlibs boost-jam
> boost1.35.nopython/
> / boost1.35.nopython-shlibs cmake compress-raw-bzip2-pm5100
> compress-raw-zlib-pm5100 crypt-ssleay-pm5100/
> / daemonic db48-aes db48-aes-shlibs dbus dbus1.3-dev dbus1.3-shlibs
> docbook-dsssl-nwalsh docbook-dtd/
> / docbook-xsl encode-pm5100 expat1 expat1-shlibs extutils-install-pm
> extutils-makemaker-pm5100/
> / extutils-manifest-pm fink-package-precedence flag-sort
> fontconfig-config fontconfig2-dev/
> / fontconfig2-shlibs freetype219 freetype219-shlibs gdbm3 gdbm3-shlibs
> getoptbin gettext-tools glib2-dev/
> / glib2-shlibs gnome-doc-utils gsl gsl-shlibs gtk-doc html-parser-pm5100
> html-tagset-pm intltool40/
> / io-compress-pm5100 kde4-buildenv lcms lcms-shlibs libgettext8-dev
> libidn libidn-shlibs libjpeg libjpeg-bin/
> / libjpeg-shlibs libjpeg8 libjpeg8-shlibs libmng2 libmng2-shlibs
> libncursesw5 libncursesw5-shlibs libpng14/
> / libpng14-shlibs libpng3 libpng3-shlibs librarian.08-shlibs libtiff
> libtiff-bin libtiff-shlibs libtool2/
> / libtool2-shlibs libwww-pm5100 libxml2 libxml2-bin libxml2-py26
> libxml2-shlibs libxslt libxslt-bin/
> / libxslt-shlibs m4 muparser muparser-shlibs openjade opensp4
> opensp4-dev opensp4-shlibs passwd pkgconfig/
> / python26 python26-shlibs qt4-mac qt4-mac-core-shlibs qt4-mac-designer
> qt4-mac-designer-shlibs qt4-mac-doc/
> / qt4-mac-gui-shlibs qt4-mac-linguist qwt-qt4-mac qwt-qt4-mac-shlibs
> rarian rarian-compat readline5/
> / readline5-shlibs sgml-entities-iso8879 sqlite3-dev sqlite3-shlibs
> system-openssl-dev tcltk tcltk-dev/
> / tcltk-shlibs texi2html texinfo uri-pm5100 xdg-base xinitrc
> xml-parser-pm5100/

<snip>
We almost never need to see the output from the download phase, unless
there is a failure in downloading a particular package.  And even in
that case, we just need the output from that package.

<snip>
cutting out irrelevant successful boost-jam build output.  In general,
only post output from the package which actually failed, not every other
package that got built before it.

<snip>
cutting out irrelevant successful build output from other packages, for
the same reason as the above.

> /Setting runtime build-lock.../
> /dpkg-deb -b /sw/src/fink.build/root-fink-buildlock-libxml2-2.7.8-102
> /sw/src/fink.build/
> /dpkg-deb: costruisco il pacchetto `fink-buildlock-libxml2-2.7.8-102' in
> `/sw/src/fink.build/fink-buildlock-libxml2-2.7.8-102_2011.01.20-18.47.24_darwin-i386.deb'./
> /Installing build-lock package.../
> //sw/bin/dpkg-lockwait -i
> /sw/src/fink.build/fink-buildlock-libxml2-2.7.8-102_2011.01.20-18.47.24_darwin-i386.deb/
> /Selezionato il pacchetto fink-buildlock-libxml2-2.7.8-102, che non lo era./
> /(Lettura del database ... 31834 file e directory attualmente installati.)/
> /Spacchettamento di fink-buildlock-libxml2-2.7.8-102 (da
> .../fink-buildlock-libxml2-2.7.8-102_2011.01.20-18.47.24_darwin-i386.deb) .../
> /Configuro fink-buildlock-libxml2-2.7.8-102 (2011.01.20-18.47.24) .../
> /
> /

<snip>

> ///./.deps/HTMLparser.Plo uses /usr/local/include/zconf.h/
> ///./.deps/HTMLparser.Plo uses /usr/local/include/zlib.h/
> /Please fix build process to get consistent use of fink's headers./

The problem is noted above.

> /### execution of fink-package-precedence failed, exit code 255/
> /Removing runtime build-lock.../
> /Removing build-lock package.../
> //sw/bin/dpkg-lockwait -r fink-buildlock-libxml2-2.7.8-102/
> /(Lettura del database ... 31835 file e directory attualmente installati.)/
> /Rimozione di fink-buildlock-libxml2-2.7.8-102 .../
> /Updating the list of locally available binary packages./
> /Scanning dists/unstable/main/binary-darwin-i386/



<snipping irrelevant "New package ..." section.>
These lines aren't errors, but indicate what new packages got built
successfully.

> /Failed: phase compiling: libxml2-2.7.8-102 failed/
> /
> /

Also, we prefer plain text formatting.

> That's all.
> 
> Thanks in advance, have a nice weekend
> 
> Stefano C
> 
> 
> 

Generally, we like to have some system information, such as:

OS version and architecture, which you can get from "fink -V | head n3"
Xcode version, which you can get from "fink list xcode"

In this case, however, the problem is that you have stuff in /usr/local,
as noted in the output, which often will lead to problems in Fink builds:

http://www.finkproject.org/faq/comp-general.php?phpLang=en#usr-local-libs

So rename /usr/local temporarily and try the build again.  You may get
some errors, however, in packages which you built previously and which
have linked to /usr/local .

- -- 
Alexander Hansen, Ph.D.
Fink User Liaison
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEUEARECAAYFAk08RKcACgkQB8UpO3rKjQ9M1gCXdI/uD7oUg58FaDVUCCKJLtyR
FgCeJPt6bCGnEwoDCr4nu3rzsfpKYTI=
=wdak
-----END PGP SIGNATURE-----