| 1 |
On 10/11/2010 04:40 PM, "Paweł Hajdan, Jr." wrote: |
| 2 |
> Today I got http://bugs.gentoo.org/340517 filed against chromium-bin. |
| 3 |
> The machine that compiled the package had only gcc-4.4.3 installed. |
| 4 |
> |
| 5 |
> It'd probably be difficult to solve the problem using dependencies (the |
| 6 |
> bug reporter had gcc-4.4.3 installed, but active version was 4.3.4). |
| 7 |
> |
| 8 |
> I was thinking about using a lower version of gcc on the builder, like |
| 9 |
> 4.1.2 or 4.3.4. |
| 10 |
> |
| 11 |
> However, I'm not sure how likely this is to cause C++ ABI mismatch |
| 12 |
> issues. I remember some problems with half of KDE compiler with one GCC |
| 13 |
> version and half with a more recent version. |
| 14 |
> |
| 15 |
> What do you think? |
| 16 |
|
| 17 |
Iff the bug reporter would have selected gcc-4.4.3 being the active version |
| 18 |
using 'gcc-config', his chrome should have been working IMO. |
| 19 |
|
| 20 |
But I don't think this is an acceptable fix: |
| 21 |
|
| 22 |
Instead, gcc-config should sort available gcc's libdirs into /etc/ld.so.conf |
| 23 |
by /descending gcc-version independent of which one is currently selected/, as |
| 24 |
gcc libraries are backwards compatible AFAICS when they have the same SONAME. |
| 25 |
|
| 26 |
For linking, the selected compiler's libs are used anyway. |
| 27 |
|
| 28 |
/haubi/ |
| 29 |
-- |
| 30 |
Michael Haubenwallner |
| 31 |
Gentoo on a different level |
Archives