On Sat, Nov 21, 2009 at 5:52 AM, Peter Jeremy <peterjer...@acm.org> wrote: > I did run into problems initially because my i386 userland wasn't > aligned with my amd64 kernel but rebuilding both fixed that (I'm > running 8.0-RC1 and a bit). > > Note that some tools that poke around in kernel innards won't work - > ps and lsof are the most obvious. ktrace works but the resultant > ktrace.out files need to read with an amd64 kdump.
A word of caution: not all the ioctl's and setsockopt's have the proper glue code under COMBAT_FREEBSD32. For example, running ifconfig on 7.2 i386-on-amd64 is unable to set an ip address, and syscons ioctls are completely broken. The program will build properly, but will be unreliable at runtime (seemingly out of the blue segfaults, a few cases of sigbus). Especially if they do a blind cast without sanity checking and confinue forward on error. While this may not seem that relevant on a build machine, remember that autoconf generates tiny stub binaries and runs them to determine 'compatibility' for the binary it intends to build. It may feed information that will lead it to making incorrect guesses about the target environment. It's not very common, but it has happened, and can fly under the radar. _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
