Bug#630399: perl: multiarch libc and partial upgrades

Jonathan Nieder jrnieder at gmail.com
Fri Jul 1 19:28:12 UTC 2011


Niko Tyni wrote:

> A couple of quick notes:
>
> - a sourceful change to make sure the multiarch paths are included
>   in libpth is still necessary. The powerpc build of 5.12.4-1 was done
>   on a buildd that with an old enough gcc + libc6 that it's still not
>   multiarch enabled
>    https://buildd.debian.org/status/fetch.php?pkg=perl&arch=powerpc&ver=5.12.4-1&stamp=1309478307
>
> - http://packages.debian.org/sid/gcc shows 4.4 is the default on
>   ia64 too, and also on quite a few non release architectures.

Thanks for the update.  (BTW your comments on why libpth in perl-base
is not likely to be part of the essential functionality were
convincing.)

> I'd love to have a better solution than the arch-specific build dependencies
> this is leading to.
>
> Maybe go back to specifying plibpth manually to Configure for a while
> (overriding the upstream change of parsing 'gcc -print-search-dirs'),
> and Build-Depend on 
>  gcc-4.6 (>= 4.6.0-13) | gcc-4.4 (>= 4.4.6-4)
> which guarantees that /usr/lib/<triplet> exists regardless of which gcc
> is actually used.

Makes sense.  That could be

  gcc-4.6 (>= 4.6.0-13) | gcc (<< 4:4.5), gcc (>> 4:4.6) | gcc-4.4 (>= 4.4.6-4)

to make sure the /usr/bin/gcc symlink points in the right place,
except I have a vague fear that autobuilders might simplify it to

  gcc-4.6 (>= 4.6.0-13), gcc (>> 4:4.6)






More information about the Perl-maintainers mailing list