public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH v2] install-qa-check.d: issue warnings for 32bit ELFs not using LFS
Date: Tue, 26 May 2015 11:45:08 -0700	[thread overview]
Message-ID: <5564BF34.4060008@gentoo.org> (raw)
In-Reply-To: <5564983E.20306@gentoo.org>

On 05/26/2015 08:58 AM, Zac Medico wrote:
> On 05/26/2015 07:24 AM, Mike Frysinger wrote:
>> +	# Only check on 32-bit systems.  Filtering by $ARCH here isn't perfect, but
>> +	# it should be good enough for our needs.
>> +	case ${ARCH} in
>> +	arm|mips|ppc|sh|x86) ;;
>> +	*) return ;;
>> +	esac
> 
> Shouldn't we also enable this for 64-bit archs when multilib is enabled?
> I've experienced a problem with multilib pkgconfig and 64-bit inodes,
> and if I enable this check for amd64 then I get these warnings for
> dev-util/pkgconfig-0.28-r2:
> 
>  * QA Notice: The following files were not built with LFS support:
>  *   Please see https://bugs.gentoo.org/471102 for details.
>  * readdir@@GLIBC_2.2.5,fopen@@GLIBC_2.2.5
> usr/bin/x86_64-pc-linux-gnu-pkg-config
>  * readdir@@GLIBC_2.2.5,fopen@@GLIBC_2.2.5 usr/bin/pkg-config
>  * fopen@@GLIBC_2.1,readdir@@GLIBC_2.0 usr/bin/i686-pc-linux-gnu-pkg-config
> 

I've confirmed that append-lfs-flags from flag-o-matic.eclass solves the
problem that I have experienced, and filed the following bug:

https://bugs.gentoo.org/show_bug.cgi?id=550482
-- 
Thanks,
Zac


  reply	other threads:[~2015-05-26 18:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26  7:44 [gentoo-portage-dev] [PATCH] install-qa-check.d: issue warnings for 32bit ELFs not using LFS Mike Frysinger
2015-05-26 14:24 ` [gentoo-portage-dev] [PATCH v2] " Mike Frysinger
2015-05-26 15:58   ` Zac Medico
2015-05-26 18:45     ` Zac Medico [this message]
2015-05-30 14:36     ` Mike Frysinger
2015-05-30 18:22       ` Zac Medico
2015-05-30 18:31         ` Mike Frysinger
2015-06-11  7:21       ` Brian Dolbec
2015-06-11 10:17         ` Mike Frysinger

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=5564BF34.4060008@gentoo.org \
    --to=zmedico@gentoo.org \
    --cc=gentoo-portage-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