Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 25 Oct 2007 14:50:39 +0800
From:      "Rong-en Fan" <grafan@gmail.com>
To:        freebsd-stable@freebsd.org
Subject:   Re: HEADSUP: don't upgrade to RELENG_6 now (7 is fine)
Message-ID:  <6eb82e0710242350n1156e867r59e4492b57e0a708@mail.gmail.com>
In-Reply-To: <6eb82e0710242104m208f43f7u1b83de21ac398d4d@mail.gmail.com>
References:  <6eb82e0710242104m208f43f7u1b83de21ac398d4d@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 10/25/07, Rong-en Fan <grafan@gmail.com> wrote:
> On 10/25/07, Rong-en Fan <grafan@gmail.com> wrote:
> > On 10/25/07, Alson van der Meulen <alson+ml@alm.flutnet.org> wrote:
> > > Hello,
> > >
> > > My installworld of RELENG_6 from a few hours ago failed with this error
> > > (from memory):
> > > /lib/libncurses.so.6: undefined symbol: __mb_sb_limit
> > >
> > > This broke everything that depended on libncurses, plus PAM. I had to
> > > force a reboot via DDB and copy /usr/obj/lib/libc/libc.so.6 to /lib
> > > using binaries from /rescue to fix it so I could run make installworld
> > > again.
> >
> > I will take a look. before that do not upgrade your system.
>
> I did some tests, it turns out that only RELENG_6 is affected. To be
> more specific, as ncurses lib is installed before libc. It gets broken.
> For 7 and above, it is fine because we install libc right after csu and
> before everything.
>
> One way to solve this is we install libc as early as possible, but I
> think it may be too risky at release cycle, so I would like to back
> out this change and add an UPDATING entry. Then check whether
> we can change the installation order of libc later.
>
> If you cvsup after 'Oct 24 14:32:33 2007 UTC', please do not
> upgrade until I send out all clear message.
>
> If you already broken your world, use this way in *single user*,
>
> /rescue/chflags noschg /lib/libc.so.6
> /rescue/cp /usr/obj/usr/src/lib/libc/libc.so.6 /lib/
>
> then you need reboot, after that continue installworld (this is what I
> just did).
>
> Sorry for all the trouble.

An entry in UPDATING is added and I'm working on a proper fix.

Regards,
Rong-En Fan



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6eb82e0710242350n1156e867r59e4492b57e0a708>