public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktd at club-internet dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/12300] New: gcc fails looking for "home frameworks" under MacOS X
Date: Tue, 16 Sep 2003 14:24:00 -0000	[thread overview]
Message-ID: <20030916132231.12300.ktd@club-internet.fr> (raw)

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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

           Summary: gcc fails looking for "home frameworks" under MacOS X
           Product: gcc
           Version: 3.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: other
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: ktd at club-internet dot fr
                CC: gcc-bugs at gcc dot gnu dot org

Hello,

I'm using MacOS 10.2.6 and gcc 3.1
When I compile an use frameworks, gcc is supposed to look for /System/Library/Frameworks, /
Library/Frameworks and ~/Library/Frameworks.
When I made a framework for the first time, I put it into ~/Library/Frameworks
However, when compiling a code using my frameworks headers, gcc reported that it could not find 
them.
I tried to force him to find using the option -F~/Library/Frameworks, but it didn't work
So I tried instead -F/Users/me/Library/Frameworks and then it worked.

If my frameworks are into /Library/frameworks, there are no problems.

Does that mean that gcc opens a new shell where "~" is undefined ?

Thanks,

Pierre Chatelier


             reply	other threads:[~2003-09-16 13:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-16 14:24 ktd at club-internet dot fr [this message]
2003-09-16 16:03 ` [Bug other/12300] " pinskia at gcc dot gnu dot org

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=20030916132231.12300.ktd@club-internet.fr \
    --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).