% sudo /usr/libexec/locate.updatedb
I ran the above and then ran:
   % locate install | grep '/install$'
jamesk @ /Users/jamesk@HOME-->locate install | grep '/install$'
/Applications/MacOS_security/administration_tools/arusers/install
/Applications/MacOS_security/firmware_passwords/secureit1_05/install
/sw/lib/dpkg/methods/apt/install
/Users/jamesk/palm/install
/usr/bin/install
/usr/local/install
/Volumes/BACKUP/Applications_backup/MacOS_security/firmware_passwords/secureit1l
/Volumes/BACKUP/jamesk_home/Desktop/arusers/install
/Volumes/BACKUP/jamesk_home/palm/install
jamesk @ /Users/jamesk@HOME-->


On Monday, May 13, 2002, at 08:44  PM, Chris Devers wrote:

> On Mon, 13 May 2002, James Kelly wrote:
>
>> Setting up glib (1.2.10-3) ...
>> usage: install [-cps] [-f flags] [-m mode] [-o owner] [-g group] [-l
>> linkflags]2
>>         install [-cps] [-f flags] [-m mode] [-o owner] [-g group] [-l
>> linkflags]y
>>         install -pd [-m mode] [-o owner] [-g group] directory ...
>
> Have you added your own copy of the 'install' program? What do you get
> when you do a 'which' search? Here's what I get:
>
>   % which install
>   /sw/bin/install
>
> You can also do a 'locate' search, provided that the locate database is
> current (updating can take several minutes, if you need to do it):
>
>   % sudo /usr/libexec/locate.updatedb
>   % locate install | grep '/install$'
>
> The latter command could produce a lot of hits, but you should see only
> one (or if you have Fink's install program like I do), two hits:
>
>   /sw/bin/install
>   /usr/bin/install
>
> If you have anything else, such as /usr/local/bin/install, then chances
> are it is a version of the program incompatible with the Debian linux
> tools that Fink uses. The GNU-Darwin project provides BSD based tools 
> that
> are incompatible with the ones Fink relies on, so if you have a lot of
> software from them or another similar source, you'll need to move or
> remove the files it put in [normally] /usr/local.
>
> Once that is out of the way, running the 'fink install...' command 
> should
> have better luck. Note though that, if 'install' wasn't the only 
> modified
> file (i.e. if you have a /usr/local/bin/make) then you may have other 
> bugs
> which haven't manifested themselves yet. If you see any weird errors, it
> may be necessary to do a "fink rebuild..." on the packages you're trying
> to install.
>
> If this is all totally offtrack, let me know. This is the first error 
> like
> this I've noticed someone ask about on the Fink lists, but it seems to 
> fit
> the profile of the BSD bugs people have been having.
>
>
> --
> Chris Devers                                [EMAIL PROTECTED]
> Apache / mod_perl / http://homepage.mac.com/chdevers/resume/
>
> "More war soon. You know how it is."    -- mnftiu.cc
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
James M. Kelly
AIM: macubergeek
PGP public key: http://members.wap.org/james.kelly/pubkey
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Fink-beginners mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-beginners

Reply via email to