Re: Problem compiling x5250

On Fri, 15 Mar 2013, Aaron Fransen wrote:

Closer! It took me a bit to figure out the autogen stuff (a bit of a source
rookie I'm afraid) but finally got that worked out, but on the next compile
for x5250 I got this far during the make:

x5250term.c: In function ?x5250_terminal_waitevent?:
x5250term.c:1976:8: warning: passing argument 1 of
?XRefreshKeyboardMapping? from incompatible pointer type [enabled by
default]
/usr/include/X11/Xlib.h:3075:12: note: expected ?struct XMappingEvent *?
but argument is of type ?union XEvent *?

I'm not sure if the above is really a problem, but definitely noted.

mv -f .deps/x5250term.Tpo .deps/x5250term.Po
gcc -DDATADIR=\"/usr/local/share\" -g -O2 -l5250 -o x5250 alloccolors.o
debug.o dialog.o help.o mouse.o key.o resources.o x5250.o x5250term.o
-lX11 -lXext
/usr/bin/ld: cannot find -lXext
collect2: ld returned 1 exit status
make[2]: *** [x5250] Error 1
make[2]: Leaving directory `/tmp/x5250/x5250-0.5.3/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/x5250/x5250-0.5.3'
make: *** [all] Error 2

This fails because the compiler can't find libXext.so. I don't know ARM, but check that you have libXext.so on your system, using a command like:

locate libXext

on my system this results in:

jimi@ferrari:~> locate libXext
/var/log/packages/libXext-1.2.0-x86_64-1
/var/log/scripts/libXext-1.2.0-x86_64-1
/usr/doc/libXext-1.2.0
/usr/doc/libXext-1.2.0/xorg.css
/usr/doc/libXext-1.2.0/INSTALL
/usr/doc/libXext-1.2.0/dpmslib.html
/usr/doc/libXext-1.2.0/README
/usr/doc/libXext-1.2.0/dpmslib.xml
/usr/doc/libXext-1.2.0/dbelib.xml
/usr/doc/libXext-1.2.0/synclib.html
/usr/doc/libXext-1.2.0/COPYING
/usr/doc/libXext-1.2.0/synclib.xml
/usr/doc/libXext-1.2.0/dbelib.html
/usr/doc/libXext-1.2.0/ChangeLog
/usr/doc/libXext-1.2.0/AUTHORS
/usr/doc/libXext-1.2.0/shapelib.xml
/usr/doc/libXext-1.2.0/shapelib.html
/usr/lib64/libXext.so.6.4.0
/usr/lib64/libXext.la
/usr/lib64/libXext.so
/usr/lib64/libXext.so.6

Those last four lines are the ones that count.

James Rich

if you want to understand why that is, there are many good books on
the design of operating systems. please pass them along to redmond
when you're done reading them :)
- Paul Davis on ardour-dev