[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 2.4 Release in 24hrs
From: |
Charles Wilson |
Subject: |
Re: 2.4 Release in 24hrs |
Date: |
Sun, 19 Sep 2010 16:16:39 -0400 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 |
On 9/19/2010 3:27 PM, Bob Friesenhahn wrote:
> The 'make' used is GNU make 3.79.1.
Yikes. Where did THAT come from? MSYS has provided at least make-3.81
for several years; the current msys make is 3.82.
> There is a 'mingw32-make' which is
> GNU make 3.82, but does not seem to work under MSYS.
Right. mingw32-make is for when you do NOT have msys installed, and
just want to use a makefile with MinGW gcc. Obviously, without msys,
you can't run configure scripts, or generate Makefile's from
Makefile.in's, etc -- or use libtool. Just as obviously, when building
libtool itself, you darned well better have msys installed, so
mingw32-make is not appropriate. Besides, mingw32-make doesn't grok
msys-style pathnames.
I sounds like your msys installation is WAY out of date. What I would
suggest is the following:
1) download and install mingw-get (get the .zip file, and unpack it
somewhere innocuous like C:\Temp\MinGW-Installer -- NOT C:\MinGW,
because we don't want to disturb your existing TDM mingw compiler.
You do not want to use easier mingw-get-inst wrapper, because it will
automatically also install mingw.org's gcc, and you're using TDM. You
*could* use mingw-get-inst, but (a) you'd have to pick a different
installation directory, and (b) by default, your new msys would be in
C:\<mingw-inst-dir>\msys\1.0, NOT C:\msys\1.0.
2) edit C:\Temp\MinGW-Installer\var\lib\mingw-get\data\profile.xml (if
it doesn't exist, copy default.xml). You should change the following
two lines:
<sysroot subsystem="mingw32" path="%R" />
<sysroot subsystem="MSYS" path="%R/msys/1.0" />
To this:
<sysroot subsystem="mingw32" path="%R" />
<sysroot subsystem="MSYS" path="C:/msys/1.0" />
The default configuration will install a new MinGW into <whereever
mingw-get is>, and a new MSYS into <whereever mingw-get-is>/msys/1.0.
You don't want that...so you have to edit the defaults.
You might want to move your existing msys installation out of the way.
Then, from a cmd prompt, cd to C:\Temp\MinGW-Installer\bin and do this:
mingw-get update
mingw-get install mingw-dtk
The first command updates all of the locally cached package manifests to
the latest version. The second command downloads and installs a
selection to tools that will closely mimic the old "MSYS-DTK" package --
into C:\msys\1.0\*. However, as mingw-dtk (and the old "MSYS-DTK")
collection includes "mingw"-ish autoconf/automake/libtool, THOSE tools
will get installed into <wherever-mingw-get-is>/*.
It's up to you whether you should brute force copy these files over onto
your existing TDM C:\MinGW or not (but do NOT put them into
C:\msys\1.0!!!) Alternatively, of course, you could edit the mingw32
subsystem path specification in profile.xml, and install THOSE
components directly into C:\MinGW.
After that, you need to edit C:\msys\1.0\etc\fstab to add
C:\MinGW /mingw
as usual...but that's old hat.
--
Chuck
- Re: 2.4 Release in 24hrs, (continued)
- Re: 2.4 Release in 24hrs, Ralf Wildenhues, 2010/09/19
- Re: 2.4 Release in 24hrs, Bob Friesenhahn, 2010/09/19
- Re: 2.4 Release in 24hrs, Ralf Wildenhues, 2010/09/19
- Re: 2.4 Release in 24hrs, Bob Friesenhahn, 2010/09/19
- Re: 2.4 Release in 24hrs, Ralf Wildenhues, 2010/09/19
- Re: 2.4 Release in 24hrs, Bob Friesenhahn, 2010/09/19
- Re: 2.4 Release in 24hrs,
Charles Wilson <=
Re: 2.4 Release in 24hrs, Peter Rosin, 2010/09/19
Re: 2.4 Release in 24hrs, Eric Blake, 2010/09/20
Re: 2.4 Release in 24hrs, Peter Rosin, 2010/09/21
Re: 2.4 Release in 24hrs, Charles Wilson, 2010/09/21