[gentoo-amd64] Re: gnome installation problem: unreslved references in the gst libraries

[Duncan]

"Nadav Horesh" <nadavh@×××××××××××.com> posted
710F2847B0018641891D9A21602763600B6DF0@×××××××××××××××.il, excerpted
below, on  Wed, 10 Oct 2007 07:13:16 +0200:

> I set the compilation flags to the recommended (-O2 -march=k -pipe)

Hope the above is a typo.  That should be -march=k8 (you missed the 8).  
I'd simply assume it was a typo and not mention it, but if that turned 
out to be the problem... =8^(

> and the make option to J1, re-emerged
> the whole gstream&friends packages. But it did not help. It looks that
> the problem is that when trying to emerge media-related gnome packages
> they are not linked against the right gstxxx libraries.

Well, it was a shot in the dark anyway...

BTW, something in the above prodded my memory...  You don't still happen 
to have the old gstreamer 0.8 series do you?  Current is 0.10 series, and 
it's possible if you still have some of the old stuff around, that's 
what's causing the incompatibility.

>    Nadav.
>
> N.B.
>
> 1. I am a speed freak, thus I use XFCE. I use the gnome package mainly
> for its utilities.

I like speed, but I like control and features better, I think, and since 
I have a dual Opteron, RAID, and an almost embarrassing 8 gigs memory, 
I've obviously thrown hardware at the problem rather than go the 
conservative memory route. =8^P  (I've observed to myself several times 
that the hardware folks should really be pushing Linux, as if folks don't 
spend the money on software, they have that much more to spend on 
hardware... and I've done just that! =8^)

Still, I'd certainly try and may stay xfce if I were running a more 
conventional single disk, single cpu/core, half-gig memory or less 
system.  Of course, I'd be much more likely to be doing it on a binary 
distribution instead of Gentoo in that case, but anyway...

 2. I did use your recommended flags as you mentioned.

=8^)  I figured that was too close to be coincidence.  

The main thing I worry about is that while yes, it's great playing around 
with these nice fancy CFLAG options, I hope that folks don't miss the 
fact that to some extent it is "out there" a bit, and as such, it /will/ 
mean fighting with things every once in awhile to get stuff compiled, 
where a more conservative "-march=k8 -O2 -pipe" will be /almost/ as good, 
and more likely to "just work", with less emerge failures and the like.

I recognize that not all computer users have the luxury of treating 
computing as a hobby, as I do, and that some prefer it "just work", and 
the less hassle to get to that state, the happier they'll be.  (I OTOH 
enjoy a bit of a challenge on occasion, the precise reason I like 
bleeding edge.  If it always "just worked", I'd be about as likely to 
find it interesting as a hobby as I am to find staring at the microwave 
or freezer "interesting"! =8^)

The concern therefore is that folks will grab my options and then wonder 
why they don't always work, as much as it is countering the myth that 
one /cannot/ run such options regularly, and only the ricers and insane 
try.  It's fine to want to experiment and run unusual cflags and test new 
packages, and in fact, /someone/ as to do it, as long as you realize the 
extra investment in time and occasional hassle it's likely to bring with 
it. =8^)

But it looks like you are pretty well aware of the issues already, and 
have made your choice knowing the tradeoffs.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@g.o mailing list