John Polstra wrote:
> David O'Brien wrote:
>
> > Since the Linux config files specify DEFALUT_VTABLE_THUNKS=1, no one
> > has posted a bug report related to them, there is an option to turn
> > them off, and this *is* -CURRENT. I may just leave them turned on by
> > default.
> >
> > Opinions?
>
>
On Fri, 30 Apr 1999, David O'Brien wrote:
> > These are good questions, and I don't know enough yet about the issues
> > surrounding vtable thunks to answer them.
>
> I haven't had time to really dig into this yet. Hopefully Saturday. I'm
> about to revert the change until I can see what the
On Fri, 30 Apr 1999, David O'Brien wrote:
> > These are good questions, and I don't know enough yet about the issues
> > surrounding vtable thunks to answer them.
>
> I haven't had time to really dig into this yet. Hopefully Saturday. I'm
> about to revert the change until I can see what the
On Fri, 30 Apr 1999, David O'Brien wrote:
# > These are good questions, and I don't know enough yet about the issues
# > surrounding vtable thunks to answer them.
#
# I haven't had time to really dig into this yet. Hopefully Saturday. I'm
# about to revert the change until I can see what the
David O'Brien wrote:
> I haven't had time to really dig into this yet. Hopefully Saturday.
> I'm about to revert the change until I can see what the problem
> is and what the upgrade issues will be. EGCS 1.2 *should* be out
> in the July/Aug time frame. Of course I will try to upgrade us
> to i
> These are good questions, and I don't know enough yet about the issues
> surrounding vtable thunks to answer them.
I haven't had time to really dig into this yet. Hopefully Saturday. I'm
about to revert the change until I can see what the problem is and what
the upgrade issues will be. EGCS
In article ,
Steve Price wrote:
> Fair enough, but the problem that really concerns me is that
> all the C++ libraries (and the programs that use them) will have
> to be recompiled when we make the switch. Is there a programatic
> way to tell which vtable implementation a library was compiled
>
On Thu, 29 Apr 1999, John Polstra wrote:
#> - Forwarded message from Steve Price -
#>
#> Since the vtable thunks are more efficient and will eventually
#> be the default, we might ought to stick with them. David mentioned
#> that there might be problems with them, but with enough develo
> - Forwarded message from Steve Price -
>
> Since the vtable thunks are more efficient and will eventually
> be the default, we might ought to stick with them. David mentioned
> that there might be problems with them, but with enough developers
> using -current to beat out the kinks we
- Forwarded message from Steve Price -
#> Remember you asked. :-)
#>
#> [ patch elided ... ]
#
# Thank you sir! I recompiled cc and friends, then the libstdc++, and
# Shazam! everything works again. Haven't done an extensive test, but KDE
# works and my X10 daemon :-)
#
# Thank you, than
Steve Price wrote:
> On Wed, 28 Apr 1999, David O'Brien wrote:
>
> # > /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined
> # > symbol "__vt_7filebuf"
> #
> # I'm rather tied up until Sunday. So it will be few days unti I can
> # really take a look at this. Until then, patches gladly a
David O'Brien wrote:
> > Aagh! As of last-night's current (Tuesday), *NO* C++ program that
> > links against libstdc++ works now. All of them come up with this
> > error, and recompilation doesn't help :-(
>
> You have done a *FULL* CVSup and `make world'? You have then recopiled
> any C++ libs f
On Wed, 28 Apr 1999, David O'Brien wrote:
# > /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined
# > symbol "__vt_7filebuf"
#
# I'm rather tied up until Sunday. So it will be few days unti I can
# really take a look at this. Until then, patches gladly accepted.
Remember you asked. :-
> /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined
> symbol "__vt_7filebuf"
I'm rather tied up until Sunday. So it will be few days unti I can
really take a look at this. Until then, patches gladly accepted.
--
-- David(obr...@nuxi.com -or- obr...@freebsd.org)
To Unsubscri
At 03:39 PM 4/28/99 -0700, David O'Brien wrote:
Aagh! As of last-night's current (Tuesday), *NO* C++ program that
links against libstdc++ works now. All of them come up with this
error, and recompilation doesn't help :-(
You have done a *FULL* CVSup and `make world'? You have then recopiled
an
> Aagh! As of last-night's current (Tuesday), *NO* C++ program that
> links against libstdc++ works now. All of them come up with this
> error, and recompilation doesn't help :-(
You have done a *FULL* CVSup and `make world'? You have then recopiled
any C++ libs from ports or private sources?
--
Aagh! As of last-night's current (Tuesday), *NO* C++ program that
links against libstdc++ works now. All of them come up with this
error, and recompilation doesn't help :-(
On my machine, this killed the entire KDE system. All of those
programs come up with the error:
/usr/libexec/ld-elf.so.1: /u
17 matches
Mail list logo
