public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: Andrew Cagney <cagney@redhat.com>
Cc: frysk <frysk@sources.redhat.com>
Subject: Re: enabling shared builds
Date: Thu, 13 Dec 2007 15:02:00 -0000	[thread overview]
Message-ID: <47614961.5090901@redhat.com> (raw)
In-Reply-To: <476146B5.7020606@redhat.com>

Andrew Cagney wrote:
> There are several ways to address this; and before making this change 
> I think we should consider our options:
>
> - wire build RPATH into binaries
> Doesn't work: the installed binary could load incorrect build-tree 
> solibs and vice versa

yuck.

>
> - rely on the developers to provide the path explicitly:
>   LD_LIBRARY_PATH=<path-to-all-solibs> ./frysk-core/frysk/bindir/fhpd
> (chance of us getting that right? 0 :-)

ugh

>
> - provide a wrapper script that sets the environment vis:
>   ./BuildTree ./frysk-core/frysk/bindir/fhpd

Feasible, but a binary should just "work" without lots of wrappers.

>
> - have 'TestRunner' export LD_LIBRARY_PATH before invoking any utilities

Don't like.

>
> - create two versions of the binary; one for build-tree and one for 
> install tree
>

Don't like.

> - switch to install-tree testing
> Would mean breaking configure convention and set --prefix=.  On the 
> other hand it would mean only testing one way.
IMO should be install tree testing anyway, as it simulates the 
environment when Frysk is deployed much more accurately. +1 for this way,

Regards

Phil

  reply	other threads:[~2007-12-13 15:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-13 14:50 Andrew Cagney
2007-12-13 15:02 ` Phil Muldoon [this message]
2007-12-13 21:38   ` Kris Van Hees
2007-12-13 23:19     ` Andrew Cagney
2007-12-13 23:58       ` Kris Van Hees
2007-12-13 16:13 ` Petr Machata

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=47614961.5090901@redhat.com \
    --to=pmuldoon@redhat.com \
    --cc=cagney@redhat.com \
    --cc=frysk@sources.redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).