From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Date: Thu, 13 Jul 2000 09:59:47 +0000 From: "Douglas A. Gwyn" Message-ID: <396D2D91.7148F4FA@null.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <20000712141620.A1017@cyber-dyne.com>, <20000712174455.A20431@gmx.net> Subject: Re: [9fans] Silly porting fun Topicbox-Message-UUID: da4e973c-eac8-11e9-9e20-41e7f4b1d025 Latchesar Ionkov wrote: > Anyway, if you add > #include "u.h" > #include "libc.h" > in your minimal program it will compile and link just fine. I think you miss the point. The "configure" script tries to compile a *standard-conforming* test program in an attempt to detect a usable C compiler on the system. The test program must *not* be platform-specific. The main problem of course is that the configure script only probes for things that have been previously discovered about various porting targets. It apparently doesn't know how to find the Plan9 APE environment, i.e. "pcc" is not one of the names it tries to find a C compiler. My guess is that adding "pcc" to the list *before* "cc" will get past that particular snag. There may be other snags; the other day I had a GNUish package fail to autoconfigure due to there being a "gcc" in my path (effectively a union /bin) that was not a native compiler (it was a cross-compiler for an embedded processor).