From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: bug-guile@gnu.org
Subject: Re: Error in guile-1.6.0/include/libguile/eval.h
Date: 19 Oct 2002 16:57:12 +0200 [thread overview]
Message-ID: <87u1jixyrb.fsf@zagadka.ping.de> (raw)
In-Reply-To: <Pine.GSO.4.44.0210181449560.15082-100000@sunhalle99>
Christof Boeckler <boeckler@informatik.tu-muenchen.de> writes:
> Then it worked on Solaris 8 with gcc 3.0.4, GNU make 3.79.1.
> I hope, that is helpful information for all you gurus ;-)
It is, thanks!
I've fixed eval.h as you describe, but I'm unsure why this is
necessary. ANSI C does not specify in what places "..." include files
are looked for, but I always thought that "..." would look first in
the directory hat contains the currently processed file, and then in
the places that <...> looks in. Isn't that how it works?
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
prev parent reply other threads:[~2002-10-19 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 12:56 Error in guile-1.6.0/include/libguile/eval.h Christof Boeckler
2002-10-19 14:57 ` Marius Vollmer [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87u1jixyrb.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=bug-guile@gnu.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 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).