Mail Archives: geda-help/2020/01/20/12:42:02
Glen,
Hmmm, OK. Good for Fedora. I’ve always resorted to “find” but like you said, its kicks
out a lot of cruff that isn’t helpful.
Thanks for the tip on updatedb.
Roger
> On Jan 20, 2020, at 4:27 AM, Glen W. Ruch (gw DOT ruch AT yahoo DOT com) [via geda-help AT delorie DOT com] <geda-help AT delorie DOT com> wrote:
>
> Roger:
>
> 'locate' is a Fedora-ism similar to 'find / -name <filename> -print'
>
> It's advantage is that it searches an existing database for the file.
>
> The disadvantage is that the user must periodically run the 'updatedb' command as a superuser to refresh the database.
>
> Another advantage over 'find' is the user isn't given a huge number of 'Permission denied' when searching areas outside his permissions.
>
> Regards.
>
> On 1/19/20 7:11 PM, Roger Traylor (traylor AT engr DOT orst DOT edu) [via geda-help AT delorie DOT com] wrote:
>> Karl,
>>
>> Thank you so much. One thing you mentioned was to use locate. I’ve been around
>> a lot of Linux systems but never heard of it. On my busted 18.04 machine, I was
>> able to remove every file related to the 2.2 release of guile. Once a fresh install
>> of geda was tried, it installed without error first time.
>>
>> I do get a slew of error messages that I will run pass you if I cannot figure them out.
>>
>> On my laptop, I removed the virtual machine and reinstalled ubuntu 19.04. Installed
>> the usual suspects and then a fresh install of geda-gaf ran perfectly. It invokes all the
>> tools with no errors at all.
>>
>> I truly appreciate the help you have given me. One machine down, one to go.
>>
>> Roger Traylor
>>
>>> On Jan 12, 2020, at 10:21 PM, karl AT aspodata DOT se wrote:
>>>
>>> Roger:
>>> ...
>>>> However, I the following directories do not exist:
>>>> /usr/local/guile_2.0.14/include/guile/2.0
>>>> /usr/local/guile_2.0.14/lib
>>> ...
>>>>> If you have guile installed somewhere, you can tell configure et.al. to
>>>>> use it by doing e.g.:
>>>>>
>>>>> export GUILE_CFLAGS="-I/usr/local/guile_2.0.14/include/guile/2.0 -pthread"
>>>>> export GUILE_LIBS="-L/usr/local/guile_2.0.14/lib -lguile-2.0 -latomic_ops -lgc"
>>>>> export GUILE=/usr/local/guile_2.0.14/bin/guile
>>>>> export GUILE_SNARF=/usr/local/guile_2.0.14/bin/guile-snarf
>>> Please do note that my example was guile compiled from git source and
>>> with ./configure --prefix=/usr/local/guile_2.0.14, which is fairly
>>> nonstandard, soo my example was perhaps non helping.
>>>
>>> What one is looking for is directories with theese files (exact version
>>> numbers might differ):
>>>
>>> $ ls -1F /usr/local/guile_2.0.14/include/guile/2.0/
>>> libguile/
>>> libguile.h
>>> readline.h
>>> $ ls -1F /usr/local/guile_2.0.14/lib/
>>> guile/
>>> libguile-2.0.a
>>> libguile-2.0.la*
>>> libguile-2.0.so@
>>> libguile-2.0.so.22@
>>> libguile-2.0.so.22.8.1*
>>> libguile-2.0.so.22.8.1-gdb.scm
>>> libguilereadline-v-18.a
>>> libguilereadline-v-18.la*
>>> libguilereadline-v-18.so@
>>> libguilereadline-v-18.so.18@
>>> libguilereadline-v-18.so.18.0.0*
>>> pkgconfig/
>>>
>>> Use locate to find e.g. libguile-2.0.so.
>>>
>>> ///
>>>
>>> On a second note, I'm having problems getting latest gschem working
>>> correctly, and is currently using lepton-schematic and
>>> old gschem (v1.9.2).
>>>
>>> So unless you want to hunt down bugs, I suggest you do the same.
>>>
>>> Regards,
>>> /Karl Hammar
>>>
>>
- Raw text -