Re: List of FTBFS in Ubuntu
On Fri, Dec 10, 2010 at 2:38 AM, Fernando Lemos <email@example.com> wrote:
> Hi Olaf, Roger
> On Thu, Dec 9, 2010 at 11:00 AM, Olaf van der Spek <firstname.lastname@example.org> wrote:
>>> Now, pkg-config isn't standardised /either/, but it's useful because
>>> it will work with any standards-conforming compiler. It's just a
>>> generalisation of existing practice (in the form of foo-config
>>> scripts generated during a package build).
>> Pkg-config probably isn't bad, but it does increase the complexity of
>> build script. Especially compared to auto linking.
> Correct me if I'm wrong, but I don't think implementing auto linking
> support in GCC is a realistic goal. I can imagine there are lots of
> technical and non-technical issues involved, it's certainly not
> something that can be accomplished in the short term.
Do we need a short term solution?
I agree it can't be done short term, but why is it unrealistic?
>>> But this is all moot. I've written the pkg-config support into the
>>> auto-link header, and we just need to integrate it into the build
>>> system to get the job done.
>> How does pkg-config handle the selection of the threading variant?
>> Toolset-variant? Seems it's hard-coded to a single variant.
> Yeah, take a look at the comments in the report Roger linked to. It
> looks like we can't handle multiple variants with pkg-config. I don't
> think this is a major problem for the time being, though, as there's a
> single variant in Debian and I imagine that's also the case for most
> other distributions.
> I think proper pkg-config support would be fantastic. I'm wondering if
> this support could be patched downstream in case upstream rejects or
> ignores the patches Roger submitted. I'll adapt btag's build system to
> use pkg-config for Boost as soon as this enters unstable.
> To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact email@example.com
> Archive: http://lists.debian.org/AANLkTipWhktHRmamA9SCwSqL-YY7wCa6rz6P7BHVjHU@mail.gmail.com