View previous topic :: View next topic |
Author |
Message |
Two meter troll n00b
Joined: 03 Jan 2008 Posts: 29 Location: oregon
|
Posted: Tue Jan 22, 2008 6:13 pm Post subject: Amarok error sort of(solved) |
|
|
*
* ERROR: sys-apps/hal-0.5.9.1-r3 failed.
* Call stack:
* ebuild.sh, line 1701: Called dyn_compile
* ebuild.sh, line 1039: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* hal-0.5.9.1-r3.ebuild, line 139: Called econf '--disable-policy-kit' '--docdir=/usr/share/doc/hal-0.5.9.1-r3' '--with-os-type=gentoo' '--with-pid-file=/var/run/hald.pid' '--with-socket-dir=/var/run/hald' '--with-hwdata=/usr/share/misc' '--enable-hotplug-map' '--enable-man-pages' '--with-backend=linux' '--disable-verbose-mode' '--without-dell-backlight' '--disable-parted' '--enable-pcmcia-support' '--enable-docbook-docs' '--enable-doxygen-docs' '--disable-selinux' '--disable-console-kit' '--enable-acpi-toshiba' '--enable-acpi-ibm'
* ebuild.sh, line 638: Called die
* The specific snippet of code:
* die "econf failed"
*
Any Ideas?
I should think i could emerge sys-apps-0.5.9.1-r3 all by its lonesome.
thanks in advance _________________ you can find a cause to die for on every street corner; its rare however to find a cause to live for. Keep looking!
Last edited by Two meter troll on Wed Jan 23, 2008 7:32 pm; edited 1 time in total |
|
Back to top |
|
|
djdunn l33t
Joined: 26 Dec 2004 Posts: 812
|
Posted: Tue Jan 22, 2008 6:20 pm Post subject: |
|
|
yeah it looks like your trying to emerge hal and you didnt really give anything usefull you would need to post the 10-20 lines above what you provided for anyone to be able to help you. _________________ “Music is a moral law. It gives a soul to the Universe, wings to the mind, flight to the imagination, a charm to sadness, gaiety and life to everything. It is the essence of order, and leads to all that is good and just and beautiful.”
― Plato |
|
Back to top |
|
|
Two meter troll n00b
Joined: 03 Jan 2008 Posts: 29 Location: oregon
|
Posted: Tue Jan 22, 2008 6:40 pm Post subject: 10 to twenty |
|
|
here you go.
checking if i686-pc-linux-gnu-gfortran PIC flag -fPIC works... yes
checking if i686-pc-linux-gnu-gfortran static flag -static works... yes
checking if i686-pc-linux-gnu-gfortran supports -c -o file.o... yes
checking whether the i686-pc-linux-gnu-gfortran linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether make sets $(MAKE)... (cached) yes
checking whether ln -s works... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for i686-pc-linux-gnu-pkg-config... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for python... /usr/bin/python
checking for python version... 2.4
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.4/site-packages
checking for python extension module directory... ${exec_prefix}/lib/python2.4/site-packages
checking sys/ioccom.h usability... no
checking sys/ioccom.h presence... no
checking for sys/ioccom.h... no
checking sys/inotify.h usability... yes
checking sys/inotify.h presence... yes
checking for sys/inotify.h... yes
checking gtk-doc version >= 1.3... yes
checking expat.h usability... yes
checking expat.h presence... yes
checking for expat.h... yes
checking for XML_ParserCreate in -lexpat... yes
checking for libusb-config... /usr/bin/libusb-config
checking for SMBIOSFreeMemory in -lsmbios... no
checking pci/pci.h usability... yes
checking pci/pci.h presence... yes
checking for pci/pci.h... yes
checking for pci_init in -lpci... yes
checking for DBUS... yes
checking for GLIB... yes
checking for VOLUME_ID... yes
checking for pgoff_t... no
checking for BLKGETSIZE64... yes
checking for getgrouplist... yes
checking for asprintf... yes
checking for mallopt... yes
checking for strndup... yes
checking for xmlto... /usr/bin/xmlto
checking whether to build DocBook documentation... checking for xmllint... /usr/bin/xmllint
yes
checking for intltool >= 0.22... 0.35.5 found
checking for perl... /usr/bin/perl
checking for XML::Parser... configure: error: XML::Parser perl module is required for intltool
!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! /var/tmp/portage/sys-apps/hal-0.5.9.1-r3/work/hal-0.5.9.1/config.log
*
temp/build.log lines 162-215/230 90% _________________ you can find a cause to die for on every street corner; its rare however to find a cause to live for. Keep looking! |
|
Back to top |
|
|
Veldrin Veteran
Joined: 27 Jul 2004 Posts: 1945 Location: Zurich, Switzerland
|
Posted: Tue Jan 22, 2008 6:50 pm Post subject: |
|
|
expat issue...
solution: reemerge XML-Parser, do a revdep-rebuild, continue with what you were doing
Code: | # emerge -1 XML-Parser
# revdep-rebuild -X -- -a |
revdep-rebuild is part of gentoolkit.
cheers
V. |
|
Back to top |
|
|
Two meter troll n00b
Joined: 03 Jan 2008 Posts: 29 Location: oregon
|
Posted: Tue Jan 22, 2008 11:18 pm Post subject: |
|
|
currently re-emerging amarok since that was the thing that failed so bad. so we will see if it will install this time out.
If it works i will edit the sub to solved if it dont i will be again asking for help.
thanks for the effort so far _________________ you can find a cause to die for on every street corner; its rare however to find a cause to live for. Keep looking! |
|
Back to top |
|
|
Two meter troll n00b
Joined: 03 Jan 2008 Posts: 29 Location: oregon
|
Posted: Wed Jan 23, 2008 4:11 am Post subject: |
|
|
bye bye Amarok
freekin slow and worthless pos these days. so off to unemerge it and get xmms.
thanks for the help any ways. sorry i took up your time _________________ you can find a cause to die for on every street corner; its rare however to find a cause to live for. Keep looking! |
|
Back to top |
|
|
Veldrin Veteran
Joined: 27 Jul 2004 Posts: 1945 Location: Zurich, Switzerland
|
Posted: Wed Jan 23, 2008 6:50 am Post subject: |
|
|
you should not use XMMS anymore - it's unmaintained and buggy.
use audacious - same look, but maintained.
just my .02$
V. |
|
Back to top |
|
|
Two meter troll n00b
Joined: 03 Jan 2008 Posts: 29 Location: oregon
|
Posted: Wed Jan 23, 2008 7:30 pm Post subject: |
|
|
thats what they say in the several threads about xmms but ive never had any problems with it and it works.
sorry im not on the band wagon about old or unmaintained tools. the same reason i wont give up my double bit ax for a wood splitter. No one makes the type of double bit i have but it still works and the wood splitter might work but it requires much more maintenance to keep it running.
qualitatively there is a vast difference between the old and simple with its bugs that i know; and the new and shiny with its bugs i don't know. if i wanted to run the buggy crap i would run ANY of the other linux distros. with gentoo i get to choose what i run. if this means i have to keep up an app that someone else has deemed unfit than i can do that.
IMO if Gentoo was concerned with how buggy an app was than all of the gecko web browsers would have been cut out of the tree as would several hundred other packages as it is gentoo devs seem concerned with who maintains a package. since i maintain my own software and i built this operating system then it is my choice to run things they may not like.
PS> these emoticons are sorta fun. _________________ you can find a cause to die for on every street corner; its rare however to find a cause to live for. Keep looking! |
|
Back to top |
|
|
|