Duplicate symbol __i686.get_pc_thunk.bx in... libbitmap.a

[afabco]

Did the emerge -uD world yesterday.

As usual, my stomach sank when I saw the xorg-x11 appear in the -puD world
Takes it to 6.8.2-r1.

So I did the emerge -uD world. I like living dangerously.

And sure enough, true to form, X is broke.

$ startx

<snip>

Duplicate symbol __i686.get_pc_thunk.bx in /usr/lib/modules/fonts/libbitmap.a:bitmapmod.o
Also defined in /usr/lib/modules/fonts/libbitmap.a

Did the emerge -C xorg-x11, and tried to

emerge x11-base/xorg-x11-6.8.0-r5

looked like it emerged ok. I even rebooted, just to be sure all the loose ends were gone.

$ startx

<snip>

Duplicate symbol __i686.get_pc_thunk.bx in /usr/lib/modules/fonts/libbitmap.a:bitmapmod.o
Also defined in /usr/lib/modules/fonts/libbitmap.a

Backed down to gcc-3.3.5 (was at gcc-3.4.3-20050110) with gcc-config.

emerge -C and re-emerged xorg-x11-6.8.0-r5. same error.

So what now?

thx,

[chunderbunny]

This is an issue affecting the hardened aspects of GCC and xorg. You can try switching to a different gcc profile (one without any hardened, pie or ssp support) and recompiling xorg but this doesn't always work. For me, I have to switch back to gcc-3.3 (I use gcc-3.4 normally) in order to get things to work.

[afabco]

yeah, I should have mentioned that. googling talked about hardening, but I'm not doing any hardening. No harden flags at all.

I am doing pic tho. Maybe tomorrow.

Thanks

[afabco]

Ok, I just did

USE="static" emerge xorg-x11, and got past the error described above.

Now I get a nice pretty blue screen with a white 2cm or so square in the middle and a dark bar (like the toolbar didn't get wrote) along the bottom. And that's it. No mouse. No keyboard. No <ctl-alt-bkspc>.

But I guess it's progress....

[afabco]

ok, nothing I did really did any lasting good. What I ended up doing was disabling the onboard intel video, and putting in an old nvidia riva agp card I had laying around. Then did an X -configure and used the resulting xorg.conf. Things look fine now, and have been for a couple of days. Only weird thing is sometimes when I make a kernel change, the first startx comes up in 640x480. Exit and startx again, and it comes up in 1280x1024 (like it should)

I don't think the on-board video is bad, because it worked fine before the emerge, and it still works fine with another commercial operating system.

Oh well, chalk it up as another one of life's little mysteries.

[vague]

USE="static" emerge xorg-x11, and got past the error described above.

USE="static" is not ideal in my mind, a better solution that has worked for some is

Code: Select all

USE="dlloader" emerge xorg-x11

Try that rather.

[afabco]

Well, anything I tried either made no difference, or made things worse (see other posts). Causative Entropy in action. Finally the system became unusable, and I finally just decided to fdisk the whole d thing and do a reinstall. Am doing that now. We'll see what happens.