public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Ajit George" <gajit@kurianinc.com>
To: <cygwin@sourceware.cygnus.com>
Subject: RE: compilation problem
Date: Sun, 31 Oct 1999 19:54:00 -0000	[thread overview]
Message-ID: <000f01bf16cf$4835f400$830120d0@abita.kurianinc.com> (raw)
Message-ID: <19991031195400.pfJLYV4Bh6syU_4R22LQp4pJj0tEZNwc1oMeDXng3Zc@z> (raw)
In-Reply-To: <19991014155838.7095.qmail@www0w.netaddress.usa.net>

[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]

Charles is correct.  You also have some typos where some variables aren't
enclosed in parentheses.  The attached file fixes those problems.

To summarize:  make requires that action lines begin with tabs, not spaces.
I don't think make has problems with ^Ms.

Ajit



-----Original Message-----
From:	cygwin-owner@sourceware.cygnus.com
[ mailto:cygwin-owner@sourceware.cygnus.com ] On Behalf Of Charles McKnight
Sent:	Thursday, October 14, 1999 10:59 AM
To:	cygwin@sourceware.cygnus.com
Subject:	RE: compilation problem

Jean,

What appears to be happening is that make does not recognize the spaces
after
the colon (:) or on the following recipe lines.  If you will replace them
with
tabs, this should fix the problem.  I've encountered this issue on other
versions of make before.  Another solution is to modify the make source code
to recognize a space as a legal separator.

Charles McKnight
cmcknigh@fastlane.net

____________________________________________________________________
Get your own FREE, personal Netscape WebMail account today at
http://webmail.netscape.com .

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


[-- Attachment #2: makefile --]
[-- Type: text/plain, Size: 616 bytes --]

# Makefile pour guest.cgi
# création sous Windows
# target : any
# date : 13/10/99

DIR_CGI=/cygnus/cygwin-b20/cgi
INCLUDE_SYS=/cygnus/cygwin-b20/H-i586-cygwin32/i586-cygwin32/include
INCLUDE_APPLI=$(DIR_CGI)/include
CC=/cygnus/cygwin-b20/H-i586-cygwin32/bin/gcc.exe
DIR_EXE=$(DIR_CGI)/bin
DIR_INSTALL=d:/devinternet/cgi


clean:
	rm $(DIR_EXE)/* 
	rm $(DIR_CGI)/*

install:
	cp $(DIR_EXE)/guest.cgi $(DIR_INSTALL)

guest.cgi: $(DIR_CGI)/guest.o
	$(CC) -g $(DEBUG) -o $(DIR_EXE)/guest.cgi $(DIR_CGI)/guest.o

guest.o: $(DIR_CGI)/guest.c
	$(CC) -c -g $(DEBUG) $(DIR_CGI)/guest.c -I$(INCLUDE_SYS) -I$(INCLUDE_APPLI)



  reply	other threads:[~1999-10-31 19:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-14  8:58 Charles McKnight
1999-10-14 22:37 ` Ajit George [this message]
1999-10-31 19:54   ` Ajit George
1999-10-31 19:54 ` Charles McKnight
2000-07-19  7:50 ISNARD Olivier 132311
2000-07-19  8:11 ` Tim Prince
2000-07-19 12:04 Earnie Boyd
2002-07-17 21:30 Compilation problem Ced
2002-07-18  4:11 ` David Starks-Browning
2002-07-18  6:47   ` Ced
2002-07-18  7:34     ` David Starks-Browning
2002-07-18  7:11   ` Ced
2003-11-03 10:50 Cédric Bouttes
2007-02-25 21:14 gcc doesn't like my .o file at the end Larry Hall (Cygwin)
2007-02-26  6:19 ` compilation problem nordine
2007-02-26 13:06   ` Larry Hall (Cygwin)
2020-04-06  9:26 Compilation problem Souleymane SOW
2020-04-06  9:27 ` cygwinautoreply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000f01bf16cf$4835f400$830120d0@abita.kurianinc.com' \
    --to=gajit@kurianinc.com \
    --cc=cygwin@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).