Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-01-24
Date: Thu, 26 Jan 2017 13:28:15 +0200	[thread overview]
Message-ID: <20170126112815.fputxxyriyc4amba@tarshish> (raw)
In-Reply-To: <1485429244.1041.1.camel@embedded.rocks>

Hi J?rg,

On Thu, Jan 26, 2017 at 12:14:04PM +0100, J?rg Krause wrote:
> On Thu, 2017-01-26 at 13:11 +0200, Baruch Siach wrote:
> > On Thu, Jan 26, 2017 at 12:04:41PM +0100, Samuel Martin wrote:
> > > On Wed, Jan 25, 2017 at 10:15 PM, Baruch Siach <baruch@tkos.co.il>
> > > wrote:
> > > > On Wed, Jan 25, 2017 at 10:05:42PM +0100, J?rg Krause wrote:
> > > > > Unfortunately I cannot reproduce this issue. Is it a rpath
> > > > > issue? cmake
> > > > > links a test program with host zlib:
> > > 
> > > Note: I'm not able to reproduce the error either.
> > 
> > Do you have a 32bit libz.so.1 in /usr/lib on your host machine?
> 
> I do have:
> 
> ls -l /usr/lib??/libz.so.1
> lrwxrwxrwx 1 root root 14 15. Jan 20:46 /usr/lib32/libz.so.1 ->
> libz.so.1.2.11*
> lrwxrwxrwx 1 root root 14 15. Jan 20:43 /usr/lib64/libz.so.1 ->
> libz.so.1.2.11*

On a recent Debian Testing I have lib32z1 installed and:

ls -l /usr/lib32/libz.so.1 
lrwxrwxrwx 1 root root 13 Dec  7 17:43 /usr/lib32/libz.so.1 -> libz.so.1.2.8

I can reproduce this failure here.

The failed gcc invocation in CMakeError.log includes -Wl,-rpath,/usr/lib32, 
which is clearly incompatible with cross compiling.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

  reply	other threads:[~2017-01-26 11:28 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2017-01-24 Thomas Petazzoni
2017-01-25 21:05 ` Jörg Krause
2017-01-25 21:15   ` Baruch Siach
2017-01-26 11:04     ` Samuel Martin
2017-01-26 11:11       ` Baruch Siach
2017-01-26 11:14         ` Jörg Krause
2017-01-26 11:28           ` Baruch Siach [this message]
2017-01-29 20:37       ` Jörg Krause
2017-01-29 21:11         ` Baruch Siach
2017-01-30 19:59           ` Jörg Krause
2017-01-30 21:20             ` Baruch Siach
2017-01-30 21:22               ` Jörg Krause
2017-01-30 21:26                 ` Baruch Siach
2017-01-30 21:45                   ` Jörg Krause
2017-02-05 22:17                   ` Jörg Krause
2017-02-06 11:06                     ` Thomas Petazzoni
2017-02-06 16:52                       ` Samuel Martin
2017-02-06 17:43                         ` Jörg Krause
2017-02-06 17:53                           ` Samuel Martin
2017-02-06 17:59                             ` Jörg Krause
2017-02-06 18:14                               ` Samuel Martin
2017-02-06 19:24                                 ` Jörg Krause
2017-02-06 21:12                                 ` Jörg Krause
2017-02-06 23:38                                 ` Jörg Krause
2017-02-07 11:28                                   ` Samuel Martin
2017-02-07 13:00                                     ` Jörg Krause
2017-02-07 13:29                                       ` Samuel Martin
2017-02-07 19:07                                         ` Jörg Krause
2017-02-09 20:02                                         ` Jörg Krause

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=20170126112815.fputxxyriyc4amba@tarshish \
    --to=baruch@tkos.co.il \
    --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