| View previous topic :: View next topic |
| Author |
Message |
FiNCH
n00b
Joined: 06 Mar 2006
Posts: 33
|
 Posted: Sun Oct 22, 2006 10:14 pm Post subject: [SOLVED] gnome-vfsmm-2.x.x build errors |
 |
|
Hey guys, baffled here. I get this error when i build gnome-vfsmm-2.6.1 as well as gnome-vfsmm-2.12.0
| Code: | ../../libgnomevfs/libgnomevfsmm/mime-handlers.h:75: error: expected constructor, destructor, or type conversion before '*' token
make[4]: *** [mime-handlers.lo] Error 1
make[4]: *** Waiting for unfinished jobs....
i686-pc-linux-gnu-g++ -DHAVE_CONFIG_H -DG_LOG_DOMAIN=\"libgnomevfsmm\" -I../../ libgnomevfs -I../../libgnomevfs -pthread -DORBIT2=1 -I/usr/include/glibmm-2.4 -I /usr/lib/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/incl ude -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gnome-vfs -2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/gconf/2 -I/usr/include/orbi t-2.0 -I/usr/include/gnome-vfs-module-2.0 -O2 -march=athlon-xp -pipe -MT transfe r.lo -MD -MP -MF .deps/transfer.Tpo -c transfer.cc -fPIC -DPIC -o .libs/transfe r.o
make[4]: Leaving directory `/var/tmp/portage/dev-cpp/gnome-vfsmm-2.6.1/work/gnom e-vfsmm-2.6.1/libgnomevfs/libgnomevfsmm'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/var/tmp/portage/dev-cpp/gnome-vfsmm-2.6.1/work/gnom e-vfsmm-2.6.1/libgnomevfs/libgnomevfsmm'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/dev-cpp/gnome-vfsmm-2.6.1/work/gnom e-vfsmm-2.6.1/libgnomevfs'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/var/tmp/portage/dev-cpp/gnome-vfsmm-2.6.1/work/gnom e-vfsmm-2.6.1/libgnomevfs'
make: *** [all-recursive] Error 1
!!! ERROR: dev-cpp/gnome-vfsmm-2.6.1 failed.
Call stack:
ebuild.sh, line 1564: Called dyn_compile
ebuild.sh, line 937: Called src_compile
gnome-vfsmm-2.6.1.ebuild, line 32: Called gnome2_src_compile
gnome2.eclass, line 64: Called die |
I've seen this error all over the boards, and I've tried everything stated. Nothing in Bugzilla helps me either =/
Does anyone have any ideas?
Last edited by FiNCH on Sun Oct 22, 2006 10:35 pm; edited 1 time in total |
|
| Back to top |
|
 |
moocha
Watchman
Joined: 21 Oct 2003
Posts: 5722
|
| Posted: Sun Oct 22, 2006 10:19 pm Post subject: |
|
|
What's the version of gnome-base/gnome-vfs you have installed? I speculate it should match the version og gnome-vfsmm (at least in the major and minor version numbers), i.e. if you want gnome-vfsmm-2.6.1 you probably need gnome-vfs-2.6.x, for vfsmm-2.12.x you need vfs-2.12.x and so on.
Please note that it's pure speculation, though.
_________________
Military Commissions Act of 2006: http://tinyurl.com/jrcto
"Those who would give up essential liberty to purchase a little temporary safety deserve neither liberty nor safety."
-- attributed to Benjamin Franklin |
|
| Back to top |
|
|
FiNCH
n00b
Joined: 06 Mar 2006
Posts: 33
|
| Posted: Sun Oct 22, 2006 10:24 pm Post subject: |
|
|
Hey Moocha thanks for the quick reply 
Was actually just looking into that.
I have gnome-vfs-2.16.1 installed.
Another thing I should add to this, is when i tried to unmask gnome-vfsmm-2.16.0 and build it, i get this error:
| Code: | --- Invalid atom in /etc/portage/package.keywords: dev-cpp/gnome-vfsmm-2.16.0
--- Invalid atom in /etc/portage/package.keywords: dev-cpp/gnome-vfsmm-2.16.0
These are the packages that would be merged, in order:
Calculating dependencies
!!! All ebuilds that could satisfy "=dev-cpp/gnome-vfsmm-2.16.0" have been masked.
!!! One of the following masked packages is required to complete your request:
- dev-cpp/gnome-vfsmm-2.16.0 (masked by: package.mask)
# Daniel Gryniewicz <dang@gentoo.org> (06 Sep 2006)
# GNOME 2.16 mask for testing |
I'll look into that as of now, to see if I can figure that out (totally new to gentoo here if you can't tell =P) ...but in the meantime, any help would be appreciated And if anyone has any other ideas that would be great! |
|
| Back to top |
|
|
FiNCH
n00b
Joined: 06 Mar 2006
Posts: 33
|
| Posted: Sun Oct 22, 2006 10:34 pm Post subject: |
|
|
Well, I got it all fixed. Fell back to gnome-vfs-2.12.2, and I could build gnome-vfsmm-2.12.0 ...duh
Thanks moocha, you got me thinking in the right way 
Peace all. |
|
| Back to top |
|
|
moocha
Watchman
Joined: 21 Oct 2003
Posts: 5722
|
| Posted: Sun Oct 22, 2006 10:59 pm Post subject: |
|
|
Glad to hear you managed to fix it. Have fun!
_________________
Military Commissions Act of 2006: http://tinyurl.com/jrcto
"Those who would give up essential liberty to purchase a little temporary safety deserve neither liberty nor safety."
-- attributed to Benjamin Franklin |
|
| Back to top |
|
|
agnitio
Tux's lil' helper
Joined: 17 Apr 2004
Posts: 136
|
| Posted: Wed Nov 01, 2006 3:33 am Post subject: |
|
|
Unmasking gnome-vfsmm-2.16.0 also solves the problem.
FiNCH: you need to add a "=" before the line in /etc/portage/package.unmask if you specify a version number, like so:
| Code: |
=dev-cpp/gnome-vfsmm-2.16.0
|
That will take away that error message of yours |
|
| Back to top |
|
|
zurd
Apprentice
Joined: 17 Dec 2003
Posts: 228
Location: Canada, Montreal
|
| Posted: Tue Nov 07, 2006 12:10 am Post subject: |
|
|
Thanks for the information, putting in comments ">=dev-cpp/gnome-vfsmm-2.16.0"
from "/usr/portage/profiles/package.mask" solved the problem, now it installs gnome-vfsmm-2.16 instead of the 2.12 version.
This bug is also documented : https://bugs.gentoo.org/show_bug.cgi?id=147331 |
|
| Back to top |
|
|
agnitio
Tux's lil' helper
Joined: 17 Apr 2004
Posts: 136
|
| Posted: Tue Nov 07, 2006 12:27 am Post subject: |
|
|
| zurd wrote: | Thanks for the information, putting in comments ">=dev-cpp/gnome-vfsmm-2.16.0"
from "/usr/portage/profiles/package.mask" solved the problem |
That's not really a good way to do it. Changes in "/usr/portage/profiles/package.mask" will get overwritten on the next "emerge --sync".
Such modifications should always be made in "/etc/portage/package.*". |
|
| Back to top |
|
|
zurd
Apprentice
Joined: 17 Dec 2003
Posts: 228
Location: Canada, Montreal
|
| Posted: Tue Nov 07, 2006 2:06 am Post subject: |
|
|
| Quote: | That's not really a good way to do it. Changes in "/usr/portage/profiles/package.mask" will get overwritten on the next "emerge --sync".
Such modifications should always be made in "/etc/portage/package.*". |
So true, I just emerge --sync and it wants to re-emerge gnome-vfsmm-2.12 
So I've put ">=dev-cpp/gnome-vfsmm-2.16.0" in "/etc/portage/package.use" but doing emerge -Dup world shows that it wants to re-install the 2.12 version. I need to keep the 2.16 version.
What should I do to make the changes permanent? |
|
| Back to top |
|
|
Kuhndog86
Apprentice
Joined: 20 Jul 2004
Posts: 271
Location: Minnesota
|
| Posted: Tue Nov 07, 2006 10:33 pm Post subject: |
|
|
| put it in package.unmask instead of package.use |
|
| Back to top |
|
|
zurd
Apprentice
Joined: 17 Dec 2003
Posts: 228
Location: Canada, Montreal
|
| Posted: Wed Nov 08, 2006 2:03 am Post subject: |
|
|
Neat! That worked perfectly well, thanks for the info!  |
|
| Back to top |
|
|
j4miel
n00b
Joined: 26 Sep 2005
Posts: 54
|
| Posted: Tue Nov 14, 2006 12:34 pm Post subject: |
|
|
| Perhaps it is masked for a good reason? |
|
| Back to top |
|
|
david.stevenson
n00b
Joined: 13 Nov 2004
Posts: 68
Location: Wiltshire, England
|
| Posted: Tue Jan 23, 2007 12:17 am Post subject: |
|
|
late jan, and I was still having the same problem. But 2.16.0 is now keyworded not masked so it is easier.
| Code: | | echo "dev-cpp/gnome-vfsmm" >> /etc/portage/package.keywords |
_________________
David |
|
| Back to top |
|
|
|
Portage & Programming
