If possible, I think they should go in the same place as the RPM installation, but I am not anal about it :-)
It would be nice if you could somehow tell the difference between a 32 and 64 bit install and use the correct library subdir. To get that to happen I had to pass some options to the make command to specify the libdir. That's actually pretty easy in an rpm as all that info is available to the rpm build environment through the preprocessing that happens prior to the rpmbuild command actually processing the spec file. So I was able to code what I needed all in the spec file. You may have more work to do but you should take a look at the spec file to see what I had to pass to make. Note that there are two invocations of make in the spec file. In order to avoid having to execute ldconfig at all you should make sure that you perform the build with the correct libdir. This may mean that you actually will need a two targets in the Makefile - one to determine the environment and call the second target with the proper make options. The second target performs the actual build and packaging. The above is just a suggestion. In any case I can help you as you need it. David Ashley On 10/19/2010 03:21 PM, Mark Miesfeld wrote: > On Tue, Oct 19, 2010 at 1:13 PM, David Ashley > <[email protected]> wrote: >> On looking back at my changes I see I did make a change that could impact >> the >> debian build. The following was changed: >> >> AC_PREFIX_DEFAULT(/usr) > Yes, that is the change that effected the debian build. What the deb > target does is build the interpreter as normal and then do an install > into a subdirectory of the build directory. Once that is done it > simply packages that subdirectory up into the .deb installation > package. > > But, that's okay. I think the installed files on a debian system > should be the same as we are doing on Fedora, SuSE, etc.. Don't you? > > I'll get that fixed up. > > But the basic question is, should the installed files go in the same > place, /usr/lib/ooRexx etc.? > > -- > Mark Miesfeld > > ------------------------------------------------------------------------------ > Download new Adobe(R) Flash(R) Builder(TM) 4 > The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly > Flex(R) Builder(TM)) enable the development of rich applications that run > across multiple browsers and platforms. Download your free trials today! > http://p.sf.net/sfu/adobe-dev2dev > _______________________________________________ > Oorexx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > ------------------------------------------------------------------------------ Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
