[solved] emerge fails with linker issue

[amaroc]

Hi,

I'm a bit stuck with a problem where I couldn't find a solution so far:

[BillWho]

amaroc,

Try USE=introspection emerge etc.

[BillWho]

amaroc,

sorry it should be USE="introspection"

[amaroc]

Thanks to BillWho for the hint on "introspection" - but it didn't help unfortunately.

That was the last emerge I tried and it failed the same way as before.

[BillWho]

amaroc,

The only other thing I can think of is to check that all its dependencies are installed. You can try this:

First use this

[amaroc]

Hi BillWho,

I followed your advice but there was no dependency issue. Note that I had tried the typical revdep-rebuild before.

I simply tried the different available atk versions and found the following by chance:
>=dev-libs/atk-1.32.0-r1 fail as already known (note dev-libs/atk-1.32.0-r1 was the installed version before)
=dev-libs/atk-1.32.0 compiled OK

I compared the ebuilds between dev-libs/atk-1.32.0 and dev-libs/atk-1.32.0-r1 and couldn't find any difference but the build log showed for -r1 that --enable-introspection has been set by ./configure whereas dev-libs/atk-1.32.0 was running with --disable-introspection.
So your guess regarding "introspection" was pretty good.

However, I tried both variants with and w/o the USE="introspection" - but it didn't change anything.

Unfortunately I'm not familiar with ebuilds and fortunately never had to dig into one the last 7 years. But I definitely do not understand why the same ebuild produces different versions and why the USE-flag does not impact the build process.

If somebody is interested in the logfiles of both buildruns please let me know.

Any further idea is very much appreciated.

Thanks.

[BillWho]

amaroc,

At this point in time I'm as perplexed as you are given that version 2.2.0 is installed here and I don't recall ever having a problem with the earlier versions.

I had high hopes for the introspection flag, but unfortunately we know how that turned out.

I looked through the ebuilds and I do see that gobject-introspection controls the setting of the introspection use flag.

The only two things that comes to mind after reading your synopsis is to try it with the "-introspection", i.e. explicitly turning it off since the previous version compiled with --disable-introspection, but I'm not sure that would override the ebuild setting.

The other thing that comes to mind is you might have installed something that pulled-in gobject-introspection and now an update with the new use flag would be required with USE="introspection emerge uavDN. Then try to emerge dev-libs/atk-1.32.0-r1 if it 's not pulled-in with the update.

That emerge will check for new use and consider the entire dependency tree of packages.

One of those have to work

Good luck

[amaroc]

[BillWho]

amaroc,

It's good to hear that you made some progress with this. I did notice that there are a lot of packages dependent on gobject-introspection - some which I use quite often especially evince and gedit.

The package description of 'infrastructure for generating gobject library bindings for various languages' is a little vague to say the least and fails to convey or even speculate on the benefits/consequences of compiling with it or not.

Since my approach on how to continue may differ from yours depending on your needs and comfort level I'll just tell you that I would enable the introspection use flag and do the emerge to update the necessary packages.

The predicate here is the fact that gobject-introspection was already pulled-in by another dependent package(s) and unmerging it would break the dependent package(s). Of course you could always unmerge the dependent package(s), but that may not be what you would want to do. In that case gobject-introspection is going to remain and there's a chance that it it could cause problems further on down the road.

In my case I have introspection enabled in make.conf rather than using package.use since there were so many packages associated with that use flag.

Whatever you decide I'd be interested to know.

Good luck

[amaroc]

[BillWho]

Hi amaroc,

Welcome back! I thought you decided to take the thing outside and shoot it!

[amaroc]

Hi BillWho,

many thanks for still trying to help.

[gienah]

[BillWho]

amaroc,

I once said to a another gentoo user that gentoo is a lot like the universe - when you finally think you understand it all, you discover something new that leads you down another path of discovery and confusion

Your use flags settings aren't bad at all, it's not like the minefield that I had to recover from. Heck, yours looks like the proverbial piece of cake.

As far as dev-python/PyQt4-4.8.4 goes, I would unmerge it. There are no packages that are dependent on it. What's the worst that can happen?

What is a little strange though is you're in the stable repos and I'm using testing repos which should less stable and more error prone. Go figure!

I would finally suggest enabling introspection on a package by basis for the actual packages you have installed in package.use.

Give it a try and let us know

[amaroc]

Hi,

The good news first - I've been able to solve the issue completely. However, I still don't understand what has really caused the problem.
Nevertheless, the hint