I built the setoolkit using a fresh pull from the SVN repository and
ran into this issue. I'm compiling with SUN Studio 10 with a configure
command of:
$ CC=cc CFLAGS="-xarch=v9" LDFLAGS="-xarch=v9" ./configure
--prefix=/gfs/home/jcraig/apps/se
I then did a "make install" and the se binary was placed in the
libexec directory, not the directory libexec/{ARCH}. When I call se
it assumes the se binary is in libexec/{ARCH} and reports unsupported
platform. My question is should we fix this in the bin/se wrapper
script or the "make install" process? Thoughts?
1) in bin/se add a test for libexec/{ARCH}/se, on failure try
libexec/se, then allow fall through to Unsupported platform
2) Have install determine what architecture was built and put the
binary in the appropriate libexec/{ARCH}/se directory.
3) ??? Ideas ???
The first is rather simple but effective. The second is probably the
most "correct" way of doing it, but I'm not a build expert and would
have to muddle through it. Maybe we could take approach 1 until
someone has time to look at approach 2.
We also need to add "python/docutils" to the dependency list for
building from source as its required for the HTML document conversion
step.
--
Jonathan Craig
|
