Thread View: gnu.gcc.bug
2 messages
2 total messages
Started by Ian G Batten, Ian G Batten
Thu, 31 Dec 1992 11:08
Emacs with GCC 2.3.3
Author: Ian G Batten, Ian G Batten
Date: Thu, 31 Dec 1992 11:08
Date: Thu, 31 Dec 1992 11:08
5 lines
627 bytes
627 bytes
My previous message is in error. The mistake was that I had not run the fixincludes script. Interestingly, emacs compile correctly without fixincludes having been run but does not execute correctly. ian
Re: Emacs with GCC 2.3.3
Author: Michael Traub
Date: Sat, 02 Jan 1993 16:50
Date: Sat, 02 Jan 1993 16:50
22 lines
1293 bytes
1293 bytes
In article <C04Exp.4u@fulcrum.co.uk> I.G.Batten@fulcrum.co.UK (Ian G Batten, Ian G Batten) writes:
>My previous message is in error. The mistake was that I had not run the
>fixincludes script. Interestingly, emacs compile correctly without
>fixincludes having been run but does not execute correctly.
Not that interesting. Many old compilers have macros for ioctls like so:
#define TIOCSETD _IOW('t', 1, int) /* set line discipline */
Which won't work with an Ansi compiler (you'll just get an ioctl with
the character 't' as the argument). Fixincludes changes them to:
#define TIOCSETD _IOW(t, 1, int) /* set line discipline */
It's not surprising that your un'fixinclude'd version didn't work.
--
Michael Traub
BT Customer Systems, Brighton Systems Centre. traub@btcs.bt.co.uk
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads