Re: emacs* broken in -current (was Re: Vtable thunks with egcs)
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 that you can check for __FreeBSD__ >= # > 3, and it will work, but this feels a bit like a hack. I've never updated a # > port, so I can either get some instruction from someone to put in a patch, # > or let someone else do it. # # I'll make the patch if a committer can get it in. Send it to me. I'll commit it. :) BTW, good catch David! -steve # -- # Joel Ray Holveck - jo...@gnu.org #Fourth law of programming: #Anything that can go wrong wi # sendmail: segmentation violation - core dumped # To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: emacs* broken in -current (was Re: Vtable thunks with egcs)
> 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 will work, but this feels a bit like a hack. I've never updated a > port, so I can either get some instruction from someone to put in a patch, > or let someone else do it. I'll make the patch if a committer can get it in. -- Joel Ray Holveck - jo...@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
RE: emacs* broken in -current (was Re: Vtable thunks with egcs)
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 will work, but this feels a bit like a hack. I've never updated a port, so I can either get some instruction from someone to put in a patch, or let someone else do it. David Deatherage -Original Message- From: Joel Ray Holveck [mailto:jo...@gnu.org] Sent: Thursday, April 08, 1999 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 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 _does_ appear to work. I've been having no problems with an Emacs 20.3 and X11R6 built in October on a -current system from April 6. (The Emacs is ELF, and built from my own sources instead of the port.) I'd like to track this down; could people give me more info privately? rms is looking at releasing a mostly bugfix Emacs, possibly tommorow, but it may be another month (he's about to leave town). I haven't been watching the changes; there may be some X-related fixes in there. Cheers, joelh -- Joel Ray Holveck - jo...@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
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 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 _does_ appear to work. I've been having no problems with an Emacs 20.3 and X11R6 built in October on a -current system from April 6. (The Emacs is ELF, and built from my own sources instead of the port.) I'd like to track this down; could people give me more info privately? rms is looking at releasing a mostly bugfix Emacs, possibly tommorow, but it may be another month (he's about to leave town). I haven't been watching the changes; there may be some X-related fixes in there. Cheers, joelh -- Joel Ray Holveck - jo...@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
