Re: Problem with configure when trying to build gcc 5.3
David Gressett <[email protected]> Mon, 9 Jan 2017 19:39:49 +0000
| Newsgroups | gmane.comp.gnu.mingw.devel |
|---|---|
| Message-ID | <MWHPR13MB16470535EF6F14A355C598C8D4640@MWHPR13MB1647.namprd13.prod.outlook.com> |
>From: Keith Marshall <[email protected]> >Sent: Sunday, January 8, 2017 7:28 AM ... snip ... >> config.status, however, contained an option list that had no --build >> option. At that point, I tried the compile step, using tee to save >> the console display. It eventually crashed with this message: >> >> C:\MinGW\mingw32\bin\ld.exe: cannot find dllcrt2.o: No such file or directory Hmm. dllcrt2.o is a component of mingwrt; for me it lives in '/home/keith/mingw32/lib`, (under the '/home/keith/mingw32' prefix, where my Linux hosted mingw32-gcc cross-compiler is installed). ... snip ... >I've never tried to build GCC natively on Windows; the whole >process is much too painful! Perhaps you need something like >the stage-by-stage procedure used for my cross-compiler? Or >maybe, a 'make bootstrap' procedure, (for which the mingw-pkg >specification isn't set up, in the 'mingw-pkg compile' case)? There should be a clue to the dllcrt2.0 problem in Earnie's build system that was used for the 4.8.1 release - when I hack it to build 5.3.0, I have problems with make stage, as I previously mentioned, but the the make compile step completes with no dllcrt2.o problem. I did a test builds of gcc 5.3.0 using both Earnie's system and mingw-pkg. In order to make a better comparison, I modified the build options in gcc-5.3.0-mingw32.pkgspec to be an exact duplicate of the ones that I lifted from the package.ini file in Earnie's 4.8.1 build. The builds had the same result as before - The compile step succeeded in Earnie's system and failed with the dllcrt.o problem with the mingw-pkg system I did a diff of the config.log and config.status files that were produced by the two build systems. I found that the only difference was the path relationship between the build and source directories, which is a trivial difference. >From that, I conclude that mingw-pkg in a native Windows environment is doing something that causes problems for make; I will need to do some more analysis to find out what is happening. It would help if I knew what command line that mingw-pkg creates for make in the compile stage, but 'sh -vx' should be useful there. ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi