This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/12300] New: gcc fails looking for "home frameworks" under MacOS X
- From: "ktd at club-internet dot fr" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 16 Sep 2003 13:22:32 -0000
- Subject: [Bug other/12300] New: gcc fails looking for "home frameworks" under MacOS X
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
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