* when preprorcessed glapi_x86.S ends up being invalid assembler input
because of whitespace problems in concatenation macros. normally the
use of these macros as they are wouldn't be a problem except we are
receiving -traditional-cpp from share/mk and the spaces are being
passed.
XXX further discussion needs to occur in order for this to be properly
fixed
building so far:
doc include dix fb mi miext randr render
again based on the work rtr made for xorg support, and of course this
is very much based on the work lukem did originally for src/x11, as is
all the stuff in src/external/mit/xorg.
hi luke! :)
without subsequently doing anything with it, so commit_address()
works with an address with phase == 0. phase == 0 is not allowed,
hence
random84# ifconfig nfe0 atalk 3.14
ifconfig: SIOCAIFADDR: Invalid argument
Solution: copy the new sockaddr_at to a temporary input environment,
and pass that environment to commit_address(). I may as well copy
the new sockaddr_at to the output environment, while I am at it.
types loaded into rump. Now it is possible to iterate over all
file system types supported by a rump program in an attempt to
access an unknown file system image instead of having to know
beforehand which type of file system is on the image.
only in the AF_UNSPEC/AF_INET/AF_INET6 cases. Maybe this will fix
the AF_APPLETALK problem that is@ reports:
random84# ifconfig nfe0 atalk 3.14
ifconfig: SIOCAIFADDR: Invalid argument
system modules for use. Sneakily this solves the problem with the
dynamic linker not wanting to handle the modules link set for
binaries where more than one file system library is included during
the link phase and therefore only one of the file systems getting
vfs_attach()ed in rump "boot". But more importantly, this is really
TRTTD, since now applications can be built, linked and shipped
completely independently of the file systems they support.
tested by Arnaud Ysmal
mrg