All of lore.kernel.org
 help / color / mirror / Atom feed
From: mjn3@codepoet.org (Manuel Novoa III)
To: Robert de Bath <robert$@mayday.cix.co.uk>
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 10:25:29 -0600	[thread overview]
Message-ID: <20020723162529.GA20550@codepoet.org> (raw)
In-Reply-To: <47f907beec9f97ed@mayday.cix.co.uk>

Robert,

On Tue, Jul 23, 2002 at 09:16:52AM +0100, Robert de Bath wrote:
> On Tue, 16 Jul 2002, Manuel Novoa III wrote:
> 
> > Some of the build changes only make sense if you aren't installing
> > in the default locations as root.
> 
> Humm, Manuel, you do realise that it isn't necessary to install dev86
> to use it don't you?

Yes, although I had some problems in the past.  Don't remember which
version though.  I had an older version of bcc installed (from the
linux distribution I was using) and at one point the newer bcc was
still calling the older bcc-cc1 unless I set BCC_EXEC_PREFIX.

> 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.

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.

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.

Manuel

  reply	other threads:[~2002-07-23 16:25 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 [this message]
2002-07-23 19:09                   ` Robert de Bath
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
  -- strict thread matches above, loose matches on Subject: below --
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=20020723162529.GA20550@codepoet.org \
    --to=mjn3@codepoet.org \
    --cc=linux-8086@vger.kernel.org \
    --cc=rhw@InfraDead.Org \
    --cc=robert$@mayday.cix.co.uk \
    /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.