This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Where is this information set inside the gcc compilation?? I thought that cygwin would handle paths at the "last stage" before opening the file, rather than GCC being compiled in a set of DOS paths as its search locations?? Any ideas??
Look for calls like this in gcc/gcc.c: add_prefix (&include_prefixes, ... and other references to include_prefixes if you really want to understand that. I added print statements to that call recently to try to understand how the include path was built.
$ arm-epoc-pe-g++ dialog.cpp -I/opt/symbian/UIQ_21/include --verbose Reading specs from c:\cygwin\opt\symbian\UIQ_21\bin\..\lib\gcc-lib\arm-epoc-pe\2.9-psion-98r2\s pecs gcc version 2.9-psion-98r2 (Symbian build 546)
c:\cygwin\opt\symbian\UIQ_21\bin\..\lib\gcc-lib\arm-epoc-pe\2.9-psion-98r2\c
pp.exe -lang-c++ -v -I/opt/symbian/UIQ_21/include -iprefix
c:\cygwin\opt\symbian\UIQ_21\bin\..\lib/gcc-lib/arm-epoc-pe\2.9-psion-98r2\ -undef -D__GNUC__=2 -D__GNUG__=2 -D__cplusplus -D__GNUC_MINOR__=9 -Darm -D__
pe__ -D__declspec(x)=__attribute__((x)) -D__arm__ -D__pe__ -D__declspec(x)=_
_attribute__((x)) -D__arm -Acpu(arm) -Amachine(arm) -D__EXCEPTIONS -D__CHAR_
UNSIGNED__ -D__ARM_ARCH_4T__ -D__APCS_32__ dialog.cpp
/cygdrive/c/DOCUME~1/ADMINI~1/LOCALS~1/Temp\ccAtCGUw.ii
GNU CPP version 2.9-psion-98r2 (Symbian build 546) (ARM/EPOC/PE)
#include "..." search starts here:
#include <...> search starts here:
c:\cygwin\opt\symbian\UIQ_21\bin\..\lib\gcc-lib\arm-epoc-pe\2.9-psion-98r2\i nclude
c:\cygwin\opt\symbian\UIQ_21\bin\..\lib\gcc-lib\arm-epoc-pe\2.9-psion-98r2\. .\..\..\..\arm-epoc-pe\include End of search list. In file included from dialog.cpp:1: dialog.h:3: eikdialg.h: No such file or directory dialog.cpp:6: eikchlst.h: No such file or directory
Hey, you gave a -I option, and that directory didn't make it into your search path! That seems pretty suspicious. You might try tracking that down.
By the way, perhaps the problem is you're configuring and building in a way that differs from how Symbian did it? According to http://www.symbian.com/developer/downloads/files/gccreadme.txt they had their own little script that set everything up just so... - Dan
------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |