All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [arc-buildroot] Re: [FYI 1/2] WIP:pcre2: new package
Date: Fri, 30 Jun 2017 09:30:38 +0000	[thread overview]
Message-ID: <1498815037.8837.10.camel@synopsys.com> (raw)
In-Reply-To: <5cba5356-ff94-7e8b-8158-44937264dd9d@mind.be>

Hi Arnout,

On Fri, 2017-06-30 at 11:25 +0200, Arnout Vandecappelle wrote:
> 
> On 29-06-17 22:17, Peter Seiderer wrote:
> [snip]
> > 
> > Did try the (relative new) support/scripts/test-pkg script with your patch/packet, two
> > failures until now:
> > 
> > - br-arcle-hs38 [ 4/47]: FAILED
> > 
> > ? checking for arc-buildroot-linux-uclibc-ar... .../test_pcre2_001/br-arcle-hs38/host/usr/bin/arc-linux-ar
> > ? checking the archiver (.../test_pcre2_001/br-arcle-hs38/host/usr/bin/arc-linux-ar) interface... unknown
> > ? configure: error: could not determine .../test_pcre2_001/br-arcle-hs38/host/usr/bin/arc-linux-ar interface
> > ? package/pkg-generic.mk:217: recipe for target '.../test_pcre2_001/br-arcle-hs38/build/pcre2-10.23/.stamp_configured' failed
> > 
> > And from 'build/pcre2-10.23/config.log':
> > 
> > ? configure:4792: .../test_pcre2_001/br-arcle-hs38/host/usr/bin/arc-linux-ar cru libconftest.a conftest.o >&5
> > ? .../test_pcre2_001/br-arcle-hs38/host/usr/bin/arc-linux-ar: error while loading shared libraries: libfl.so.2: cannot open shared object file: No
> > such file or directory
> > ? configure:4795: $? = 127
> > 
> > 	$ ./host/usr/bin/arc-linux-ar -V
> > ? ./host/usr/bin/arc-linux-ar: error while loading shared libraries: libfl.so.2: cannot open shared object file: No such file or directory
> > 
> > 	$??LD_LIBRARY_PATH=host/opt/ext-toolchain/lib ./host/usr/bin/arc-linux-ar -V
> > ? GNU ar (GNU Binutils) 2.28.51.20170313
> > ? Copyright (C) 2017 Free Software Foundation, Inc.
> > ? This program is free software; you may redistribute it under the terms of
> > ? the GNU General Public License version 3 or (at your option) any later version.
> > ? This program has absolutely no warranty.
> > 
> > Looks more like a toolchain support problem...I think nothing pcre2 specific...

Yeah this is an issue with Tomas' prebuilt toolchain where libfl is not in RPATH.
We discussed that with Thomas recently and the plan was for him to check
how that toolchain gets built.

Note with Buildroot-built toolchain such a problem doesn't exist.

Let's see what Thomas says.

-Alexey

  reply	other threads:[~2017-06-30  9:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-28  7:39 [Buildroot] [FYI 0/2] Qt5.9 and pcre2 Naoki Matsumoto
2017-06-28  7:40 ` [Buildroot] [FYI 1/2] WIP:pcre2: new package Naoki Matsumoto
2017-06-29 19:29   ` Peter Seiderer
2017-06-29 20:17   ` Peter Seiderer
2017-06-30  9:25     ` Arnout Vandecappelle
2017-06-30  9:30       ` Alexey Brodkin [this message]
2017-06-28  7:42 ` [Buildroot] [FYI 2/2] WIP:qt5: Bump up to 5.9 Naoki Matsumoto
2017-06-29 19:36   ` Peter Seiderer
2017-06-30  2:24     ` Naoki Matsumoto
2017-06-30  9:25       ` Arnout Vandecappelle
2017-07-02  1:06         ` jsmith
2017-07-02 10:58           ` Arnout Vandecappelle
2017-07-03  5:31             ` Brent Sink
2017-07-03 13:12               ` Arnout Vandecappelle

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=1498815037.8837.10.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.