From owner-freebsd-current Thu Jun 6 23:41:41 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 0EC1937B407; Thu, 6 Jun 2002 23:41:36 -0700 (PDT) Received: from nbs.imp.ch (nbs.imp.ch [157.161.4.7]) by mail.imp.ch (8.11.6/8.11.6) with ESMTP id g576fY667064; Fri, 7 Jun 2002 08:41:34 +0200 (CEST) Received: from levais.imp.ch (levais.imp.ch [157.161.4.66]) by nbs.imp.ch (8.12.3/8.12.3) with ESMTP id g576fX9013645111; Fri, 7 Jun 2002 08:41:33 +0200 (MES) Date: Fri, 7 Jun 2002 08:42:43 +0200 (CEST) From: Martin Blapp To: Terry Lambert Cc: , , Subject: Re: nl_langinfo is MFCed, but what about compat/libc.so.4? In-Reply-To: <3D00263D.B369F344@mindspring.com> Message-ID: <20020607083712.F11797-100000@levais.imp.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi > I think that if this is going to result in MFC's of things that > change the libraries for 4.6, that the update of the libc image > in 5.x for -compat is going to have to wait for 4.6-RELEASE. That's a good idea. > I also think that it may mean another major version number change, > since there's aren't real minor version numbers any more. 8-(. That surly not necessary. We only have major version number change if we change from Releng Majors 3->4, 4->5. This is just compat stuff, and CURRENT is not yet production. > > so it doesn't coredump anymore doing the tests. Which means > > fixing gcc31 in CURRENT, since the package was build on STABLE > > with gcc31 from ports. > > That last sentence is hard to parse unambiguously. stlport breacks within openoffice in CURRENT, or seperatly build as a port. I'll have to test if it breaks also with the newest snapshot from ports. > Are you saying that it breaks because of -current, or are you > saying it breaks because of the compiler change, or are you > saying that the compiler in ports is different than the compiler > that's now in 5.x? I guess the latest is true. We have a newer snapshot in ports than in CURRENT. It will be true if gcc31 in CURRENT can build it and make a running version. > As a note, I would ask if "DESTDIR" was being set or not? It > may be that the reason it's working is that you are getting the > old compiler headers instead of the new ones, when you compile > it with the new compiler on -stable (I've noted this problem > before; the first time was in 1998). That's not possible. I'd get to many errors then. I've gcc31 specific includes and they work fine. Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message