On Fri, 18 Aug 2000 [EMAIL PROTECTED] wrote:
>> Checking the actual build, "configure" ends off saying:
>>
>> Pike binary used: /usr/pike/7.0.71/bin/pike
>> Pike version: 7.0.71
>> Pike include dir: -I/usr/pike/7.0.71/include/pike
>>
>> The above pike binary is the correct one, and there is a symlink
>> in /usr/bin/pike pointing to this binary. However, the package
>> refuses to install claiming the /usr/local/bin/pike dependancy.
>
>First you can install with --nodeps but this is a hack. Fundamental
>problem is that somewhere there is a script with
>#!/usr/local/bin/pike. It is probably hardcoded so this is not fixed
>by the building process. In that case you will have to create a patch
>for the script.
After sending the message I went on a hunt with rgrep and I did
in fact find 6 scripts hard-coded and fixed them. Fortunately, I
didn't write them so I'm not to blame. ;o)
I made a patch to fix the problem.
Now I'm having another problem though.
I have:
package.tgz and "filename.init" in SOURCES.
I want filename.init added to the package as well when it is
built. I've tried various combinations of:
Source: package.tgz
Source1: filename.init
%setup
%setup -D 1
etc.. all to no avail. I'm not that familiar with setup's
options, and I've tried the various examples in maximum RPM under
the %setup description and can't seem to get it to work.
How do I force RPM to include this file? I'm assuming all it
does is copy it into the build directory where the sources were
untarred. That is fine.
Any ideas?
--
Mike A. Harris Linux advocate
Computer Consultant GNU advocate
Capslock Consulting Open Source advocate
Try out Red Hat Linux today: http://www.redhat.com
ftp://ftp.redhat.com/pub/redhat/redhat-6.2/
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
