Summary: | glademm-0.6.2 fails to build | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rigo <rigo> |
Component: | Current packages | Assignee: | Nick Hadaway <grandmasterlinux> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | gabriele_giorgetti, jap1, lostlogic, mholzer |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Rigo
2002-07-02 14:20:21 UTC
I Can verify this Sorry Seemant, but I'm still with gcc-2.95 and I can't verify this one. I forgot to throw this one back into the pool. Gabriele,
Sorry, the reporter's problem was with gcc-3.1. I am running gcc-2.95.3, and I
get this:
Calculating world dependencies ...done!
>>> emerge dev-util/glademm-0.6.2 to /
>>> md5 ;-) glademm-0.6.2.tar.gz
>>> Unpacking source...
>>> Unpacking glademm-0.6.2.tar.gz
>>> Source unpacked.
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
checking for a BSD compatible install... /bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for i686-pc-linux-gnu-g++... i686-pc-linux-gnu-g++
checking for C++ compiler default output... configure: error: C++ compiler
cannot create executables
!!! ERROR: The ebuild did not complete successfully.
!!! Function src_compile, Line 5, Exitcode 77
!!! (no error message)
!!! emerge aborting on /usr/portage/dev-util/glademm/glademm-0.6.2.ebuild .
I am running gcc-2.95.3 and glademm-0.6.2 builds just fine.
(so you know that it works under certain circumstances :-) )
Calculating dependencies ...done!
>>> emerge dev-util/glademm-0.6.2 to /
>>> md5 ;-) glademm-0.6.2.tar.gz
>>> Unpacking source...
>>> Unpacking glademm-0.6.2.tar.gz
>>> Source unpacked.
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
checking for a BSD compatible install... /bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for i686-pc-linux-gnu-g++... no
checking for i686-pc-linux-gnu-c++... no
checking for i686-pc-linux-gnu-gpp... no
checking for i686-pc-linux-gnu-aCC... no
checking for i686-pc-linux-gnu-CC... no
checking for i686-pc-linux-gnu-cxx... no
checking for i686-pc-linux-gnu-cc++... no
checking for i686-pc-linux-gnu-cl... no
checking for i686-pc-linux-gnu-FCC... no
checking for i686-pc-linux-gnu-KCC... no
checking for i686-pc-linux-gnu-RCC... no
checking for i686-pc-linux-gnu-xlC_r... no
checking for i686-pc-linux-gnu-xlC... no
checking for g++... g++
checking for C++ compiler default output... a.out
checking whether the C++ compiler works... yes
checking whether we are cross compiling... no
checking for executable suffix...
checking for object suffix... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
and so on.
ok I steel this, and give to raker and or myself :) I'm pretty sure it is a gcc-3.1 stupid c++ issue, give us a while :) directly from http://www.gnome.org "NOTE: glade-- 1.1.0+ is usable for both Gnome and Gnome2!" Is there a specific reason for sticking with glademm 0.6.2? In that "while" I'll test glade-- 1.1.0+ to see if it works with Gnome1/2 as stated... it appears that glade-- 1.1.0c compiles fine and works with glade 0.6.4 at least on my system. :) Should we unmask glade--??? I have already heard 2 reports of it working fine. I think we should mask out glademm and unmask libglademm and make things that depend on glademm .6.2 depend on libglademm instead :) there are only 3 packages with this dependency that will need to be changed. what are those 3 programs that need to be changed to utilize libglademm instead of glademm? The only program that appeared to be leftover which depended on glademm was anjuta. Currently there is a 0.9.99 beta ebuild (thank you stroke!) of anjuta masked in portage. The currently unmasked (0.1.9) build of anjuta does not build corretly in the current state of libraries in the portage tree... Maybe we should unmask the new version? Are there any other programs that I am missing here or can we call this bug resolved with an anjuta update? Sorry for the late reaction...Just tried glademm-1.1.0c & 1.1.1b and I can confirm 1.1.0c compiles...1.1.1.b failed: image.cc: In member function `void Gtk_Image::EmbedImage(CxxFile&, const std::string&) const': image.cc:171: `ifstream' undeclared (first use this function) image.cc:171: (Each undeclared identifier is reported only once for each function it appears in.) image.cc:171: parse error before `(' token image.cc:172: `is' undeclared (first use this function) make[3]: *** [image.o] Error 1 make[3]: Leaving directory `/var/tmp/portage/glademm-1.1.1b/work/glademm-1.1.1b/src/writers' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/glademm-1.1.1b/work/glademm-1.1.1b/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/glademm-1.1.1b/work/glademm-1.1.1b' make: *** [all] Error 2 !!! ERROR: The ebuild did not complete successfully. !!! Function src_compile, Line -158, Exitcode 2 !!! (no error message) Regards, Rigo is this still a issue ? 1.1.1c is in portage tree >>> Regenerating /etc/ld.so.cache... >>> dev-util/glademm-1.1.1c merged. >>> Recording dev-util/glademm in "world" favorites file... dev-util/glademm selected: none protected: 1.1.1c omitted: none >>> clean: No packages selected for removal. >>> Regenerating /etc/ld.so.cache... >>> Auto-cleaning packages ... >>> No outdated packages were found on your system. * GNU info directory index is up-to-date. * IMPORTANT: 1 config files in /etc need updating. * Type emerge --help config to learn how to update config files. |