Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 1/2] package/gobject-introspection: add package
Date: Thu, 23 Feb 2017 14:44:13 +0100	[thread overview]
Message-ID: <20107548.7MX6vXLLbF@sagittae> (raw)
In-Reply-To: <b5cbc35d4d8e4457563fdf5b8dfd04360c6616a5.1487811280.git.sam.bobroff@au1.ibm.com>

Hello Sam,

On Thursday 23 February 2017 11:54:54 CET Sam Bobroff wrote:
[...]
> diff --git a/package/gobject-introspection/create-ldd-cross.sh b/package/
gobject-introspection/create-ldd-cross.sh
> new file mode 100755
> index 000000000..58d4281e8
> --- /dev/null
> +++ b/package/gobject-introspection/create-ldd-cross.sh
> @@ -0,0 +1,46 @@
> +#!/bin/bash
> +set -e
> +
> +if [ $# -ne 2 ]; then
> +	echo "Usage: <full qemu path> <staging dir>"
> +	exit 2
> +fi
> +
> +QEMU="$1"
> +STAGING_DIR="$2"
> +OUT="$STAGING_DIR/usr/bin/ldd-cross"
> +cat > "$OUT"<<'EOF'
> +#! /bin/bash
> +
> +set -e
> +
> +EOF
> +echo "QEMU=\"$QEMU\"" >> "$OUT"
> +eval "$(grep ^RTLDLIST= $STAGING_DIR/usr/bin/ldd)"
> +
> +echo -n 'RTLDLIST="' >> "$OUT"
> +for RTLD in $RTLDLIST; do
> +	echo -n "$STAGING_DIR$RTLD " >> "$OUT"
> +done
> +echo '"' >> "$OUT"
> +echo >> "$OUT"
> +
> +cat >> "$OUT"<<'EOF'
> +for file do
> +  case $file in
> +  */*) :
> +       ;;
> +  *) file=./$file
> +     ;;
> +  esac
> +  for RTLD in ${RTLDLIST}; do
> +    if test -x $RTLD; then
> +      "$QEMU" "$RTLD" --list "$file"

Why do not call directly ldd? It does not give same result?

In add, do uclibc and musl provide ldd?

If you are looking for a cross-ldd, you can take a look to this script:

  https://gist.github.com/jerome-pouiller/c403786c1394f53f44a3b61214489e6f

It come from crosstool-ng project (and written by Yann Morin).

You may also have noticed that Yocto use "prelink"[1]. However, it seems 
overkill for our usage.

[1] http://git.yoctoproject.org/cgit/cgit.cgi/prelink-cross/


> +    fi
> +  done
> +done
> +EOF


-- 
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr

  parent reply	other threads:[~2017-02-23 13:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-23  0:54 [Buildroot] [RFC PATCH 0/2] add gobject-introspection Sam Bobroff
2017-02-23  0:54 ` [Buildroot] [RFC PATCH 1/2] package/gobject-introspection: add package Sam Bobroff
2017-02-23  9:18   ` Thomas Petazzoni
2017-02-24  4:07     ` Sam Bobroff
2017-02-24  8:25       ` Thomas Petazzoni
2017-02-27 14:58         ` Arnout Vandecappelle
2017-02-27 15:06           ` Baruch Siach
2017-02-27 23:22             ` Sam Bobroff
2017-08-15 10:47               ` Adam Duskett
2017-08-17  6:44                 ` Alexey Roslyakov
2017-08-17 22:39                   ` Arnout Vandecappelle
2017-08-22 10:57                     ` Adam Duskett
2017-08-24 23:03                       ` Arnout Vandecappelle
2017-08-26 16:01                         ` Adam Duskett
2017-08-27  5:11                           ` Waldemar Brodkorb
2017-08-27 15:15                             ` Adam Duskett
2017-02-27 15:58           ` Thomas Petazzoni
2017-02-27 22:54             ` Sam Bobroff
2017-02-23 13:02   ` Baruch Siach
2017-02-23 13:44   ` Jérôme Pouiller [this message]
2017-02-23  0:54 ` [Buildroot] [RFC PATCH 2/2] package/libvips: enable introspection Sam Bobroff
2017-02-23  9:19   ` Thomas Petazzoni

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=20107548.7MX6vXLLbF@sagittae \
    --to=jezz@sysmic.org \
    --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