g'day,
Because I read this list in digest form, I'm coming a littel late to the
party. Forgive me, as I'm a few drinks behind, and wont be quite as
snarky and witty as the rest of you... ;-)
> Subject: Re: Multi-Segment Apps - Question
> From: John Marshall <[EMAIL PROTECTED]>
> Date: Wed, 27 Mar 2002 23:58:03 +0100
> X-Message-Number: 68
>
> On Wed, Mar 27, 2002 at 11:37:00AM -0500, [EMAIL PROTECTED] wrote:
> >>> Is there a good description for setting all this up, as if I was
> >>> doing it for the first time? Where?
> [...]
> > I don't find the tools hard to find. I also don't find the setup hard to
> > follow.
>
> Perhaps then you could explain what your previous message's questions
> (above) were *really* asking.
>
> > I followed
> > those instructions to the point where I got an illegal operation in the
> > final step. That made me wonder about that process.
>
> If you think you have found a bug in Cygwin's setup.exe utility, then
> you should report it to the Cygwin people. There's not a lot of point
> talking about it here. (For the record, I've never seen or heard of
> this error.)
In Mike's defense, there may actually be a real bug here in the Cygwin
stuff, possibly around how it sets up paths, or possibly in a version
incompatibility problem. He talks about using B20 as his previous build,
but this doesn't sound right. I seem to recall from somewhere that it's
documented that this wont work with the GCC/PilRC toolset? Certainly in
my experience there's a problem there.
At one point, I tried upgrading my Cygwin installation. I was frustrated
by the lack of a "which" command in the version I was using (Yaweh, at
some point I'm taking the time to get the Linux box back up, so I can
get on to a real machine, but I digress... :-)
In checking something else, I realized one day that "which" was in the
latest Cygwin release I decided to take a bit of time one afternoon to
upgrade. I thought I did it by the book, and ended up getting an error
message from as about "unrecognized option -no-68881". Frankly, I'm late
on my project, so I reverted to using the existing, working, Cygwin and
marked this under "too hard for now..."
This failure may be:
a) an unrelated screwup on my part
b) another instantiation of Mike's problem
c) a documented, known feature of this release that
both he and I missed
d) something that was fixed, and we're both working off a bogus release
e) a warp in the space-time continuum
I suspect Mike doesn't give a shit at this point what's causing the
problem, he just wants a working installation so he can get some work
done. So, enough teaching the man to fish and feeding him for life.
Mike, you might want to check this. What's the package name you're
installing? (the one that fails for me is "cygwin-B20_1-full.exe". I
doubt this is an approved method for checking the version, but you migth
try the following at the bash shell:
> bash --version
The failing version for me gives:
GNU bash, version 2.05a.0(3)-release (i586-pc-cygwin)
The working Cygwin version bash here tells me it is version:
GNU bash, version 2.02.1(2)-release (i586-pc-cygwin32)
I *think* this is a part of the cygwin release "cygwin1.3.10-1.tar.bz2",
but this may be some artifact I've found lying around. In any event, you
might try an earlier version of Cygwin and see if that helps.
And if you figure it out, I'd like to hear since at some point I'm going
back to fix this for myself, once I ship... :-)
- peterd
-----------------------------------------------------------------------
Peter Deutsch [EMAIL PROTECTED]
Gydig Software
"This, my friend, is a pint."
"It comes in pints?!? I'm getting one!!"
- Lord of the Rings
----------------------------------------------------------------------
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
