On 9 Apr 1999, Joel Ray Holveck wrote:
# > I've found where this problem is coming from. It's in
# > emacs20.3/src/s/freebsd.h. It sets a macro called BSD_SYSTEM based upon the
# > version number contained in __FreeBSD__, checking for 1, 2 and 3. Of
# > course, -current uses 4. I have found th
> I've found where this problem is coming from. It's in
> emacs20.3/src/s/freebsd.h. It sets a macro called BSD_SYSTEM based upon the
> version number contained in __FreeBSD__, checking for 1, 2 and 3. Of
> course, -current uses 4. I have found that you can check for __FreeBSD__ >=
> 3, and it
9:18 PM
To: Steve Price
Cc: Peter Jeremy; curr...@freebsd.org; po...@freebsd.org
Subject: Re: emacs* broken in -current (was Re: Vtable thunks with egcs)
> You are absolutely right. I just tried the new version of emacs
> that I built on my pre-egcs box and it doesn't work on that b
> You are absolutely right. I just tried the new version of emacs
> that I built on my pre-egcs box and it doesn't work on that box
> either. This definitely doesn't appear to be anything caused by
> changing to egcs. Not that it matters much but for grins I just
> built/installed the xemacs por
You are absolutely right. I just tried the new version of emacs
that I built on my pre-egcs box and it doesn't work on that box
either. This definitely doesn't appear to be anything caused by
changing to egcs. Not that it matters much but for grins I just
built/installed the xemacs port and it _
Steve Price wrote:
>The one I'm fretting over right now is emacs. I haven't quite
>figured out why, but invoking it brings up the window, but never
>displays anything in the window. Using a version built with the
>old compiler doesn't seem to make any difference. :(
I submitted ports/10783 cove
On Tue, 6 Apr 1999, David O'Brien wrote:
# > I'm assuming that the default for egcs uses vtable thunks instead of
# > offsets in the vtable to handle multiple inheritance.
#
# At the moment, yes.
#
# > It occurred to me that since this changes the C++ calling convention,
# > we have to bump the
> I'm assuming that the default for egcs uses vtable thunks instead of
> offsets in the vtable to handle multiple inheritance.
At the moment, yes.
> It occurred to me that since this changes the C++ calling convention,
> we have to bump the major version number of all c++ libraries,
> particular
I'm assuming that the default for egcs uses vtable thunks instead of
offsets in the vtable to handle multiple inheritance. It occurred to me
that since this changes the C++ calling convention, we have to bump the
major version number of all c++ libraries, particularly the ones in ports.
--
Doug Ra
