[Pkg-openssl-devel] Bug#638137: Bug#638137: Please transition openssl for multiarch

Steve Langasek steve.langasek at canonical.com
Mon Sep 12 10:26:25 UTC 2011


Hi Kurt,

On Sat, Sep 10, 2011 at 03:50:45PM +0200, Kurt Roeckx wrote:
> On Tue, Aug 16, 2011 at 06:15:39PM -0700, Steve Langasek wrote:
> > Package: openssl
> > Version: 1.0.0d-3.1
> > Severity: normal
> > Tags: patch
> > User: ubuntu-devel at lists.ubuntu.com
> > Usertags: origin-ubuntu oneiric ubuntu-patch

> > Please find attached a patch to openssl to transition it to use of the
> > multiarch library paths as described at
> > <http://wiki.debian.org/Multiarch/Implementation>.  This patch has been
> > tested and included in Ubuntu Oneiric.

> > openssl is obviously a pretty core library, and is part of the stack
> > packaged in ia32-libs.  Converting openssl for multiarch use, and thus
> > facilitating the direct installation of i386 packages on amd64 systems, will
> > be a great step forward in the release goal of getting rid of ia32-libs for
> > wheezy.  So please consider including this patch in Debian sooner rather
> > than later.

> So I've uploaded the patch.  But I have a question:
> The header files depend on the arch, because some comptile time
> options are stored in it.  I think they're all in opensslconf.h.

> libssl-dev didn't get an Multi-Arch line in the control file,
> so I assume they currently can't install it from different
> arches currently.  Should I move the include files to
> /usr/include/$triplet for that too?

> Or do we currently not want to support installing multiple
> -dev packages?

There is a not-yet-resolved Debian Policy bug proposing
/usr/include/$triplet as another FHS exception for per-architecture header
files.  Since it's not yet in Policy, I haven't been pushing such changes as
part of the patches for multiarch (with the exception of linux-libc-dev and
libc6-dev, which are obviously prerequisites for any build-time multiarch
support).  But if you're inclined to add support for co-installable -dev
packages, this would be the way to do it - it's what the toolchain already
supports and that's not likely to change.

There's certainly an open question of what the best way to implement this is
- whether all headers for a library should move to /usr/include/$triplet if
one of them must, or if only the arch-dependent headers should move.  It's
mostly a trade-off of on-disk space savings vs. ease of implementation wrt
upstream build systems.

Cheers,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek at ubuntu.com                                     vorlon at debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-openssl-devel/attachments/20110912/b91d31f5/attachment.pgp>


More information about the Pkg-openssl-devel mailing list