From: Micha <micha@topsurf.com>
To: linux-newbie@vger.kernel.org
Subject: Re: Debian libc6 upgrade
Date: Wed, 28 Jan 2004 16:52:38 +0100 [thread overview]
Message-ID: <200401281652.39190.micha@topsurf.com> (raw)
In-Reply-To: <5.1.0.14.1.20040127140555.01fe9d38@celine>
> > > Hi to all,
> > > I'm running a mixed Debian Woody, with a few backports and libc6
> > > 2.3.1-16. Now I would like to upgrade to libc6 2.3.2.ds1-10.
> > > Anything runs fine - until I try to compile a program :
>
> Sorry I missed this the first time through. Let me ask the basic question:
> when you upgraded libc6, did you also upgrade libc6-dev (the .deb with the
> header files) to match?
>
> I run Sid here, so offhand I do not know what libc6 is "current" for Woody
> ... so I can't deduce from what you posted if you did your libc6 upgrade
> through Debian package management or if it is part of what makes this what
> you call a "mixed" system.
The current version of libc6 for woody is 2.2.5-11.5, mixed system, because I
already upgraded libc6 and a few other packages.
However, I had first an woody testing system. Then I upgraded the libc6 from
2.2.4-7 to 2.3.1-16 via aptitude, this was the testing release this time. But
everything run fine, beside the fact, using the praeprocessor for compiling a
program didn't succeed.. :-)
But the compiler did his job.
Now I did again this upgrade of libc6, also of libc6-dev and
linux-kernel-headers using aptitude.
Maybe, I've got the wrong version of gcc (2.95.4-9 now ) ?
Micha
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2004-01-28 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 20:40 Debian libc6 upgrade Michael Scondo
2004-01-27 21:34 ` caszonyi
2004-01-27 22:16 ` Ray Olszewski
2004-01-28 15:52 ` Micha [this message]
2004-01-28 21:27 ` Michael Scondo
2004-01-28 22:24 ` Michael Scondo
2004-01-28 22:30 ` Ray Olszewski
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=200401281652.39190.micha@topsurf.com \
--to=micha@topsurf.com \
--cc=linux-newbie@vger.kernel.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