new totem .99.19 won't compile at all

Professor Frink

Here's the error message I get:

In file included from /usr/include/netdb.h:28,
from /usr/include/gnome-vfs-2.0/libgnomevfs/gnome-vfs-address.h:31,
from /usr/include/gnome-vfs-2.0/libgnomevfs/gnome-vfs.h:28,
from totem-disc.c:38:
/usr/include/netinet/in.h:354: error: syntax error before '(' token
/usr/include/netinet/in.h:354: error: syntax error before "__u32"
/usr/include/netinet/in.h:355: error: syntax error before '(' token
/usr/include/netinet/in.h:355: error: syntax error before "__u16"
/usr/include/netinet/in.h:357: error: syntax error before '(' token
/usr/include/netinet/in.h:357: error: syntax error before "__u32"
/usr/include/netinet/in.h:359: error: syntax error before '(' token
/usr/include/netinet/in.h:359: error: syntax error before "__u16"
make[2]: *** [totem-disc.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory `/var/tmp/portage/totem-0.99.19/work/totem-0.99.19/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/totem-0.99.19/work/totem-0.99.19'
make: *** [all-recursive-am] Error 2

!!! ERROR: media-video/totem-0.99.19 failed.
!!! Function gnome2_src_compile, Line 40, Exitcode 2
!!! compile failure
!!! If you need support, post the topmost build error, NOT this status message.

Any ideas? These are the flags I'm using
[ebuild U ] media-video/totem-0.99.19 [0.99.8-r2] -debug +gstreamer* -lirc +mad 0 kB
_________________
"You've got to listen to me. Elementary chaos theory tells us that all robots will eventually turn against their masters and run amok in an orgy of blood, and kicking and the biting with the metal teeth and the hurting and shoving."

anybody · n00b Joined: 14 Sep 2003 Posts: 32

I got exactly the same problem and have no idea how to fix this.

Totem 0.99.8-r2 emerged fine.

boilersuit · n00b Joined: 13 Oct 2004 Posts: 28 Location: England

Same here. Totem is on it's arse.

RSay · Posted: Tue Nov 16, 2004 4:30 am Post subject:

Ditto, it stopped me too :cry:

llsardonicll · Tux's lil' helper Joined: 07 Oct 2004 Posts: 110

Totem 0.99.20 works flawlessly on my system. Just rename the ebuild and digest it.

Pip101 · n00b Joined: 30 Mar 2004 Posts: 62 Location: UK

Just tried that and I get the same error

OPelerin · Guru Joined: 17 Jul 2004 Posts: 354 Location: Belgium

Same for me. I even changed make.conf flags from pentium4 to pentium3 to pentium2 No changes. It always fails
_________________
Olivier PELERIN

mr_clark · n00b Joined: 13 Feb 2004 Posts: 14

Ditto for me. Gettting exactly the same error.

Anybody find a solution yet?

Kabuto · l33t Joined: 01 Aug 2002 Posts: 701

No problem here with same use flags. 'emerge info'?

jwalcik · n00b Joined: 22 Sep 2003 Posts: 27 Location: austin, tx

i'm having the exact same problem, w/ the same USE flags, here's my "emerge info":

Pip101 · n00b Joined: 30 Mar 2004 Posts: 62 Location: UK

OK, it seems like it might be CFLAGS-related. I just tried with CFLAGS="" for the hell of it, and it worked. Set CFLAGS="-mcpu=athlon-xp -march=athlon-xp -O3 -pipe" (minimally more conservative than my normal ones, I normally have -fomit-frame-pointer and -ffast-math in there), and it fails again. Fiddling with others now, gradually dropping down.

EDIT: Eventually whittled it down to "-mcpu=i686 -march=i686" and it finally worked, -O1 was the last one I got rid of to make it work for me. Raising the other options again.

EDIT2: OK, "-mcpu=athlon-xp -march=athlon-xp -pipe -fomit-frame-pointer -ffast-math" is also working.. It just b0rks at any optimisation level (-O*) for me. Note that this is with totem 0.99.20 from the suggestion above.

"emerge info" anyway:

grlownzl · n00b Joined: 24 Jan 2004 Posts: 1 Location: UK

Hi

if you add
#define _LINUX_BYTEORDER_LITTLE_ENDIAN_H

to
/var/tmp/portage/totem-0.99.19/work/totem-0.99.19/src/totem-disc.c
(it should go before the
#include <linux/cdrom.h>
line)
and then run ebuild qmerge it should work. (at least it did for me)
[from https://bugs.gentoo.org/show_bug.cgi?id=68087]

[Ahem]

what I should have said in the second part is
#ebuild /usr/portage/media-video/totem/totem-0.99.19.ebuild compile
#ebuild /usr/portage/media-video/totem/totem-0.99.19.ebuild install
#ebuild /usr/portage/media-video/totem/totem-0.99.19.ebuild qmerge

Geoff
_________________
******
Fortune favours the brave, but keeps an axe for the stupid.....
******

jwalcik · n00b Joined: 22 Sep 2003 Posts: 27 Location: austin, tx

i managed to get it working with:

don quixada · l33t Joined: 15 May 2003 Posts: 790

How about just this?:

johndoe_1995 · n00b Joined: 27 Oct 2004 Posts: 4

Hi,

Just to keep the info flowing. I too was having the problem... After reading the thread, here's what worked and didn't work for me.

Did not work

dscamp · Posted: Thu Nov 18, 2004 1:28 pm Post subject:

I just did it with

OPelerin · Guru Joined: 17 Jul 2004 Posts: 354 Location: Belgium

Same for me:

CFLAGS="-march=pentium4" emerge -u totem

No troubles.
_________________
Olivier PELERIN

dopeflish · n00b Joined: 18 Nov 2004 Posts: 4 Location: Glasgow

Thanks CFLAGS="-march=athlon-xp -pipe -fomit-frame-pointer -ftracer -fprefetch-loop-arrays" emerge -u totem worked for me.

Problem solved.

deanpence · Apprentice Joined: 08 Nov 2004 Posts: 158 Location: Earth

This worked for me as well:

llsardonicll · Tux's lil' helper Joined: 07 Oct 2004 Posts: 110

here's mine and seems all the versions compiled fine

llsardonicll · Tux's lil' helper Joined: 07 Oct 2004 Posts: 110

ran into the problem on the wife's machine... i removed the 2.4 linux headers and emerged the 2.6 headers and totem compiled fine on there.

wimvandorst

anybody · n00b Joined: 14 Sep 2003 Posts: 32

Unmerging linux-headers and emerging linux26-headers solved my problems too. I didn't try one of the other possible solutions as i liked that one best ;-)

OPelerin · Guru Joined: 17 Jul 2004 Posts: 354 Location: Belgium

Hi,

Then I have 2 questions.

1) Why thoses old linux headers are installed even when I installed only a kernel 2.6?

2) What is the risk of using linux headers 2.6 ? Any future errors possible?
_________________
Olivier PELERIN

nickrout · Posted: Tue Nov 23, 2004 9:22 pm Post subject:

omitting -O3 worked for me too.