> Library functions aren't available to kernel modules directly.
["server" modules I presume] ah ok I understand, the exported symbols list
is in fact restricted to the xf86* functions and symbols directly
generated by the server... strange that I really did not miss the C
library so far :-)
This means I will have to provide a version of the __divdi3 function in
the module itself -- ok, I can just link in libgcc (or at least the
relevant object), but the moment some other module wants to do the same I
will get module load failures due to duplicate symbols
> I'm not sure that all supported compilers/platforms support long long
>
> If you actually want a 64 bit type, I don't know whether it would
> be more sensible to define INT64 for your platform in xc/include/Xmd.h ?
I can declare it, but this still does not make the required symbol
available from libgcc; besides at the moment I want to get it working at
all before thinking too much about other platforms
Best regards
--
Helge Bahmann <[EMAIL PROTECTED]> /| \__
The past: Smart users in front of dumb terminals /_|____\
_/\ | __)
$ ./configure \\ \|__/__|
checking whether build environment is sane... yes \\/___/ |
checking for AIX... no (we already did this) |
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
