RE: [HACKERS] .exe extension on Windows

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
Cc: Yutaka tanida <yutaka(at)marin(dot)or(dot)jp>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>, pgsql-ports(at)postgresql(dot)org
Subject: RE: [HACKERS] .exe extension on Windows
Date: 2000-06-27 00:42:52
Message-ID: Pine.LNX.4.21.0006270239260.9749-100000@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-ports

Hiroshi Inoue writes:

> Hmm,I see the following in my environment.
>
> bash-2.02$ ls
> CVS Makefile pg_passwd.c pg_passwd.o
> bash-2.02$ make pg_passwd
> gcc -o pg_passwd
> pg_passwd.o -lcrypt -lm -lreadline -ltermcap -lncurses -lcygipc
> -g
> bash-2.02$ ls
> CVS Makefile pg_passwd.c pg_passwd.exe pg_passwd.o
> bash-2.02$ make pg_passwd
> make: `pg_passwd' is up to date.

Seems make is smarter than it wants to admit. Then that would not sit well
with the changes I just made (which would require you to do `make
pg_passwd.exe', unless make is *that* smart). Gotta investigate this in
the GNU make manuals. Thanks.

--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-06-27 00:44:19 Is *that* why debugging backend startup is so hard!?
Previous Message Ryan Kirkpatrick 2000-06-27 00:36:02 Re: [HACKERS] Re: Call for port testing on fmgr changes -- Results!

Browse pgsql-ports by date

  From Date Subject
Next Message Bruce Momjian 2000-06-27 18:08:05 Re: [HACKERS] Re: Call for port testing on fmgr changes -- Results!
Previous Message Ryan Kirkpatrick 2000-06-27 00:36:02 Re: [HACKERS] Re: Call for port testing on fmgr changes -- Results!