Re: Problem with configure when trying to build gcc 5.3
David Gressett <[email protected]> Tue, 3 Jan 2017 14:24:41 +0000
| Newsgroups | gmane.comp.gnu.mingw.devel |
|---|---|
| Message-ID | <DM5PR13MB1641A604635B135CE5A9BE98D46E0@DM5PR13MB1641.namprd13.prod.outlook.com> |
From: Keith Marshall <[email protected]> Sent: Sunday, January 1, 2017 4:57 PM >On 01/01/17 22:15, David Gressett wrote: >> I found a problem; it contained --build=x86_64-pc-linux-gnu >- From whence is it picking that up? For me, that comes from my >$HOME/.mingw-pkgrc; it should not be defined otherwise. >> instead of the expected -build=mingw32 >Why is this expected? If your $build == $host, (as would be the >norm for a native build), your configure line should (ideally) >not specify either --build or --host. >> I have a copy of .mingw-pkgrc in both my $HOME directory and >> the gcc build directory. >Well, that's just plain wrong; if you need it at all, (which you >may not, unless you have a burning desire to customize something), >then it belongs in $HOME, and nowhere else. >> It appears that mingw-pkg is behaving badly in msys on my >> Windows 10 computer. My next step is to avoid mingw-pkg and >> do all the patching and configuration manually. >Well, okay as an interim measure, but we really need to debug this. >Did you run 'mingw-pkg patch'? In the source or the build tree? >If so, what was its (console) output? I ran it as you specified in you message in the MinGW list: $ cd $HOME/build/gcc-5.3.0-mingw32 $ mingw-pkg SRCDIR=../../src/gcc-5.3.0 patch For my next attempt, I removed both copies of .mingw-pkgrc., deleted all the remains of the previous attempt from my build directory and did the patch and configure steps again. This time, I used tee to save the console display and stayed to watch the patch step. $ mingw-pkg SRCDIR=../../src/gcc-5.3.0 patch | tee ../mingw-pkg-patch.log the console showed this: >>> apply patches >>> done. It completed so quickly that it is obvious that it really did no patches, rather than suppressing or redirecting any console output. I then did the configure: $ mingw-pkg SRCDIR=../../src/gcc-5.3.0 configure | tee ../mingw-pkg-configure.log The configure step produced exactly the same results as my previous configure, even though there was no .mingw-pkgrc: The console display still announced that it would build java but not ada and the configure command line still contained --build=x86_64-pc-linux-gnu. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot