Submitted by Anonymous on Tue, 07/23/2002 - 16:44. General Questions
I started out with the src rpm openmotif-2.1.30-2_ICS.src.rpm and ran in several
dead ends. Using gcc it complained about
gcc cannot specify -o with -c or -S and multiple compilations
(This problem was posted to this list already, but I could not find the answer).
I have on the system also ccc (Compaq cc) That worked slightly longer until in a Makefile gcc turned up and DefaultGcc2AxpOpt was nowhere to be found.
(It is around in linux.cf).
At that point I decided to go to the real source ics.com and downloaded the
openMotif-2.2.2.tar.gz
untared and went to work using
CC=cc CFLAGS=-O ./configure
make
(humming nicely along, I thought I`m in business) until O got stuck with
/bin/sh ../../libtool --mode=link cc -O -version-info 310 -o libMrm.la -rpath /usr/X11R6/lib MrmIbuffer.lo MrmIentry.lo MrmIfile.lo MrmIheader.lo MrmIindex.lo MrmIindexw.lo MrmIrid.lo MrmIswap.lo MrmItop.lo MrmItopw.lo Mrmappl.lo Mrmcontext.lo Mrmerror.lo Mrmhier.lo Mrmicon.lo Mrminit.lo Mrmlread.lo Mrmlwrite.lo Mrmmodule.lo Mrmos.lo Mrmptrlist.lo Mrmtable.lo Mrmtime.lo Mrmvm.lo Mrmwci.lo Mrmwcrw.lo Mrmwcrwr.lo Mrmwread.lo Mrmwrefs.lo Mrmwvalues.lo Mrmwwrite.lo MrmMessages.lo ../Xm/libXm.la -L/usr/X11R6/lib -lXt -lSM -lICE -lX11
rm -fr .libs/libMrm.la .libs/libMrm.* .libs/libMrm.*
cc -shared MrmIbuffer.o MrmIentry.o MrmIfile.o MrmIheader.o MrmIindex.o MrmIindexw.o MrmIrid.o MrmIswap.o MrmItop.o MrmItopw.o Mrmappl.o Mrmcontext.o Mrmerror.o Mrmhier.o Mrmicon.o Mrminit.o Mrmlread.o Mrmlwrite.o Mrmmodule.o Mrmos.o Mrmptrlist.o Mrmtable.o Mrmtime.o Mrmvm.o Mrmwci.o Mrmwcrw.o Mrmwcrwr.o Mrmwread.o Mrmwrefs.o Mrmwvalues.o Mrmwwrite.o MrmMessages.o --rpath /home/kum/openMotif-2.2.2/lib/Xm/.libs --rpath /usr/X11R6/lib -L/usr/X11R6/lib ../Xm/.libs/libXm.so -lXt -lSM -lICE -lX11 -lc -soname libMrm.so.3 -o .libs/libMrm.so.3.0.1
/home/kum/openMotif-2.2.2/lib/Xm/.libs file not recognized Is a directory
collect2 ld returned 1 exit status
Now, that directory exists and all the libs for Xm are there.
Something similar should have worked for making the Xm libs, but that scrolled of the
screen.
Appreciate any ideas.
Gerfried
dont know about this one, but do you have the latest libtools?
jim
That looks like your pretty close. I`m assuming some .c files compiled succefully by your drawl.
You probably did see in the readme that Imake (ugh) is still stable way to compile and that "./configure" isn`t absolutely finished in the writing yet.
Ha ha ha?? You know what? I bet its just file perms. You compiling in your home directory maybe?
Oh yes,
You know - I think "./configure" uses its own version of libtool so libtool is likely ok.
Be sure and check your "configure.log" for any hints. Your on "alpha/compaq" is that right? That isn`t necessarily osf or linux or sun - but one of them might be "closer".
You are using "bash" or a good "sh" right? "./config" will certainly not do its magic logic right if using a less than par shell.
That line was building
openMotif-2.2.?/lib/Mrm/.libs/libMrm.so...
which will end up in /usr/X11R6/lib after a "make install".
The message says simply what it means Xm/.libs is not a file. And its right. That means that either the make script or the system is wrong (your not compiling on an NFS drive, right?).
You said you didn`t get to see the message. You can get the message and watch like this
# make 2>&1 >> make.log
# tail -f make.log
So - that should fix your lost log problem anyway. You can Ctrl-C to stop and then restart the tail at any time.
If your still having problems, try that and post the make.log in the forum.
I see
--rpath /home/kum/openMotif-2.2.2/lib/Xm/.libs
--rpath /usr/X11R6/lib
I might be wrong, but I think aclocal.m4 is including rpath twice for your platform that ./configure (did or did not) detect.
Take a look in "lib/Mrm/Makefile" and search for "rpath". (Ignore the Xm directory the libs are already created).
Anyway - don`t forget to think out of the box. Untar the thing again insuring you preserve file permissions within. Try running config as root just so you know configure didn`t fail to access a file.
Try choosing a different architecture (like linux) before trying to hack the code.
Maybe try following the direction for an Imake build. You might find that easier - you never know.
Post your "configure.log" and your "make.log" if you can`t get it to work again,
Hope that help,
John