public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Mark Cuss" <mcuss@cdlsystems.com>
To: <dank@kegel.com>, <gcc@gcc.gnu.org>
Subject: Re: How to make an application look somewhere other than /lib for ld-linux.so.2
Date: Tue, 26 Jul 2005 19:02:00 -0000	[thread overview]
Message-ID: <01a001c59214$987801d0$ab0e10ac@pinchy> (raw)
In-Reply-To: <42D6E21B.9030402@kegel.com>

Ok - thanks.

For #1, if I build with --static, then no libraries can be linked in 
dynamically at runtime...  I need to do this for some custom Qt libraries 
and plugins, so I can't just make a completely static executable.  This is 
unfortunate - the resulting binaries would be big, but they'd work on any 
distro.

#2 - I'd never heard of LSB or lsbcc...  I've just done a google and turned 
up an article on an IBM website on building binary-compatible Linux 
applications...  Thanks for the pointer on this one - it looks like this may 
be the way to go.

Mark

----- Original Message ----- 
From: "Daniel Kegel" <dank@kegel.com>
To: <gcc@gcc.gnu.org>; "Mark Cuss" <mcuss@cdlsystems.com>
Sent: Thursday, July 14, 2005 4:07 PM
Subject: How to make an application look somewhere other than /lib for 
ld-linux.so.2


> "Mark Cuss" <mcuss@cdlsystems.com> wrote:
>> I'm trying to get myself a group of libraries that I can distribute with 
>> my program so that they'll run on any distro.
> > I run into problems all the time when different distros have different 
> > versions of system libraries like libstdc++, libgcc, libc, etc.
>> ...
>> Is there a way to somehow configure gcc build executables that look 
>> elsewhere
>> for ld-linux.so.2, or is what I'm trying to do simply not possible? I'd 
>> really like to have a set of libraries with my program so that it's 
>> binary compatible with other distros... there must be a way. If anyone 
>> has any tips or advice I'd appreciate it.
>
> There are two official ways to go:
>
> 1) Build static binaries.  (If your apps use libnss*.a, you may want to
>    configure your toolchain's glibc with --enable-static-nss; I'm
>    doing that now for one project.  Don't tell drepper.)
> 2) Build your apps with lsbcc.  That will link to the LSB's
>    frozen version of libstdc++, etc.
>
> #1 is doable right now.  #2 is, too, but requires your users to
> install your distro's LSB runtime package.
>
> - Dan
>
> 


  reply	other threads:[~2005-07-26 19:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-14 22:07 Daniel Kegel
2005-07-26 19:02 ` Mark Cuss [this message]
2005-07-26 19:29   ` Haren Visavadia
2005-07-26 19:32     ` Mark Cuss
  -- strict thread matches above, loose matches on Subject: below --
2005-07-14 21:52 Mark Cuss
2005-07-15 10:24 ` Kai Ruottu
2005-07-15 11:13   ` Kai Ruottu
2005-07-26 19:17   ` Mark Cuss
2005-07-27  5:38     ` Ranjit Mathew
2005-07-27  5:49     ` Bob Proulx

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='01a001c59214$987801d0$ab0e10ac@pinchy' \
    --to=mcuss@cdlsystems.com \
    --cc=dank@kegel.com \
    --cc=gcc@gcc.gnu.org \
    /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).