All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: 'Thomas Petazzoni' <thomas.petazzoni@bootlin.com>,
	"Yann E. MORIN" <yann.morin.1998@free.fr>,
	"mail@jens-maus.de" <mail@jens-maus.de>,
	"fesc2000@mailbox.org" <fesc2000@mailbox.org>,
	"f.rogall@gmx.de" <f.rogall@gmx.de>,
	"oliver.kasten@trsystems.de" <oliver.kasten@trsystems.de>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] NodeJS, qemu wrapper and ELF interpreter fun
Date: Tue, 1 Nov 2022 08:46:23 +0000	[thread overview]
Message-ID: <f7086aad47234c089332330689ae9a42@AcuMS.aculab.com> (raw)
In-Reply-To: <20221031213926.50d3c778@windsurf>

...
> (C) Pass LD_LIBRARY_PATH pointing to $(STAGING_DIR)/lib and
>     $(STAGING_DIR)/usr/lib in the Qemu wrapper. This works because
>     LD_LIBRARY_PATH paths have precedence over paths given by
>     ld.so.cache.
> 
>     This is the solution already used by the GOI qemu wrapper in
>     package/gobject-introspection/g-ir-scanner-qemuwrapper.in, and
>     which was suggested in bug
>     https://bugs.busybox.net/show_bug.cgi?id=14366.
> 
> Any opinion? Or other ideas?

Using LD_LIBRARY_PATH like that is a bad idea.
Just google for it and you'll find a load of stuff about it.

LD_LIBRARY_PATH should only really be used not substitute a
non-standard library - eg for testing.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-11-01  8:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 20:39 [Buildroot] NodeJS, qemu wrapper and ELF interpreter fun Thomas Petazzoni via buildroot
2022-11-01  8:46 ` David Laight [this message]
2022-11-01 10:02   ` Yann E. MORIN
2022-11-01 10:15 ` Yann E. MORIN

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=f7086aad47234c089332330689ae9a42@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=buildroot@buildroot.org \
    --cc=f.rogall@gmx.de \
    --cc=fesc2000@mailbox.org \
    --cc=mail@jens-maus.de \
    --cc=oliver.kasten@trsystems.de \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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.