On 11:21:57 pm 2005-04-23 "Max T. Woodbury" <max.teneyck.woodbury@...> wrote:
> Earnie Boyd wrote:
> > On 2:20:22 pm 2005-04-21 "Max T. Woodbury" <max.teneyck.woodbury@...
> rizon.net> wrote:
> > > I've been trying to build a useable MSYS from CVS HEAD with
> > > changes and failing.
> > >
> > > I figured that I might have better luck if I tried to build a
> > > base 1.0.10 distribution so I could be sure I hadn't messed up
> > > something without knowing it was important. I pulled and
> > > unpacked the src tarball from sourceforge, made a working copy
> > > of the resulting tree with cp -pR and tried configure and make.
> > > I seem to be missing some crucial step...
> > >
> > > Could you point me at or provide a description of what I should
> > > be doing?
> > >
> > Did you follow these instructions? http://www.mingw.org/MinGWiki/in
> Thank you that was the pointer I needed.
> Someone is in the process of updating this information. This should
> be very helpful indeed. However, there are some 'interesting'
> statements in the new description that raise questions when you think
> about them.
> 1) There is a recommendation to get TortoiseCVS. msysDTK already
> includes CVS. Why get a second version?
None, as far as I can see. You're welcome to modify the suggestion to
reflect the case of, "if you're not going to install msysDTK or just want a
GUI for CVS if you do" feel free. This is a community effort.
> 2) There is a recommendation to get GnuWin32 bison. There is a MinGW
> bison package. I suspect that the MinGW version is specifically
> adapted to MSys/MinGW, so why get the non-MinGW version? (Also,
> there is an implication that FLex is needed. Is this true?)
I hope to have a mingwPORT of these up so that you can build them to your
liking and store them where you want them. The problems with bison/flex
stem from pathing problems. The newer bison requires the m4 scripting
language. Part of the problem with the MinGW bison is that the MinGW m4 it
uses isn't properly ported. Now m4 is included with MSYS so there is a
conflict of applications. I could keep going but I won't.
> 3) I did not see a sequence for building the test suites. I happen to
> believe strongly in regression testing, so I would like to be able
> to run any test programs available. What is needed for this?
Test suites for which package are you talking about? You've gone from
talking about build MSYS to talking about the entire MinGW suite. I make
mention of the testsuite of the MSYS package for building MSYS.
> Note on the download page -- Originally I stopped scrolling when I
> came the the 'Previous' table simply because I didn't want to store
> the old stuff and missed the 'Snapshot' section as a result. Could
> you please move the 'Snapshot' section so that is follows 'Current'
> but precedes 'Previous'?
No, the order is presented as it is given by the SF File Release page. I
use a script to create the table at http://www.mingw.org scrubbing the SF File
Release page. The script that creates the table is currently broken due to
changes by SF to the File Release page. There is one party looking at
using PHP to create the page for me so that external scripting isn't
needed. Perhaps once that happens we can reorder the table.
MinGW - http://www.mingw.org/
Wiki - http://www.mingw.org/MinGWiki/
Bug Report - http://sourceforge.net/tracker/?group_id=2435&atid=102435
Submit Patch - http://sourceforge.net/tracker/?group_id=2435&atid=302435
SF Project - http://sourceforge.net/projects/mingw
Job Listing - http://sf.net/people/viewjob.php?group_id=2435&job_id=21643