On Fri, Jun 07, 2002 at 02:44:41AM +0200, Martin Blapp wrote:
> What is the status here ? In my CURRENT system, these compat
> libs are still the old ones :-(
>
> I've now updated the libs manually to be able to run OO
> on CURRENT. And yes - it works. Yes :-))
I don't quite know what you mean b
Hi Terry,
> I saw a posting of some of the breakage. There was a type that
> wasn't defined in scope in a prototype, and then there were a
> couple that were missing (e.g. "unexpected ;") because of some
> bogus includes. I didn't really see anything that I could blame
> on GCC31 itself (I adm
Martin Blapp wrote:
> > 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
>
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
Martin Blapp wrote:
> > Why is it linked against a hacked 4.x libc, instead of an
> > unhacked 5.x libc?
>
> Because gcc31 and libstd++ and stlport are unusable for OpenOffice
> to build. Exceptions are broken. Optimazations are broken.
I think that if this is going to result in MFC's of things
Hi,
> Why is it linked against a hacked 4.x libc, instead of an
> unhacked 5.x libc?
Because gcc31 and libstd++ and stlport are unusable for OpenOffice
to build. Exceptions are broken. Optimazations are broken.
>
> Why is the compat stuff necessary for -current at all?
Because some users like
Martin Blapp wrote:
> What is the status here ? In my CURRENT system, these compat
> libs are still the old ones :-(
>
> I've now updated the libs manually to be able to run OO
> on CURRENT. And yes - it works. Yes :-))
>
> -r--r--r-- 1 root wheel 725012 Jun 7 02:36 libc.so.4
> -r--r--r-- 1
Hi,
What is the status here ? In my CURRENT system, these compat
libs are still the old ones :-(
I've now updated the libs manually to be able to run OO
on CURRENT. And yes - it works. Yes :-))
-r--r--r-- 1 root wheel 725012 Jun 7 02:36 libc.so.4
-r--r--r-- 1 root wheel 675600 Jun 7 02
On Tue, Mar 19, 2002 at 09:34:19AM -0800, David Wolfskill wrote:
> However, the symbol in question does not appear to exist in the version
> of libc.so.4 in -CURRENT's /usr/lib/compat -- and that can cause
> programs which had been compiled under -STABLE and which might well
> otherwise work Just
