compile is asking me to report some warnings:
checking for sched_yield... no
checking sched.h usability... no
checking sched.h presence... yes
configure: WARNING: sched.h: present but cannot be compiled
configure: WARNING: sched.h: check for missing prerequisite headers?
configure: WARNING: sched.h: see the Autoconf documentation
configure: WARNING: sched.h: section "Present But Cannot Be Compiled"
configure: WARNING: sched.h: proceeding with the preprocessor's result
configure: WARNING: sched.h: in the future, the compiler will take precedence
configure: WARNING: ## ------------------------------ ##
configure: WARNING: ## Report this to [email protected] ##
configure: WARNING: ## ------------------------------ ##
checking for sched.h... yes
checking for getifaddrs... no
checking ifaddrs.h usability... no
checking ifaddrs.h presence... yes
configure: WARNING: ifaddrs.h: present but cannot be compiled
configure: WARNING: ifaddrs.h: check for missing prerequisite headers?
configure: WARNING: ifaddrs.h: see the Autoconf documentation
configure: WARNING: ifaddrs.h: section "Present But Cannot Be Compiled"
configure: WARNING: ifaddrs.h: proceeding with the preprocessor's result
configure: WARNING: ifaddrs.h: in the future, the compiler will take precedence
configure: WARNING: ## ------------------------------ ##
configure: WARNING: ## Report this to [email protected] ##
configure: WARNING: ## ------------------------------ ##
checking for ifaddrs.h... yes
checking for inet_ntop... no
checking for inet_pton... no
checking arpa/nameser.h usability... no
checking arpa/nameser.h presence... yes
configure: WARNING: arpa/nameser.h: present but cannot be compiled
configure: WARNING: arpa/nameser.h: check for missing prerequisite headers?
configure: WARNING: arpa/nameser.h: see the Autoconf documentation
configure: WARNING: arpa/nameser.h: section "Present But Cannot Be Compiled"configure: WARNING: arpa/nameser.h: proceeding with the preprocessor's result
configure: WARNING: arpa/nameser.h: in the future, the compiler will take precedence
configure: WARNING: ## ------------------------------ ##
configure: WARNING: ## Report this to [email protected] ##
configure: WARNING: ## ------------------------------ ##
checking for arpa/nameser.h... yes
checking for memset... no
checking for socklen_t... no
checking for in_port_t... no
checking value of sizeof((((struct sockaddr_in *) 0) ->sin_port)) by analyzing object code... 0
checking value of sizeof(long) by analyzing object code... 0
checking value of sizeof(int) by analyzing object code... 0
checking value of sizeof(short) by analyzing object code... 0
checking value of sizeof(char) by analyzing object code... 0
checking for h_errno declaration in netdb.h... no
checking for getaddrinfo... no
checking for getnameinfo... no
checking for struct in6_addr... no
checking for struct sockaddr_in6... no
checking for struct sockaddr_storage... no
checking for sa_family_t... no
configure: error: Failed to get size of sa_family in struct sockaddr.
Then it errors as you can see.
Are the warnings and this fail related? Does it look like a problem with my environment or the mipsel compile itself?
Thanks
Rich.
On 10/18/05, Dalibor Topic <[EMAIL PROTECTED]> wrote:
Richard Brady wrote:
> I've had fun this weekend installing Ubuntu on an old 10GB drive. I'm
> guessing Dalibor was joking about that particular Linux flavour but it's
> fine for a noob like me. Had to install a couple of extra packages
> (bison/flex/etc) to get the toolchain compiling but it was pretty
> straightforward.
I currently run Ubuntu on my notebook, among other distros. It's nice. I
change my distributions regularly, though, so now that Breezy is
released, I guess I'll switch to something else for a while. :)
> So Michael, what's my next step? The OpenWrt docs are saying I need to
> write a Makefile and Config.in <http://Config.in> for the new ipkg but
> as I don't really need it packaged up, is there a simpler way to get it
> cross compiling? Can I edit the kaffe configure script to use the
> mipsel compiler?
for cross-compiling you first need a local instance of kaffe built for
your OS and installed, since you'll need the kaffeh tool to generate the
headers for the native libraries in kaffe.
once you've installed kaffe locally, set the environment variable KAFFEH
to /full/path/to/wherever/you/installed/kaffeh so that configure can
pick it up.
Finally, tell configure that you're cross compiling for a different
platform, so pass --build='platform-name-prefix-for-gcc' to configure.
You can find out the platform name prefix by looking sharply at the
supplied toolchain for your platform. For example, if your gcc is called
arm-gnu-linux-gcc , then the prefix is arm-gnu-linux :)
That helps configure find the right tools to end up producing the
correct binaries for your platform.
I hope this helps!
cheers,
dalibor topic
_______________________________________________ kaffe mailing list [email protected] http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
