public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "brian at dessent dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/35916] problem running GCC under Vista with relocated directory
Date: Sun, 20 Apr 2008 08:29:00 -0000	[thread overview]
Message-ID: <20080420082823.4767.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35916-15052@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from brian at dessent dot net  2008-04-20 08:28 -------
Subject: Re:  problem running GCC under Vista with relocated 
 directory

As pointed out in <http://gcc.gnu.org/ml/fortran/2008-03/msg00120.html>,
config/mh-mingw contains BOOT_CFLAGS += -D__USE_MINGW_ACCESS.  Does this
setting get applied only when building gcc, or does it apply to target
libraries too?  Because there are places in libiberty (e.g.
make-relative-prefix.c) where access() is called, and so libiberty needs
to be built with -D__USE_MINGW_ACCESS if it is to contain the Vista
workaround.

If the above host fragment only applies to gcc, then I think it will
still be necessary to override BOOT_CFLAGS and CFLAGS when invoking
make.

Brian


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35916


  parent reply	other threads:[~2008-04-20  8:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-12 17:47 [Bug fortran/35916] New: problem running gfortran 4.4.0 in Vista DHConsultancy at skynet dot be
2008-04-12 18:08 ` [Bug fortran/35916] " pinskia at gcc dot gnu dot org
2008-04-13  0:07 ` brian at dessent dot net
2008-04-13 16:12 ` DHConsultancy at skynet dot be
2008-04-16 17:49 ` pinskia at gcc dot gnu dot org
2008-04-16 21:03 ` [Bug driver/35916] problem running GCC under Vista with relocated directory steven at gcc dot gnu dot org
2008-04-20  8:29 ` brian at dessent dot net [this message]
2008-04-20  8:44 ` brian at dessent dot net
2008-04-24 17:42 ` bartoldeman at users dot sourceforge dot net
2008-06-03  4:30 ` pinskia at gcc dot gnu dot org
2008-06-03  4:32 ` pinskia at gcc dot gnu dot org
2008-06-03  4:33 ` pinskia at gcc dot gnu dot org
2008-06-04  8:23 ` dannysmith at users dot sourceforge dot net
2008-06-05  3:47 ` dannysmith at gcc dot gnu dot org
2008-06-05  6:24 ` dannysmith at users dot sourceforge dot net

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=20080420082823.4767.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.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).