Date: Thu, 10 Feb 2000 12:49:43 -0500 (EST) From: Lyndon Griffin <lgriffin@bsd4us.org> To: freebsd-sparc@freebsd.org Subject: Cross-compiler question Message-ID: <Pine.BSO.4.10.10002101244260.30411-100000@ns.bsd4us.org>
next in thread | raw e-mail | index | archive | help
OK - so, everything is looking good for me getting a working toolchain up from FreeBSD 3.4 to sparc-netbsd (32-bit toolchain, though 64-bit shouldn't be much different). As soon as I get it done, I am going to publish the steps to getting it done as well as probably make a tarball or package or something that people can use to skip all the fancy hacking necessary to get it working ;) I have one question, and it's probably a stupid one, but it's got me stumped... Scenario: I'm building the toolchain to install in /usr/sparc. So far, I've had to copy /usr/include to /usr/sparc/include and set appropriate flags in the makefiles. Everything seems to be going ok, until I get into the actual gcc compiling. At this point, it seems relectant to look in /usr/include or /usr/sparc/include for any of the files that I've placed there. I keep having to hard-code things like this: changing #include <stdlib.h> to #include "/usr/sparc/include/stdlib.h" to get things moving along. As this is usually A Bad Thing (tm), and since I'm sure there's a better way to make this happen, can anyone shed any light? Thanks, <:) Lyndon Griffin http://www.bsd4us.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-sparc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSO.4.10.10002101244260.30411-100000>