Linux PARISC architecture development
 help / color / mirror / Atom feed
From: David Huggins-Daines <dhd@linuxcare.com>
To: drepper@cygnus.com (Ulrich Drepper)
Cc: parisc-linux@thepuffingroup.com, debian-hppa@lists.debian.org,
	parisc@lists.linuxcare.com
Subject: Re: [parisc-linux] glibc 2.1.94 CVS merge, packages on the way, ABI breakage :(
Date: 03 Oct 2000 21:23:43 -0400	[thread overview]
Message-ID: <87og114cww.fsf@linuxcare.com> (raw)
In-Reply-To: Ulrich Drepper's message of "03 Oct 2000 15:42:35 -0700"

Ulrich Drepper <drepper@redhat.com> writes:

> David Huggins-Daines <dhd@linuxcare.com> writes:
> 
> > I take it that libc.so, libm.so, and ld.so should all be versioned
> > with GLIBC_2.2 as the base, then?
> 
> Every single DSO.  There is no compatibility to be preserved.

Okay, yes, you're right.  Unfortunately we've built a bunch of
binaries against our broken libc, so it will all have to be rebuilt,
because all binaries expect to see GLIBC_2.0 and GLIBC_2.1 versions.

But I guess this is the right thing to do, since we really do not want
any of the compatibility cruft bloating our libc.

HP people note: Yes it looks like we have to rebuild everything.  I
think I can get things up again rather quickly, as I just need to
build a static toolchain and then relink all the packages that are
sitting around built on my A180.  We will have to clear out the
archive in pehc:/pub/debian-hppa though.

I am not very pleased with symbol versioning at the moment :(

-- 
dhd@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.

      reply	other threads:[~2000-10-04  1:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-03 22:06 [parisc-linux] glibc 2.1.94 CVS merge, packages on the way, ABI breakage :( David Huggins-Daines
2000-10-03 22:23 ` Ulrich Drepper
2000-10-03 22:28   ` David Huggins-Daines
2000-10-03 22:42     ` Ulrich Drepper
2000-10-04  1:23       ` David Huggins-Daines [this message]

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=87og114cww.fsf@linuxcare.com \
    --to=dhd@linuxcare.com \
    --cc=debian-hppa@lists.debian.org \
    --cc=drepper@cygnus.com \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=parisc@lists.linuxcare.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