public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas Sachau <tommy@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] multilib eclass support for building binaries for none-default ABI
Date: Sun, 25 Aug 2013 21:34:09 +0200	[thread overview]
Message-ID: <521A5C31.6080704@gentoo.org> (raw)
In-Reply-To: <21018.4483.127950.569766@a1i15.kph.uni-mainz.de>

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

Ulrich Mueller schrieb:
>>>>>> On Sun, 25 Aug 2013, Thomas Sachau wrote:
> 
>> workaround: add a variable, which changes the return of the function
>> checking for the current ABI (always true with variable, without
>> only true, when $ABI == $DEFAULT_ABI)
> 
> Would this variable be set by the user, in profiles, or in ebuilds?

This variable can be set by users and profiles, when they want binaries
for a different ABI (e.g. 64bit toolchain with 32bit userland).

> 
>> first version (multilib1.patch) directly changes the output of the
>> currently used multilib_is_native_abi() function:
> 
> I think this would be very misleading. If a function is called
> multilib_is_native_abi then it should test for exactly that, not for
> something else.
> 
>> second version (multilib2.patch) creates a new function, which
>> should then be used by ebuild authors to check, if they should build
>> ABI-specific content or not (using build_binaries() function instead
>> of multilib_is_native_abi() function)
> 
> +build_binaries() {
> 
> Name space pollution? Prefix with "multilib" please.

i dont really care about the naming, so if you prefer some multilib in
there, how about this:

multilib_build_binaries()?

> 
> +	if [[ ${COMPLETE_MULTILIB} == yes ]] ; then
> +		return 0
> +	else
> +		multilib_is_native_abi
> +	fi
> 
> This can be expressed much shorter (and clearer):
> 
> 	[[ ${COMPLETE_MULTILIB} == yes ]] || multilib_is_native_abi
> 
> But allow me a stupid question, why do you want to build binaries for
> other ABIs anyway? It's called multilib, not multibin.

I already wrote about a setup needing the above. If a user only enables
ab_x86_32 for ebuilds with binary-restrictions, they wont get any binary
at all.
Pretty bad, when you try a reboot with e.g. no udev binaries. ;-)

In addition, users previously had the choice with multilib-portage to
build binaries for some or all target ABIs. Restricting the building of
binaries to the default ABI removes this ability from users.


-- 

Thomas Sachau
Gentoo Linux Developer


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 379 bytes --]

  parent reply	other threads:[~2013-08-25 19:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-25 13:44 [gentoo-dev] [PATCH] multilib eclass support for building binaries for none-default ABI Thomas Sachau
2013-08-25 14:15 ` Ulrich Mueller
2013-08-25 14:30   ` Michał Górny
2013-08-26 14:08     ` Ian Stakenvicius
2013-08-25 19:34   ` Thomas Sachau [this message]
2013-08-25 20:17     ` Michał Górny
2013-08-25 21:55       ` Thomas Sachau
2013-08-26  6:43         ` Michał Górny
2013-09-17 12:41     ` Thomas Sachau
2013-08-26 14:07   ` Ian Stakenvicius
2013-09-17 12:30     ` Thomas Sachau
2013-08-26 14:16   ` Alexis Ballier
2013-08-26 16:06 ` Alexis Ballier
2013-09-17 12:38   ` Thomas Sachau
2013-09-17 14:22     ` Alexis Ballier

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=521A5C31.6080704@gentoo.org \
    --to=tommy@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