Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 2/2] ngrep: fix static linking issue with libpcre
Date: Tue, 05 Nov 2013 00:05:06 +0100	[thread overview]
Message-ID: <52782822.90900@openwide.fr> (raw)
In-Reply-To: <87li13q3g9.fsf@dell.be.48ers.dk>

Le 04/11/2013 22:09, Peter Korsgaard a ?crit :
>>>>>> "Romain" == Romain Naour <romain.naour@openwide.fr> writes:
> 
>  > Adding -lpcre in LDFLAGS place the library before object files:
>  > gcc ... -lpcre -L.../sysroot/usr/lib -s -o ngrep ngrep.o -lpcap
> 
>  > Makefile.in is patched to use @LIBS@ for adding -lpcre in the right place.
> 
>  > Fixes:
>  > http://autobuild.buildroot.net/results/684/684a3bed28d13ef5e5156257aade3b9aff32f180
> 
>  > Signed-off-by: Romain Naour <romain.naour@openwide.fr>
>  > ---
>  >  package/ngrep/ngrep-0003-fix-static-link.patch | 22 ++++++++++++++++++++++
>  >  package/ngrep/ngrep.mk                         |  2 +-
>  >  2 files changed, 23 insertions(+), 1 deletion(-)
>  >  create mode 100644 package/ngrep/ngrep-0003-fix-static-link.patch
> 
>  > diff --git a/package/ngrep/ngrep-0003-fix-static-link.patch b/package/ngrep/ngrep-0003-fix-static-link.patch
>  > new file mode 100644
>  > index 0000000..6d70778
>  > --- /dev/null
>  > +++ b/package/ngrep/ngrep-0003-fix-static-link.patch
>  > @@ -0,0 +1,22 @@
>  > +fix static link
>  > +Libraries must be placed before object files.
> 
> I guess you mean AFTER.
> 

Yes, copy and past error...
Thanks

Romain

      reply	other threads:[~2013-11-04 23:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-02 15:51 [Buildroot] [PATCH v3 2/2] ngrep: fix static linking issue with libpcre Romain Naour
2013-11-04 21:09 ` Peter Korsgaard
2013-11-04 23:05   ` Romain Naour [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=52782822.90900@openwide.fr \
    --to=romain.naour@openwide.fr \
    --cc=buildroot@busybox.net \
    /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