[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pcc-list
Subject:    RE: should cpp, pcc, and man pages include target
From:       greg () bitlynx ! com
Date:       2008-10-15 20:49:12
Message-ID: 20081015134912.ab62c74ef4fdac7a72bd4f4cde8f70c1.4cb31d0b52.wbe () email ! secureserver ! net
[Download RAW message or body]


> I built with ./configure -target=i386-unknown-netbsd4.99.62
> 
> And this resulted in the following installed:
> 
> bin/i386-unknown-netbsd4.99.62-pcc
> libexec/i386-unknown-netbsd4.99.62-cpp
> libexec/i386-unknown-netbsd4.99.62-ccom
> share/man/man1/i386-unknown-netbsd4.99.62-pcc.1
> share/man/man1/i386-unknown-netbsd4.99.62-cpp.1
> share/man/man1/i386-unknown-netbsd4.99.62-ccom.1
> 
> And target also embedded into tools, for example:
> 
> tx:pcc$ /home/reed/tmp/pcc/bin/i386-unknown-netbsd4.99.62-pcc -v ~/tmp/test.c 
> pcc 0.9.9 for i386-unknown-netbsd4.99.62, reed@tx.reedmedia.net Wed Oct 15 08:05:29 \
>                 CDT 2008
> /home/reed/tmp/pcc/libexec/i386-unknown-netbsd4.99.62-cpp -v -D__PCC__=0 \
> -D__PCC_MINOR__=9 -D__PCC_MINORMINOR__=9 -D__NetBSD__ -D__ELF__ -D__i386__ -S \
> /home/reed/tmp/pcc/i386-unknown-netbsd4.99.62/include -I \
> /home/reed/tmp/pcc/lib/pcc/i386-unknown-netbsd4.99.62/0.9.9/include/ \
> /home/reed/tmp/test.c /tmp/ctm.15017b
cpp: pcc 0.9.9 for i386-unknown-netbsd4.99.62, reed@tx.reedmedia.net Wed
Oct 15 08:05:29 CDT 2008 /home/reed/tmp/test.c:2: error: cannot find
'stdint.h'
> 
> Is that normal? Correct behaviour?

The build has determined that the target is different to the build/host
machine and built a cross-compiler.  So everything looks okay.

Maybe you want to cross-build, rather than build a cross compiler?  Try
specifying --host=i386-unknown-netbsd4.99.62 also.  This should tell
configure that the host and target machines are the same.  Then it won't
prefix the executables and modify the paths.

> I don't see how manual pages should be installed with different name.

Maybe.  I didn't check if there was precedence in this matter.  The
manpages are installed with the same names as the executables.

> And does cpp and pcc (front-end) change depending on target? 

The pcc front-end is heavily host dependent.

> (libexec/i386-unknown-netbsd4.99.62-ccom makes sense to me though.)
> 
> Also the built-in include paths (like -S 
> /home/reed/tmp/pcc/i386-unknown-netbsd4.99.62/include) seems wrong too. I 
> worked around that using "-isystem /usr/include".
> 
> Also is the default as(1) name as i386-unknown-netbsd4.99.62-as correct 
> also?

For a cross-compiler, it is.


[prev in list] [next in list] [prev in thread] [next in thread]