Re: [SEToolkit-developer] Miscellaneous notes

[Tankersley, J. <jon...@ed...>]

=20

>-----Original Message-----
>From: Dagobert Michelsen [mailto:da...@ba...]=20
>Sent: Wednesday, January 09, 2008 3:07 AM
>To: set...@li...; Tankersley,=20
>Jon; Alex Kiernan
>Subject: Re: Miscellaneous notes
>
>Hi Jon,
>
>Von "Tankersley, Jon" <jon...@ed...> (Tue, 8 Jan=20
>2008 16:12:27 -0600):
>> I had to 'rebuild' a package so that I could hand it off to someone=20
>> who doesn't want to understand anything.....
>>=20
>> I didn't start with the full SVN pkg yet, but I did notice some=20
>> changes to the old package that need to be made, and that would have=20
>> to be check with the new packaging scheme.
>> Or we COULD just build a separate package for Orca that has a=20
>> dependency on the SEToolkit package.
>
>That is my intention. The plan is to have two packages for SE=20
>Toolkit, one with the old directory scheme and one new package=20
>in Blastwave style. The include files all go into SE Toolkit.=20
>The Orca software is packaged in two parts, the collector and=20
>the web presentation package.
>
>If you want to take a look the repository is open at
>  http://svn.blastwave.org/trac/browser/csw/trunk/utils/setoolkit
>  http://svn.blastwave.org/trac/browser/csw/trunk/utils/orca

That was my starting point, but I didn't have time to guess as to the
intent.... I can now go back and try building a package the 'right' way.

>
>> Binaries move to libexec
>> Bin/se script has that change included
>>=20
>> To INCLUDE Orca we should somehow include the Orca and Adrian's=20
>> extensions.
>> Here's what I did to hack the new stuff into the old package.
>>=20
>> Trunk/se/adrian copied to /opt/RICHPse/adrian=20
>Trunk/orca/lib/SE copied=20
>> to /opt/RICHPse/lib along with symlinks to have 3.4.x per=20
>the version=20
>> information.
>> Orcallator startup scripts modified to have=20
>> -I/opt/RICHPse/adrian/include and -I/opt/RICHPse/lib/SE/3.4.x=20
>> Orcallator/orcallator.se.490 - svn version 490 of the orcallator=20
>> script included - orcallator.se is symlinked to this file.
>> Various binaries appropriately installed in the libexec directory.
>>=20
>> This is enough to get the orcallator script to launch properly.
>>=20
>> Any thoughts?
>
>You should rebuild the software with autoconf and prefix set=20
>and let 'make install' install the software in the proper locations.
>Everything should work with this, otherwise it is a bug that=20
>needs to be fixed.
>

Hmm... Regarding this one...
I was trying to build on a Solaris 10 x86....
Automake/autoconf/autoreconf/etc. all were non-cooperative.
Automake --add-missing got me most of the way but it was complaining
about Makefile.in and ltmain.sh.
Finally, after many different tries, I got it to build Makefile.in.  The
ONLY solution I could come up with for ltmain.sh was to copy from my
Solaris 10 SPARC build.  Then everything built and at first blush
appears to be okay.  I've not fully tested it yet.  We need yet another
test suite for JUST the SVN trunk.