Actually, I can see several things in ksh93/ setting these options:
$ git grep -w cr .
src/cmd/ksh93/Mamfile:setv ARFLAGS cr
src/cmd/ksh93/Mamfile:exec - ${AR} cr libshell.a alarm.o cd_pwd.o
cflow.o deparse.o getopts.o hist.o misc.o print.o read.o sleep.o trap.o
test.o typeset.o ulimit.o umask.o whence.o arith.o args.o array.o
completion.o dlopen.o defs.o edit.o expand.o fault.o fcin.o history.o
init.o io.o jobs.o
src/cmd/ksh93/Mamfile:exec - ${AR} cr libshell.a lex.o macro.o name.o
parse.o path.o string.o streval.o subshell.o tdump.o timers.o trestore.o
userinit.o waitevent.o xec.o limits.o msg.o strdata.o testops.o
keywords.o options.o signals.o aliases.o builtins.o variables.o
lexstates.o emacs.o vi.o
src/cmd/ksh93/OPTIONS:CRNL=0 # accept <cr><nl> for <nl>
src/cmd/ksh93/README: CRNL off <cr><nl> treated as <nl> in shell
grammar.
src/cmd/ksh93/edit/vi.c: * This routine returns when cr, nl, or
(eof in column 0) is
src/cmd/ksh93/ksh.mk:ARFLAGS=cr
src/cmd/ksh93/ksh.mk: ${AR} cr libshell.a alarm.o cd_pwd.o cflow.o
getopts.o hist.o misc.o \
src/cmd/ksh93/ksh.mk: ${AR} cr libshell.a macro.o name.o parse.o
path.o string.o streval.o \
src/cmd/pax/Mamfile:setv ARFLAGS cr
src/lib/lib0ast/Mamfile:setv ARFLAGS cr
src/lib/libAST/Mamfile:setv ARFLAGS cr
src/lib/libast/Mamfile:setv ARFLAGS cr
src/lib/libast/Mamfile:exec - ${AR} cr libast.a state.o opendir.o readdir.o
...
I am not sure whay this is causing a problem for your OS, unless ${AR}
is defined on your system to already include the ar options in addition
to the ar command, and then ARFLAGS is just adding to the issue. As I
said, on linux/*bsd, this issue doesn't show up. Maybe the above gives
you a clue as to where to look.
-jon
On 1/14/19 11:29 AM, Jon Trulson wrote:
> On 1/14/19 11:18 AM, Alex Ivanov wrote:
>> It is NixOS Linux distro. Non FHS compliant. Its strange that I had no such
>> issue with 2.2.4 release, but have it with current release
>> Any things I should check at first?
>>
>
> Not sure what would have changed that behavior - I assume by "current
> release" you mean git master?
>
> These options (and the command itself) are set in imake via the config
> files in config/cf/
>
> With some grepping around, I see:
>
> cray.cf:#define ArCmd bld cr
>
> It's the only place I see 'ar' and 'cr' in the same file.
>
> Imake.tmpl defines the ArCmd as:
>
> Imake.tmpl:#define ArCmd ArCmdBase clq
>
> So I think something in there somewhere (config/cf) might be doing the
> wrong thing on your OS for some odd reason.
>
> See how ArCmd, ArCmdBase and other related Ar commands are being put
> together in config/cf would be my suggestion.
>
> Of course, there might also just be something weird with ksh and it's
> 'detection' of your OS. This is another one of those painful modules in
> CDE.
>
> -jon
>
>
>> 14.01.2019, 21:13, "Jon Trulson" <[email protected]>:
>>> On 1/13/19 10:12 AM, Alex Ivanov wrote:
>>>> 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?
>>>
>>> I don't see this on linux of freebsd... What OS are you trying to build
>>> for. Seems an odd problem...
>>>
>>> --
>>> Jon Trulson
>>>
>>> "The Party told you to reject the evidence of your eyes and ears.
>>> It was their final, most essential command."
>>>
>>> -- 1984
>>>
>>> _______________________________________________
>>> cdesktopenv-devel mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
>
--
Jon Trulson
"The Party told you to reject the evidence of your eyes and ears.
It was their final, most essential command."
-- 1984
_______________________________________________
cdesktopenv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
