Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-01-24
Date: Mon, 06 Feb 2017 20:24:59 +0100	[thread overview]
Message-ID: <1486409099.4950.1.camel@embedded.rocks> (raw)
In-Reply-To: <CAHXCMMJy9T9QTviUMUUqxR8j3Y866BfXQbQ7uN4xcu6BY87eig@mail.gmail.com>

On Mon, 2017-02-06 at 19:14 +0100, Samuel Martin wrote:
> On Mon, Feb 6, 2017 at 6:59 PM, J?rg Krause <joerg.krause@embedded.ro
> cks> wrote:
> > 
> > 
> > Am 6. Februar 2017 18:53:56 MEZ schrieb Samuel Martin <s.martin49@g
> > mail.com>:
> > > On Mon, Feb 6, 2017 at 6:43 PM, J?rg Krause
> > > <joerg.krause@embedded.rocks> wrote:
> > > > 
> > > > 
> > > > Am 6. Februar 2017 17:52:33 MEZ schrieb Samuel Martin
> > > 
> > > <s.martin49@gmail.com>:
> > > > > Hi Jorg, all,
> > > > > 
> > > > > On Mon, Feb 6, 2017 at 12:06 PM, Thomas Petazzoni
> > > > > <thomas.petazzoni@free-electrons.com> wrote:
> > > > > > Hello,
> > > > > > 
> > > > > > On Sun, 05 Feb 2017 23:17:17 +0100, J?rg Krause wrote:
> > > > > > 
> > > > > > > > I meant to ask about Debian and the lib32z1 package
> > > > > > > > specifically
> > > > > > > > (not
> > > > > > > > zlib1g:i386). This package installs 32bit libz.so.1 in
> > > 
> > > /usr/lib32.
> > > > > > > 
> > > > > > > I reported the issue on the CMake mailing list [1]. The
> > > > > > > issue is
> > > > > 
> > > > > that
> > > > > > > the host rpath is used when cross-compiling a simple test
> > > > > > > program
> > > > > > > generated by the check_symbol_exists() macro. I had no
> > > > > > > success in
> > > > > > > disabling the rpath for any of the check_*_macros().
> > > > > > > 
> > > > > > > As I am not a CMake expert, it's quite possible that I
> > > > > > > missed
> > > > > > > something. Has anyone an idea how to fix this issue?
> > > > > > > 
> > > > > > > [1] https://cmake.org/pipermail/cmake/2017-February/06497
> > > > > > > 0.html
> > > > > > 
> > > > > > I've added Samuel in Cc. He is our CMake guy :)
> 
> [...]
> 
> > Do you have any idea why CMake adds the rpath when using
> > check_symbol_exists() in a cross-compilation environment? I
> > reported the issue on the CMake mailing list...
> 
> I saw your report.
> Not a clue so far.
> I do have /usr/lib32/libz.so.1 (/usr/lib32/libz.so.1 ->
> libz.so.1.2.11) on my system as well, but I'm not able to reproduce
> the error (the cmake-3.7.2 from my host archlinux picks the right lib
> from the sysroot :-/).

I am not able to reproduce the issue on my Arch Linux host, too. But, I
am able to reproduce it on a Debian host.

Despite the reproducability, am I right that rpath should not be passed
to the cross-linker by CMake when compiling and linking a test program
as it is done when using check_symbol_exists()? Only the sysroot flag
should be passed to the cross-linker, right?

J?rg

  reply	other threads:[~2017-02-06 19:24 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
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 [this message]
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=1486409099.4950.1.camel@embedded.rocks \
    --to=joerg.krause@embedded.rocks \
    --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