From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert de Bath Subject: Re: C compiler, assembler and linker Date: Tue, 23 Jul 2002 20:09:32 +0100 (BST) Sender: linux-8086-owner@vger.kernel.org Message-ID: <423bf9356790bf97@mayday.cix.co.uk> References: <20020723162529.GA20550@codepoet.org> Mime-Version: 1.0 Return-path: In-Reply-To: <20020723162529.GA20550@codepoet.org> List-Id: Content-Type: TEXT/PLAIN; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Manuel Novoa III Cc: Riley Williams , Linux-8086 On Tue, 23 Jul 2002, Manuel Novoa III wrote: > > I just put these two lines in a script in my $HOME/bin directory. > > > > #!/bin/sh - > > exec /usr/src/linux_86/bin/ncc "$@" > > I use a similar script (with options and include path overrides), but I > was using bcc rather than ncc. That's the difference; ncc looks in directories relative to where it is on the fielsystem, bcc looks in 'standard' places. > BTW, there was one other mod in my bcc patch that I forgot to mention. > Since bcc doesn't support ## for token pasting, I was using the old k&r > method (where /**/ doesn't get mapped to space as in ANSI C). But > > #define __PASTE(x,y) x/**/y > > wasn't working for me, so I patched things so it would. That was some > time ago though, so I don't know if it is still a problem with stock > bcc. I'd looked at that line several times but didn't do anything about it. But it _is_ a K&R compiler so it probably should do K&R pasting. > Oh yes, and I had modifed the flags for ncc in the dev86 build to > include -ansi because the ELKS headers have now been ansi-fied. XXXX Rant about BCC being a K&R compiler deleted! -- Rob. (Robert de Bath )