Strange behaviour of "make"

Strange behaviour of "make"

Post by Florence Henr » Thu, 27 Sep 2001 03:50:48



Hello,

I run under a Digital (OSF1 mesiow.obspm.fr V4.0 878 alpha) and the
command make has a strange behaviour:
I am using a Makefile.exp and it works perfectly well with

$ make -f Makefile.exp all

but when I rename my (experimental) "Makefile.exp" in "Makefile", is
does not work anymore and

$ make all

produces :

 syntax error The source line is 1.
 The error context is
                { FS = "\{" } /input/ { gsub("\}","",) >>>   <<<
 awk: The statement cannot be correctly parsed.
 The source line is 1.
*** Exit 2
Stop.
*** Exit 1
Stop.
*** Exit 1
Stop.

Any help ???
Thanks

Florence HENRY

ps : Here is my Makefile

.SUFFIXES: .ps .dvi .tex
.MAIN: article

${.TARGET

Quote:}.tex `


Quote:}' $${P

ARTIES}`
ECHO= echo ---\>

##### Pour l'article en mode 2 colonnes
article :


article.dvi : ${PARTIES}
article.ps : ${FIGURES}

##### Pour l'article en mode 1 colonne
article1 :


article_1.dvi : $${PARTIES}
article_1.ps : $${FIGURES}

##### Regles generiques
.tex.dvi:



      $(ECHO) "latex $*.tex " ; \
     *$*.tex > tmp ; \
   done



.dvi.ps:


all :



clean :

 
 
 

Strange behaviour of "make"

Post by Kenneth Brod » Thu, 27 Sep 2001 12:09:19



> Hello,

> I run under a Digital (OSF1 mesiow.obspm.fr V4.0 878 alpha) and the
> command make has a strange behaviour:
> I am using a Makefile.exp and it works perfectly well with

> $ make -f Makefile.exp all

> but when I rename my (experimental) "Makefile.exp" in "Makefile", is
> does not work anymore and

> $ make all

> produces :

[...]

Check to make sure that you don't have a file named "makefile" (note the
lower-case "m").  According to my "make" documentation, "makefile" is
looked for before "Makefile":

    If no -f option is present, then the files makefile, Makefile,
    and the Source Code Control System (SCCS) files s.makefile, and
    s.Makefile are tried in order.

--

+---------+----------------------------------+-----------------------------+

|    J.   |                                  |  herein are not necessarily |
|  Brody  | http://www.bestweb.net/~kenbrody |  those of fP Technologies." |
+---------+----------------------------------+-----------------------------+
GCS (ver 3.12) d- s+++: a C++$(+++) ULAVHSC^++++$ P+>+++ L+(++) E-(---)

    DI+(++++) D---() G e* h---- r+++ y?

 
 
 

Strange behaviour of "make"

Post by Florence HEN » Thu, 27 Sep 2001 20:46:49



Quote:> Check to make sure that you don't have a file named "makefile" (note the
> lower-case "m").  According to my "make" documentation, "makefile" is
> looked for before "Makefile":

>     If no -f option is present, then the files makefile, Makefile,
>     and the Source Code Control System (SCCS) files s.makefile, and
>     s.Makefile are tried in order.

I have no makefile in my directory.

But I have made some few tests with a Makefile slightly different. It
works when it is called Makefile but not when it is called
Makefile.old or foo

$ make -f foo all

gives :

Make: Don't know how to make article.  Stop.
*** Exit 1
Stop.

Here is the Makefile :

.SUFFIXES: .ps .dvi .tex
.MAIN: article

ECHO= echo ---\>
PARTIES= intro.tex obs.tex model.tex jets.tex rad.tex ccl.tex bib.tex

$$3 }' ${PARTIES}`

##### Pour l'article en mode 2 colonnes
article :


article.dvi : ${PARTIES}
article.ps : $${FIGURES}

##### Pour l'article en mode 1 colonne
article1 :


article_1.dvi : ${PARTIES}
article_1.ps : $${FIGURES}

##### Regles generiques
.tex.dvi:



      $(ECHO) "latex $*.tex " ; \
     *$*.tex > tmp ; \
   done



.dvi.ps:


compress :
   mv article.ps art.ps ;
   psnup -pa4 -2 art.ps article.ps ;

all :


clean :

deepclean :

tps :
   touch figures/*.eps ;

tex :
   touch *.tex ;

----
Florence HENRY

 
 
 

1. strange behavior from "gdb" and "ObjectCenter"

I've recently noticed an odd problem that I can repeat with both
ObjectCenter and gdb, on Solaris 2.3.

My simple test case looks like this:

int main(int argc, char *argv[])
{
    printf("1.\n");
    getchar();
    printf("2.\n");

If I compile and link this, load it into either gdb or objectcenter,
run it, wait for the first "printf" to finish, and then press ^C to
get back to the debugging prompt, I then enter:

    printf("3.\n")

and press return (in "gdb", I need "call" before the printf"), I
should see the function execute and print "3".  However, what happens
is exactly nothing.  The cursor goes to the left margin and nothing
happens.  I waited quite a while and then thought to press Return.  It
then executed the printf.  I then tried changing the "getchar" to a
call to "sleep(30)".  Instead of having to press Return, I just waited
about 20 seconds more and then it executed the printf.

I also found that if I set a breakpoint at "printf" and called the
function from the prompt, it would hit the breakpoint before going
into idle mode.  When I continued from the breakpoint, it then went
into idle mode.

In addition, I tried setting breakpoints in the application and
waiting until the debugger hit the breakpoint.  At that point, I would
try calling the printf from the prompt, and that worked fine.

I have not upgraded my versions of "gdb" (4.14) or "objectcenter"
(2.1).  I don't remember when I last saw this scenario work correctly
(I've used this scenario for real work many times in the past).  It's
possible I've updated the jumbo patch on my workstation since then,
but I also repeated this on another workstation with an older jumbo
patch.  It is possible that this stopped working about the time we
moved to using ClearCase, however my test case isn't in a MVFS
filesystem, so it doesn't seem like it would matter.

2. ISA NIC

3. : Weird ">" redirect behavior vs. ">>" redirect behavior

4. How to automate ftp from Windows NT directory to UNIX directory

5. GETSERVBYNAME()????????????????????"""""""""""""

6. locate, find and book suggestions...

7. """"""""My SoundBlast 16 pnp isn't up yet""""""""""""

8. Problems printing - EVEN USING THE "HOW TO" ???

9. Strange "w", "who" and "uptime" output

10. Type "(", ")" and "{", "}" in X...

11. terminal behavior after "man", "less", etc.

12. Incorrect key "translation" behavior for "xterm"

13. I need help with "while" Vs "for" bizarre behavior