> -----Original Message-----
> From: > Max T. Woodbury
> Sent: mardi 24 mai 2005 01:17
> Julien Lecomte wrote:
> > Here's a link to the problem and resolution:
> > http://www.amanitamuscaria.org/content/view/10/0/
> There are two items in there, one of which you patch in
> exactly the same way that I worked out a few minutes ago. A
> patch should be written for 'msys' and whoever wrote that
> header originally.
> I was going to do it, but you have priority if you want it.
Yeah, my inbox synchronized with the outbox... And I saw that you found the
The current header file in the CVS of mSys is already patched.
> The note on 'termcap' is correct, but is not the whole story.
> Since the replacement 'termcap' is incorrect, either its
> generation has to be corrected or its proper source needs to
> be found. Then there needs to be a patch that puts the
> result in the generated package's space, not in the current
> system. The proximate patch for the placement is to
> 'configure', but the ultimate patch should be to the
> generation file. Since there is a work around, I was going
> to wait on it until I'd gotten a whole build done before
> going into that.
I've still got to understand what exactly that termcap file does. With or
without it, everything works fine for me.
> > I'll (or if someone else wants to) put that on the MinGWiki.
> > Julien
> > Ps : About the subject "How do I recreate the MSYS
> distribution?"; I'm
> > also trying to provide a clean and easy way to build what I call a
> > "Msys From Scratch"
> > Please contribute !!! At the current stage, it almost works (some
> > headers aren't installed, and thus the new mSys doesn't yet really
> > work) http://www.mingw.org/MinGWiki/index.php/mSysFromScratch
> You've set it that up as a 'howto'. There was already a much
> smaller 'howto' on part of it. I've been writing a chronicle
> and posted a part of it to this list a little while ago.
> You're welcome to use the information it contains with a
> 'thanks to' note.
The HowTo is basically just on the mSys package, not on recreating a whole
mSys with tools and co.
> When I looked at what you've written so far, the biggest
> problem I have is the reference to GnuW32. Whoever is doing
> that is recreating the wheel and only doing a fair job of it.
> Their personal taste in build environments gets into their
> packages and will make it harder for someone else to use
> their basic work. Further, using it will slow down getting
> corrections to their proper point of application.
> I've tried to locate original distributions where I could.
Yeah, I hate that windres stuff too. If I have spare time, I'll try to do a
autoconf macro to test for windres and autocreate a rc file for executables
Nevertheless, the flex and bison packages were, at the time, the best ones I
had found. I'm not too sure about a compiling a canonical coreutils from
mSys though (to be tested in the days to come)
> I guess I'm actually trying to go one step further than you are.
> When I say 'source' I mean a CVS or other network repository
> source, not just a tarball. A tarball will meet many
> requirements and will let someone make changes they need, but
> the result will be a forked project with the resulting
> contribution to the OSS community diluted. But that's
> getting pretty deep and I have a personal problem I have to
> take care of PDQ.
I'm also for CVS and not just tarballs, but that means that the mSys module
should contain all the cvs of basically everytool that is currently missing
(flex, bison, etc...)
Earnie, what's your input on that ?