Re: Issue with building make with mingw32 compilers.

> Date: Fri, 29 Nov 2013 21:09:47 +0400 > From: Pavel Fedin > CC: bug-make@gnu.org > > >> and that means that I need to use --host=i586-mingw32msvc when building > >> make. > > > Why does the prefix end with "msvc"? The MSVC compiler is not > > involved in this build or in the target system, so

Re: Issue with building make with mingw32 compilers.

Hello, Eli. Saturday, November 23, 2013, 12:00:49 you wrote: >> and that means that I need to use --host=i586-mingw32msvc when building >> make. > Why does the prefix end with "msvc"? The MSVC compiler is not > involved in this build or in the target system, so the prefix sounds > wrong. May

Re: MSVC runtime lib issue

> From: "Gisle Vanem" > Date: Fri, 29 Nov 2013 14:01:46 +0100 > > This project file doesn't specify any runtime lib to link with. Hence the > default is to use > LIBCMT.LIB as if '-MT' was used. I would like to build using '-MD' (or > '-MDd') which > pulls in msvcrt[d].dll (most MSVC software

MSVC runtime lib issue

I've compiled the lastest Git-repo with MSVC using the make_msvc_net2003.vcproj project. This is a bit outdated (was converted to make_msvc_net2003.vcxproj by my Visual Studio 2010. I also had to insert guile.c in again). This project file doesn't specify any runtime lib to link with. Hence the d

[bug #40322] Interrupting a build with CTRL-C doesn't kill subprocesses

Update of bug #40322 (project make): Status:None => Not A Bug Open/Closed:Open => Closed ___ Reply to this item at:

Re: [bug #40639] GNU Make with profiling information

When I did something similar (which I am not allowed to post) I made a new file for each submake and the output filename "base" was in an environment variable. I realise that nobody ever wants to change the way they implemented something but I thought I'd mention it. Also, having written a few ex

[bug #40344] Can't handle Windows path names longer than 259 characters

Follow-up Comment #8, bug #40344 (project make): One other thing: such a patch will probably be quite substantial, so you will need legal paperwork to assign the copyright to the FSF, before the patch can be admitted. If that's fine with you, I suggest to start the paperwork ASAP, as it can take

[bug #40322] Interrupting a build with CTRL-C doesn't kill subprocesses

Follow-up Comment #8, bug #40322 (project make): Please close. I /think/ all the issues i've had so far are due to our intermediate processes not handling things well. I'll reopen if it turns out there is something wrong with make. ___ Repl

[bug #40322] Interrupting a build with CTRL-C doesn't kill subprocesses

Follow-up Comment #7, bug #40322 (project make): Any news on this one? Should I close it? ___ Reply to this item at: ___ Message sent via/by Savannah