I think the problem arises while running makekeys. I have checked that
it is executable file
   [ ELF executable , 64-bit ......]
     The file keysymdef.h exitst. When I manually execute makekeys with the
same arguments I
     get the same result. i.e. Floating point exception.
     I have applied the patch mentioned on the page.

     The error is not in make. Then where is the error?

      Thanks in advance.

I'm afraid that I don't really have a concrete answer for you, but I
found two threads that might be of some help to you:

http://lists.freedesktop.org/archives/xorg/2006-June/015852.html
http://people.debian.org/~terpstra/message/20060912.125004.034e1b10.en.html

I don't know if you found those threads previously of if they'll
really be any help to you, but I thought that I'd point them out.  The
first basically seems to say to use the GIT version of libx11 instead
of the CVS version, but it's about 7 months old, so I would have
thought that it would no longer be an issue. On top of that, I would
assume that you're using a version of the files taken from the links
given in CBLFS as opposed to the CVS or GIT versions.

The second thread basically says that it could be a version mismatch.
Now it IS Ubuntu related, so it may not be terribly helpful, but I
think that it's well worth trying an older version of a package or two
if you've been using the newest versions.  Sometimes the newest ones
don't play well together.  If you can figure out which package or
packages don't agree with one another, then you can probably downgrade
one or all involved and be fine.

I'm sorry that I can't be of more help, but I thought that I'd give
what little information I had.  So, my best suggestion would be to
figure out which packages are too new and downgrade them.  Worst comes
to worst, just use the Xorg 7.1 files and don't use any of the newer
versions.

- Jonathan M Davis
_______________________________________________
Clfs-support mailing list
[email protected]
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support

Reply via email to