About Karl_BAG

Karl_BAG · ‎10-13-2011

We had to dig quite deep in the system this morning and finally got the bug caused by copying 15 year old config files / scripts into the new system. It turned to be an "alias", not shown if calling "$ alias" - and we guess it is because the "alias definition" of make is defined in a function in a script setting up the shell environment: make() { if [ -f "env.x" ] then . env.x fi /usr/bin/make -f makefile.mk ${*:-} } # make Thanks a lot for your help Karl

Karl_BAG · ‎10-12-2011

If I use "/usr/bin/make" no warning message is printed. I also tried to find a make-function, or some alias but couldn't find anything. But there must be some kind of configuration file where I can change/set some default options because I additional tried some different cases, where I get even more curios results: $ whereis make make: /usr/bin/make /usr/ccs/bin/make /usr/share/man/man1.Z/make.1 $ $ which make /bin/make $ $ ll /bin/make lr-xr-xr-x 1 bin bin 17 Jan 24 2011 /bin/make -> /usr/ccs/bin/make $ $ ll /usr/bin/make lr-xr-xr-x 1 bin bin 17 Jan 24 2011 /usr/bin/make -> /usr/ccs/bin/make $ $ ll /usr/ccs/bin/make -r-xr-xr-x 1 bin bin 303268 Feb 15 2007 /usr/ccs/bin/make --------------------------------------------------------------------- $ ll total 16 drwxr-xr-x 2 lka users 96 Oct 12 15:16 . drwxr-xr-x 5 lka users 96 Oct 12 15:14 .. -rwxr-xr-x 1 lka users 95 Oct 12 15:24 makefile.mk $ $ make optmake1 makefile.mk: Option - make1 $ $ /usr/bin/make optmake1 Make: Don't know how to make optmake1. Stop. $ $ make -f makefile.mk optmake1 Too many command lines for `optmake1' makefile.mk: Option - make1 $ $ /usr/bin/make -f makefile.mk optmake1 makefile.mk: Option - make1 $ --------------------------------------------------------------------- $ ll total 16 drwxr-xr-x 2 lka users 96 Oct 12 15:29 . drwxr-xr-x 5 lka users 96 Oct 12 15:14 .. -rwxr-xr-x 1 lka users 83 Oct 12 15:29 xyz.mk $ $ make optxyz1 Make: Cannot open makefile.mk. Stop. $ $ /usr/bin/make optxyz1 Make: Don't know how to make optxyz1. Stop. $ $ make -f xyz.mk optxyz1 Make: Cannot open makefile.mk. Stop. $ $ /usr/bin/make -f xyz.mk optxyz1 xyz.mk: Option - xyz1 $ --------------------------------------------------------------------- $ ll total 32 drwxr-xr-x 2 lka users 96 Oct 12 15:16 . drwxr-xr-x 5 lka users 96 Oct 12 15:14 .. -rwxr-xr-x 1 lka users 95 Oct 12 15:36 makefile.mk -rwxr-xr-x 1 lka users 83 Oct 12 15:36 xyz.mk $ $ make optmake1 makefile.mk: Option - make1 $ $ make optxyz1 Make: Don't know how to make optxyz1. Stop. $ $ make -f makefile.mk optmake1 Too many command lines for `optmake1' makefile.mk: Option - make1 $ $ make -f xyz.mk optxyz1 xyz.mk: Option - xyz1 $ $ make -f xyz.mk optmake1 makefile.mk: Option - make1 $ $ /usr/bin/make -f xyz.mk optxyz1 xyz.mk: Option - xyz1 $ $ /usr/bin/make -f xyz.mk optmake1 Make: Don't know how to make optmake1. Stop. $ --------------------------------------------------------------------- $ cat makefile.mk optmake1: @echo "makefile.mk: Option - make1" optmake2: @echo "makefile.mk: Option - make2" $ $ $ cat xyz.mk optxyz1: @echo "xyz.mk: Option - xyz1" optxyz2: @echo "xyz.mk: Option - xyz2" $

Karl_BAG · ‎10-12-2011

