public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nick Kurshev <nickols_k@mail.ru>
To: Neil Booth <neil@daikokuya.demon.co.uk>
Cc: gcc@gcc.gnu.org
Subject: Re: Strange gcc-3.0.1 preprocessor
Date: Mon, 15 Oct 2001 10:59:00 -0000	[thread overview]
Message-ID: <20011015190353.3be9d593.nickols_k@mail.ru> (raw)
In-Reply-To: <20011014190904.A16465@daikokuya.demon.co.uk>

Hello, Neil!
On Sun, 14 Oct 2001 19:09:04 +0100, you wrote:

> Nick Kurshev wrote:-
> 
> > But for me - no.
> 
> I don't believe you.
> 
> > #undef __MACHINE__
> > #define __MACHINE__ ia32
> >     #define _INLINES <biewlib/sysdep/__MACHINE__/_inlines.h>
> >     #define __CONFIG <biewlib/sysdep/__MACHINE__/__config.h>
> >     #include __CONFIG
> >     #include _INLINES
> > 
> > In file included from biewlib/biewlib.c:24:
> > biewlib/sysdep/__config.h:27:14: warning: pasting "/" and "__MACHINE__" does not give a valid preprocessing token
> > biewlib/sysdep/__config.h:27:22: biewlib/sysdep/__MACHINE__/__config.h: No such file or directory
> > make: *** [biewlib/biewlib.o]  1
> 
> Why is it complaining about pasting?  I don't think the code you quote
> above is not the code you are using; the code you are using still has
> the ## that I asked you to remove.
> 
Yes! You are perfectly right.
I cleaned not all such places.
Now it works. Thanks!
> Neil.
> 


Best regards! Nick

      reply	other threads:[~2001-10-15 10:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-14  7:46 Nick Kurshev
2001-10-14  8:12 ` Neil Booth
2001-10-14 10:45   ` Nick Kurshev
2001-10-14 10:59     ` Neil Booth
2001-10-14 11:06       ` Nick Kurshev
2001-10-14 11:09         ` Neil Booth
2001-10-15 10:59           ` Nick Kurshev [this message]

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=20011015190353.3be9d593.nickols_k@mail.ru \
    --to=nickols_k@mail.ru \
    --cc=gcc@gcc.gnu.org \
    --cc=neil@daikokuya.demon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).