On 11/5/19 10:43 AM, Нина Диденко wrote:
> Hi.
>
>> Default AR arguments (clq) are added to KSH arguments (cr) resulting
> in (ar clq
>> cr)
>> And so build starts to fail when building ksh's libast:
>>
>> + ar clq cr libast.a state.o opendir.o readdir.o rewinddir.o seekdir.o
>> telldir.o getcwd.o fastfind.o hashalloc.o hashdump.o hashfree.o
> hashlast.o
>> hashlook.o hashscan.o hashsize.o hashwalk.o memhash.o memsum.o strhash.o
>> strsum.o mematoe.o m
>> emetoa.o chresc.o chrtoi.o streval.o strexpr.o strmatch.o strcopy.o
> modei.o
>> modex.o
>
>>
>
>>
>> ar: libast.a: No such file or directory
>>
>> In the past I had no such issue (CDE 2.2.4), but I have it now with
> latest
>> release.
>> Anyone knows how to track this issue?
>
> This happens when build environment sets AR variable.
> In case of NixOS, the build system sets AR=ar.
> A workaround is to do "unset AR" in the build script.
>
> Jon, I'm not sure. But should anything be done on the CDE side to prevent
> this from happing accidently?
I've not seen this error - but yes, it seems that perhaps AR should be
unset? What build env is setting this when building CDE?
--
Jon Trulson
"Nothing unreal exists."
-- Kiri-kin-tha
_______________________________________________
cdesktopenv-devel mailing list
cdesktopenv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
