Phil,
Hello all,
I'm finding that the polyml source RPM unpacks certain files but doesn't build. I have (RedHat) Fedora Core 1. The contents of my terminal is below. In short: poly wasn't installed initially and the rpm command put files in /usr/src/redhat/{SOURCES, SPECS} but didn't build anything. (rpm took about 0.5s) Does anyone have any ideas?
I don't really know, because I downloaded the source tarballs from the Poly/ML web site not the RPM, but my experience with Linux sources is that installing source RPMs does just put tarballs into the /usr/src/ directory and doesn't build anything - so the Poly/ML source RPM is uniform with that.\
Will building the source RPM still include XMotif support if that's installed on my machine?
Thanks, Phil.
[root@pclayton SRPMS]# rpm -qa | grep "poly"
[root@pclayton SRPMS]# rpm -ivh polyml-4.1.3Release-1.src.rpm warning: user dave does not exist - using root warning: user dave does not exist - using root warning: user dave does not exist - using root warning: user dave does not exist - using root 1:polyml ########################################### [100%]
[root@pclayton SRPMS]# ls /usr/src/redhat/SOURCES/ polyml-4.1.3.i386.tar.gz polyml-4.1.3.ppc.tar.gz polyml-driver-4.1.3.tar.gz
If you unpack it and go into the driver directory and follow the instructions it should be reasonably obvious at the configure stage whether or not it's found X Windows and Motif. However, you need to recompile the compiiler as well as the driver program I believe. The instructions in the FAQ on the web site worked fine for me.
[root@pclayton SRPMS]# ls /usr/src/redhat/SPECS/ polyml-4-1-3.spec
I don't know anything about this. What I'd be expecting to find is the ML code of the compiler in a tarball that unpacks into a directory called mlsource.
Hope that helps!
Rob.
Rob Arthan wrote:
I'm finding that the polyml source RPM unpacks certain files but doesn't build. I have (RedHat) Fedora Core 1. The contents of my terminal is below. In short: poly wasn't installed initially and the rpm command put files in /usr/src/redhat/{SOURCES, SPECS} but didn't build anything. (rpm took about 0.5s) Does anyone have any ideas?
I don't really know, because I downloaded the source tarballs from the Poly/ML web site not the RPM, but my experience with Linux sources is that installing source RPMs does just put tarballs into the /usr/src/ directory and doesn't build anything - so the Poly/ML source RPM is uniform with that.\
Looking at the commands in the spec file put in /usr/src/redhat/SPECS, I would expect this RPM to build and install when I run the rpm command. The source tarballs are put in /usr/src/redhat/SOURCES ready for building. The spec file is like a recipe for building --- a description is at http://www.rpm.org/RPM-HOWTO/build.html It is my understanding that source RPMs are intended to hide the build process from the user too.
I've managed to build it manually as Rob describes, which works fine. However, I prefer RPMs because its easier to keep track of what's on my machine/set up new machines.
I am using rpm-4.2.1-0.30. Also uname -m returns i686 --- could both %ifarch guards in the spec file be false?
If anyone can point out why this source RPM won't build, that would be greatly appreciated! Thanks, Phil
[root@pclayton SRPMS]# rpm -qa | grep "poly"
[root@pclayton SRPMS]# rpm -ivh polyml-4.1.3Release-1.src.rpm warning: user dave does not exist - using root warning: user dave does not exist - using root warning: user dave does not exist - using root warning: user dave does not exist - using root 1:polyml ########################################### [100%]
[root@pclayton SRPMS]# ls /usr/src/redhat/SOURCES/ polyml-4.1.3.i386.tar.gz polyml-4.1.3.ppc.tar.gz polyml-driver-4.1.3.tar.gz
If you unpack it and go into the driver directory and follow the instructions it should be reasonably obvious at the configure stage whether or not it's found X Windows and Motif. However, you need to recompile the compiiler as well as the driver program I believe. The instructions in the FAQ on the web site worked fine for me.
[root@pclayton SRPMS]# ls /usr/src/redhat/SPECS/ polyml-4-1-3.spec
I don't know anything about this. What I'd be expecting to find is the ML code of the compiler in a tarball that unpacks into a directory called mlsource.