All of lore.kernel.org
 help / color / mirror / Atom feed
From: "b.gunreben" <b.gunreben@web.de>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: GNU/Libc 2.3.1 on HP-PARISC requires >= 2.4.19 kernel.
Date: Thu, 05 Dec 2002 19:10:03 +0100	[thread overview]
Message-ID: <3DEF967B.8B7F68AA@web.de> (raw)
In-Reply-To: 200212051650.gB5GoG7d003199@hiauly1.hia.nrc.ca

John David Anglin wrote:
> 
> > Hi, my name is Carlos, and I cause all your nightmares with glibc on
> > HPPA :)
> > [...]
> > I recommend that you _do_ _not_ upgrade glibc on HPPA until 2.3.1-6.
> 
> Being perverse, I tried installing 2.3.1-5.  I hit the same problem
> that Joel mentioned previously, the old dynamic loader doesn't define
> GLIBC_PRIVATE.  I was trying to install glibc privately in a prefix of
> my selection.  I have been using LD_LIBRARY_PATH to select my library
> path.  However, this no longer works since all system binaries are
> linked using /lib/ld.so.1 and it isn't compatible with the 2.3.1
> libraries.  Is there a way around this?

Well, I don't think it is perverse. I have already more than 10 days
uptime with a machine, that runs completely with 2.3.1 (and this machine
was only for about 13h idle).

In order to run with the new ld.so, you may try the following:

<prefix>/lib/ld.so.1 --library-path <prefix>/lib:<prefix>/usr/usr/lib
command

or you set up a chroot system with all needed programs.

Berthold

  reply	other threads:[~2002-12-05 18:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-05  1:08 [parisc-linux] GNU/Libc 2.3.1 on HP-PARISC requires >= 2.4.19 kernel Carlos O'Donell
2002-12-05 13:31 ` [parisc-linux] " Matthew Wilcox
2002-12-05 15:39   ` Carlos O'Donell
2002-12-05 15:39   ` Carlos O'Donell
2002-12-05 13:31 ` Matthew Wilcox
2002-12-05 16:50 ` John David Anglin
2002-12-05 18:10   ` b.gunreben [this message]
2002-12-05 16:50 ` John David Anglin

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=3DEF967B.8B7F68AA@web.de \
    --to=b.gunreben@web.de \
    --cc=parisc-linux@lists.parisc-linux.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 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.