On Tue, Nov 12, 2002 at 05:23:54AM -0800, Joe Siebenmann wrote:
> Is'n it obvious I just substituted the actual name of my app with
> (myapp)? That was probably a mistake..
When you write "On the 2nd line Make says", you should not be surprised
when people believe you and proceed to assume that make is indeed saying
precisely what you reported.
General bug reporting tip for everyone: if you're going to edit what
make or some other tool said, you need to mention, *clearly*, that you're
doing that. But generally it's best to just report the output literally.
> If make works on a makefile
> named "Makefile", or "makefile", but chokes on "MAKEFILE", I'd say
> that's a problem.
Interesting -- how come you never posted this explanation back in May?
The make documentation says it looks for "Makefile" and "makefile" (and
also "GNUmakefile"), so it's not so surprising that it doesn't find
"MAKEFILE", just as it doesn't find "meekfeel". Of course, on a
case-insensitive filesystem, it is somewhat surprising! The proper
recourse, if you'd like to see this improved, would be to contact the
Cygwin people and find out if they've considering configuring their make
with HAVE_CASE_INSENSITIVE_FS.
However make is not a part of prc-tools, so a subject line of "Cygwin
PRC-TOOLS problems on XP.." was misleading.
> As far as my pilrc problem, I gave Aaron a sample app that clearly
> showed the problem. run pilrc 2.8 on it and it's "fine", run that
> version of 2.9 on it and the "problem" shows up.
As you say, that was a problem with PilRC. PilRC is a part of neither
prc-tools nor Cygwin. So a subject line of "Bug in new Cygwin/
PRC-Tools?" was misleading.
> Every one of my "problems" has been real.
I did not say that you have not been having problems. But I did ask you
to use subject lines that are a little more descriptive and accurate
than "prc-tools problem". If every message here was entitled "Palm OS
programming problem" or "CodeWarrior problem" or "prc-tools problem",
it would not be a very pleasant forum to read, no?
So have you tracked down your problem yet? Are you typing "make" from
an ordinary Windows command prompt? You might want to try it also from
within bash -- you don't seem to be getting much diagnostic information
from your shell (unless you have elided that too!), and a Unix shell
would be more descriptive if the problem is, for example, that it cannot
find a command named "multigen".
John
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
