G
Guest
Guest
Archived from groups: alt.games.mame (More info?)
Hello all,
I am attemtping a compile of the vanilla xmame 0.92 source. I have a
Redhat Fedora Core 3 box. Unfortunately, I did a binary install of
redhat without much source. I don't have the redhat disks anymore so I
can't load source off them.
My compile has made it a long way, but I am hacking various things at
this point and beginning to feel like I am reaching beyond my skill
level. A little advice from some gurus would be great.
1) At first the compile couldn't find Xlib.h. So I went and got
XFree86 source rpm off the net and installed it. I installed
XFree86-4.3.0-55.src.rpm, untarred the source, adjusted the include
directive in the make file and attempted a build. This time it got
further, but then I got a bunch of syntax errors. It turns out that
some paths assumed in the #includes were not there. I fixed them up
with sym links inside the expanded XFree source tree and got it to
compile. Is this a typical experience? Or am I doing something the
hard way with regards to snagging source from the net? After installing
the source rpm I kind of expected the source to be expanded somewhere.
It wasn't. It was just sitting in a gzipped tar ball out in
/usr/src/redhat/SOURCES. So I manually untarred to a working dir along
side of my xmame source. Is this typical? I feel like I am missing
some step in the source file installation process.
2) When I installed the XFree86 source rpm it came with a slew of .patch
files. Uh, was I supposed to use these somehow? I didn't. I saw the
full source tar ball sitting there and went for that. My main question
here is: are those patch files supposed to be applied to that source in
the tar ball or is the bundled source already patch-applied?
3) Well, with the compile complete it is on to linking problems. I
found that some of my libs were not being picked up because they were
not present in /usr/lib with the proper names, it seems. For example, I
had and error on -lexpat. I found this in /usr/lib
lrwxrwxrwx 1 root root 17 May 2 00:10 /usr/lib/libexpat.so.0 ->
libexpat.so.0.5.0
-rwxr-xr-x 1 root root 127592 Jun 16 2004 /usr/lib/libexpat.so.0.5.0
So I created an additional sym link
lrwxrwxrwx 1 root root 13 May 16 02:00 /usr/lib/libexpat.so ->
libexpat.so.0
and the problem went away. Then on to the next library with a similar
problem.
Is this a common problem? Why are my .so libraries getting installed
without all of the necessary name links?
Thanks all,
John
Hello all,
I am attemtping a compile of the vanilla xmame 0.92 source. I have a
Redhat Fedora Core 3 box. Unfortunately, I did a binary install of
redhat without much source. I don't have the redhat disks anymore so I
can't load source off them.
My compile has made it a long way, but I am hacking various things at
this point and beginning to feel like I am reaching beyond my skill
level. A little advice from some gurus would be great.
1) At first the compile couldn't find Xlib.h. So I went and got
XFree86 source rpm off the net and installed it. I installed
XFree86-4.3.0-55.src.rpm, untarred the source, adjusted the include
directive in the make file and attempted a build. This time it got
further, but then I got a bunch of syntax errors. It turns out that
some paths assumed in the #includes were not there. I fixed them up
with sym links inside the expanded XFree source tree and got it to
compile. Is this a typical experience? Or am I doing something the
hard way with regards to snagging source from the net? After installing
the source rpm I kind of expected the source to be expanded somewhere.
It wasn't. It was just sitting in a gzipped tar ball out in
/usr/src/redhat/SOURCES. So I manually untarred to a working dir along
side of my xmame source. Is this typical? I feel like I am missing
some step in the source file installation process.
2) When I installed the XFree86 source rpm it came with a slew of .patch
files. Uh, was I supposed to use these somehow? I didn't. I saw the
full source tar ball sitting there and went for that. My main question
here is: are those patch files supposed to be applied to that source in
the tar ball or is the bundled source already patch-applied?
3) Well, with the compile complete it is on to linking problems. I
found that some of my libs were not being picked up because they were
not present in /usr/lib with the proper names, it seems. For example, I
had and error on -lexpat. I found this in /usr/lib
lrwxrwxrwx 1 root root 17 May 2 00:10 /usr/lib/libexpat.so.0 ->
libexpat.so.0.5.0
-rwxr-xr-x 1 root root 127592 Jun 16 2004 /usr/lib/libexpat.so.0.5.0
So I created an additional sym link
lrwxrwxrwx 1 root root 13 May 16 02:00 /usr/lib/libexpat.so ->
libexpat.so.0
and the problem went away. Then on to the next library with a similar
problem.
Is this a common problem? Why are my .so libraries getting installed
without all of the necessary name links?
Thanks all,
John