public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] The gx86 multilib project -- masterplan
Date: Sun, 27 Jan 2013 17:08:20 +0100	[thread overview]
Message-ID: <1359302900.2927.30.camel@belkin4> (raw)
In-Reply-To: <20130127161237.1a04614e@pomiocik.lan>

[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]

El dom, 27-01-2013 a las 16:12 +0100, Michał Górny escribió:
[...]
> 5. Solutions to specific problems
> ---------------------------------
> 
> 1. x11-proto packages
> 
> Those packages install headers to /usr/include and pkg-config files
> to /usr/lib64. This supposedly means that the headers could be
> ABI-specific; however, so far I haven't seen a single difference.
> 
> Possible solutions:
> 
> a) check the headers by hand, move pkg-config files to /usr/share,
> 
> b) make the proto packages multilib. This will cause identical .pc
>    files to be installed to lib32 & lib64 but will also enable eclass
>    checks for header consistency.
> 

Currently, emul packages can install /usr/lib32/pkgconfig files (when
enabling "development" USE flag). This was added because, as emul sets
tend to be obsolete in a few weeks, people compiling packages against
its lib32 provided libs were getting build failures due "native"
pkgconfig files (usually from newer libs) were being used.

Regarding /usr/include, it looks harder to solve, current emul packages
simply don't provide headers at all, but it caused issues like this in
the past:
https://bugs.gentoo.org/show_bug.cgi?id=299490

Maybe installing headers in other place would be interesting :/

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2013-01-27 16:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-27 15:12 [gentoo-dev] The gx86 multilib project -- masterplan Michał Górny
2013-01-27 16:07 ` Ciaran McCreesh
2013-01-27 16:30   ` Michał Górny
2013-01-27 18:04     ` Sergei Trofimovich
2013-01-27 18:11       ` Michał Górny
2013-01-30  0:39         ` Maciej Mrozowski
2013-01-30  9:54           ` Michał Górny
2013-01-27 16:08 ` Pacho Ramos [this message]
2013-01-30  8:35   ` Multilib approach(es) " Michael Weber
2013-01-30  8:52     ` Michael Weber
2013-01-30  9:58     ` Michał Górny
2013-01-30 11:30       ` Michael Weber
2013-01-30 11:46         ` Michał Górny
2013-01-27 16:11 ` Alexis Ballier
2013-01-27 19:14 ` Matt Turner
2013-01-27 20:20   ` Michał Górny

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1359302900.2927.30.camel@belkin4 \
    --to=pacho@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox