All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert de Bath <robert$@mayday.cix.co.uk>
To: Manuel Novoa III <mjn3@codepoet.org>
Cc: Riley Williams <rhw@InfraDead.Org>,
	Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: C compiler, assembler and linker
Date: Tue, 23 Jul 2002 20:09:32 +0100 (BST)	[thread overview]
Message-ID: <423bf9356790bf97@mayday.cix.co.uk> (raw)
In-Reply-To: <20020723162529.GA20550@codepoet.org>

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 <robert$ @ debath.co.uk>)
                                       <http://www.cix.co.uk/~mayday>




  reply	other threads:[~2002-07-23 19:09 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-14 14:05 C compiler, assembler and linker Harry Kalogirou
2002-07-14 17:27 ` Manuel Novoa III
2002-07-15  6:07   ` Riley Williams
2002-07-15 17:02     ` Manuel Novoa III
2002-07-15 19:13       ` Riley Williams
2002-07-15 22:02         ` Manuel Novoa III
2002-07-16  6:27           ` Riley Williams
2002-07-17  1:31             ` Manuel Novoa III
2002-07-17  6:33               ` Riley Williams
2002-07-18 12:03                 ` Minix vs. ELKS Feher Tamas
2002-07-18 12:27                   ` Javier Sedano
2002-07-02 15:07                     ` (unknown) Miguel A. Bolanos
2002-07-18 13:40                   ` Minix vs. ELKS Alan Cox
2002-07-22 21:41                 ` C compiler, assembler and linker Robert de Bath
2002-07-23  8:16               ` Robert de Bath
2002-07-23 16:25                 ` Manuel Novoa III
2002-07-23 19:09                   ` Robert de Bath [this message]
2002-07-24 21:17         ` More dev86 changes (0.16.5) Robert de Bath
2002-07-24 22:02           ` Riley Williams
2002-07-25 15:42             ` Manuel Novoa III
2002-07-26  7:55               ` Robert de Bath
2002-07-26 15:12                 ` Manuel Novoa III
2002-07-26  8:22             ` Robert de Bath
2002-07-24 22:26           ` Paul Nasrat
2002-07-25 16:34             ` Manuel Novoa III
2002-07-22 23:26       ` C compiler, assembler and linker Robert de Bath
2002-07-23  0:34         ` Riley Williams
2002-07-23  0:58           ` Manuel Novoa III
2002-07-23  0:46         ` Manuel Novoa III
2002-07-15 14:16 Ken Martwick
2002-07-15 19:21 ` Riley Williams

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=423bf9356790bf97@mayday.cix.co.uk \
    --to=robert$@mayday.cix.co.uk \
    --cc=linux-8086@vger.kernel.org \
    --cc=mjn3@codepoet.org \
    --cc=rhw@InfraDead.Org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.