public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Leno Hou <lenohou@gmail.com>
To: gentoo-dev@lists.gentoo.org,
	"Anthony G. Basile" <blueness@gentoo.org>,
	 Leno Hou <lenohou@gmail.com>,
	Zhao Kevin <kevin.zhaoshuai@gmail.com>
Subject: Re: [gentoo-dev] [PATCH v1][ 1/8] app-text/opensp: Fix ppc64le configure problem
Date: Fri, 22 Apr 2016 15:48:16 +0800	[thread overview]
Message-ID: <CAGQVrL_TrNjs0E+uZorvsYchejcW4se8W+U+sooZm7vH8bvPHw@mail.gmail.com> (raw)
In-Reply-To: <20160420023359.GU5369@vapier.lan>

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

On Wed, Apr 20, 2016 at 10:33 AM, Mike Frysinger <vapier@gentoo.org> wrote:

> On 19 Apr 2016 22:12, Leno Hou wrote:
> > --- /dev/null
> > +++ b/app-text/opensp/files/opensp-1.5.2-configure-with-ppc64le.patch
> > @@ -0,0 +1,26 @@
> > +--- configure.orig   2016-04-09 16:24:17.507053635 +0000
> > ++++ configure        2016-04-09 16:25:41.851918142 +0000
> > +@@ -4947,6 +4947,9 @@
> > +         ppc64-*linux*|powerpc64-*linux*)
> > +           LD="${LD-ld} -m elf32ppclinux"
> > +           ;;
> > ++        ppc64le-*linux*|powerpc64le-*linux*)
> > ++          LD="${LD-ld} -m elf32lppclinux"
> > ++          ;;
>
> you appear to be patching libtool code.  this should be in libtool
> itself. if it's a common issue, we'll want to leverage elibtoolize
> here.  make a patch and stick it in eclass/ELT-patches/ppc64le/,
> and then update the libtool.eclass file to apply those.  then update
> opensp to call the elibtoolize function in src_prepare.
> -mike
>

Thanks Mike, I've sent the patch in mailing list and cc'ed you. Could you
help me to review and merge?

-Leno Hou

[-- Attachment #2: Type: text/html, Size: 1764 bytes --]

      reply	other threads:[~2016-04-22  7:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19 14:12 [gentoo-dev] [PATCH v1][ 1/8] app-text/opensp: Fix ppc64le configure problem Leno Hou
2016-04-19 14:13 ` [gentoo-dev] [PATCH v1][ 2/8] dev-libs/expat: " Leno Hou
2016-04-19 14:13 ` [gentoo-dev] [PATCH v1][ 3/8] net-firewall/iptables: " Leno Hou
2016-04-19 14:13 ` [gentoo-dev] [PATCH v1][ 4/8] net-libs/libmnl: " Leno Hou
2016-04-19 14:13 ` [gentoo-dev] [PATCH v1][ 5/8] sys-apps/acl: " Leno Hou
2016-04-19 14:13 ` [gentoo-dev] [PATCH v1][ 6/8] sys-apps/attr: " Leno Hou
2016-04-19 14:13 ` [gentoo-dev] [PATCH v1][ 7/8] sys-libs/gdbm: " Leno Hou
2016-04-19 14:13 ` [gentoo-dev] [PATCH v1][ 8/8] sys-process/procps: " Leno Hou
2016-04-19 14:20 ` [gentoo-dev] [PATCH v1][ 1/8] app-text/opensp: " Michał Górny
2016-04-19 14:32   ` Leno Hou
2016-04-19 14:36     ` Michał Górny
2016-04-19 14:51       ` Leno Hou
2016-04-19 15:09         ` Leno Hou
2016-04-20  2:33 ` Mike Frysinger
2016-04-22  7:48   ` Leno Hou [this message]

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=CAGQVrL_TrNjs0E+uZorvsYchejcW4se8W+U+sooZm7vH8bvPHw@mail.gmail.com \
    --to=lenohou@gmail.com \
    --cc=blueness@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=kevin.zhaoshuai@gmail.com \
    /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