"It appears you have your own version of make?" -> I'll check this with the guy who set up the system. And then I also gonna try "gmake" to check if there will be any problems with this. for $whence -v make i get make is a funcion

Karl_BAG · ‎10-11-2011

Neu-hpws1001(lka):VRZ=v3-28-0a_lka$ whence make make Neu-hpws1001(lka):VRZ=v3-28-0a_lka$

Karl_BAG · ‎10-11-2011

I use "make -f makefile.mk option1", which leads to the following: Neu-hpws1001(lka):VRZ=v3-28-0a_lka$ make -f makefile.mk option1 Too many command lines for `option1' hello Neu-hpws1001(lka):VRZ=v3-28-0a_lka$ Neu-hpws1001(lka):VRZ=v3-28-0a_lka$ uname -a HP-UX hpws1001 B.11.31 U ia64 3480881845 unlimited-user license

Karl_BAG · ‎10-11-2011

We are porting from PA-RISC -> Itanium / HPUX11.11 -> HPUX11.31. When running our makefiles I get the message "Too many command lines for 'Target'. Compilation works fine (make -f makefile.mk binname.exe / clear / clean) but I'd really like to get rid of this warnings. My guess is, that it only occurs if the makefile executes some shell command lines (either to link *.h / *.c files to the working directory or to clean up the working directory after compiling -> see attached file). To be sure the problem is independent from the existing makefiles I also wrote a very short test makefile, where I still get the warning. Is there some syntax error and if, how can I fix it? (I don't get the message by using option1:: instead of option1: but then hello is printed twice). Thanks Karl test makefile: (make -f makefile.mk option1/option2) option1: @echo "hello" option2: @echo "how are you"

Karl_BAG · ‎09-14-2011

Hej Dennis Thanks for your help. In this case i'll just fix the affected lines. Karl

Karl_BAG · ‎09-14-2011

We are porting from PA-RISC -> Itanium / HPUX11.11 -> HPUX11.31. During the compilation of dvav.c I get a couple of warnings #3665, which I don't know how to solve: "dvav.c", line 986: warning #3665-D: concatenation with "TimeRef" in macro "INSTALL_AV" does not create a valid token INSTALL_AV (TimeRef); ^ If I substitute "&av.##x" with "&av.TimeRef" no warnings are reported, so I guess there is some problem with the precompiler. ---------------------------------------------------------------------------------------------------------------------- cc +Olit=const -Aa -c +e +O3 -z +w2 +DD32 -D _XOPEN_SOURCE_EXTENDED -D _HPUX_SOURCE -D HOST_WKS -D ENV_HPUX -D VERSION='"akt"' -I/usr1/xfm/v3.3/include -I/usr/include/Motif2.1 -I/usr/include/X11 -I/usr/include/X11R6 -D NeedFunctionPrototypes=1 -c dvav.c ---------------------------------------------------------------------------------------------------------------------- #define STR_LEN 30 .... .... #define INSTALL_AV(x) \ \ FmAttachAv (#x, &av.##x); \ .... .... { /* Visualisierungsfenster */ /* ---------------------- */ char TimeRef [STR_LEN]; char TimeStamp [STR_LEN]; char VisStatus [STR_LEN]; char VisStatusColor [STR_LEN]; char AnzStatus [STR_LEN]; char AnzStatusColor [STR_LEN]; char TrigStatus [STR_LEN]; char TrigStatusColor [STR_LEN]; char ErrorStatus [STR_LEN]; char ErrorStatusColor [STR_LEN]; char CfgName [STR_LEN]; char CfgNameColor [STR_LEN]; char CfgVersion [STR_LEN]; char CfgVersionColor [STR_LEN]; char SnapFile [STR_LEN]; char SnapFileColor [STR_LEN]; char EnvColor [STR_LEN]; } av; .... .... INSTALL_AV (TimeRef); Thanks Karl

Re: Too many command lines for 'Target'

Re: Too many command lines for 'Target'

Re: Too many command lines for 'Target'

Re: Too many command lines for 'Target'

Re: Too many command lines for 'Target'

Too many command lines for 'Target'

Re: Warning #3665-D: concatenation with "xy" in ma...

Warning #3665-D: concatenation with "xy" in macro ...