From: Chris S. <ir0...@gm...> - 2012-08-24 16:08:54
|
Hi All, I'm having a bit of a challenge with make as a result of the recently added Guile support in make. The addition of the Guile support has added a build time dependency on pkg-config which seems to be unavailable in MSYS. As such I posted to the make-w32 mailing list and Eli provided a few suggestions: On 24 August 2012 11:15, Eli Zaretskii wrote: >> Date: Fri, 24 Aug 2012 11:00:57 -0400 >> From: Chris Sutcliffe >> >> Is there a way to disable the guile support when running autoreconf >> when building from CVS? This introduces a dependency on pkg-config >> during configure that is not available under MinGW / MSYS. > > First, there _is_ a Windows port of pkg-config: > > http://www.gtk.org/download/win32.php We can go down the road of potentially using a 3PP tool to build a MinGW utility, but I know historically this I believe has been frowned upon in that now there is an external dependency outside of mingw.org's control. > Second, the official supported way of building a Windows port of Make > is by using build_w32.bat batch file. That script should detect > whether you have Guile and pkg-config, and supports the --without-guile > option to build without Guile even if you have it. This works, but is not historically how I've created the mingw32-make binaries. I'd have to look in to how to generate the lang files, man pages, info, etc. as the batch file seems to only produce the binary (though I haven't looked in to it too much, perhaps it can do more). > And third, if you must use the Posix 'configure's script to build, my > reading of the script is that you should be able to pass the option > "--with-guile=no" to configure and build without Guile. This unfortunately doesn't help as the pkg-config call still remains in the configure script. Thoughts? Chris -- Chris Sutcliffe http://emergedesktop.org http://www.google.com/profiles/ir0nh34d |
From: Earnie B. <ea...@us...> - 2012-08-24 17:11:27
|
On Fri, Aug 24, 2012 at 12:08 PM, Chris Sutcliffe wrote: >> Second, the official supported way of building a Windows port of Make >> is by using build_w32.bat batch file. That script should detect >> whether you have Guile and pkg-config, and supports the --without-guile >> option to build without Guile even if you have it. > > This works, but is not historically how I've created the mingw32-make > binaries. I'd have to look in to how to generate the lang files, man > pages, info, etc. as the batch file seems to only produce the binary > (though I haven't looked in to it too much, perhaps it can do more). > Thwwwt... >> And third, if you must use the Posix 'configure's script to build, my >> reading of the script is that you should be able to pass the option >> "--with-guile=no" to configure and build without Guile. > > This unfortunately doesn't help as the pkg-config call still remains > in the configure script. > > Thoughts? IIRC, there are environment variables that can be set to remove the need for pkg-config. I'll have to research for it. -- Earnie -- https://sites.google.com/site/earnieboyd |
From: Chris S. <ir0...@gm...> - 2012-08-25 16:30:26
|
On 24 August 2012 13:11, Earnie Boyd wrote: > On Fri, Aug 24, 2012 at 12:08 PM, Chris Sutcliffe wrote: >>> And third, if you must use the Posix 'configure's script to build, my >>> reading of the script is that you should be able to pass the option >>> "--with-guile=no" to configure and build without Guile. >> >> This unfortunately doesn't help as the pkg-config call still remains >> in the configure script. >> >> Thoughts? > > IIRC, there are environment variables that can be set to remove the > need for pkg-config. I'll have to research for it. I haven't come across anything on Google for it. The specific error I'm getting is: /src/make/make-3.82.90-mingw32-cvs-20120823-1/src/make/configure: line 8403: PKG_PROG_PKG_CONFIG: command not found /src/make/make-3.82.90-mingw32-cvs-20120823-1/src/make/configure: line 8415: syntax error near unexpected token `GUILE,' /src/make/make-3.82.90-mingw32-cvs-20120823-1/src/make/configure: line 8415: ` PKG_CHECK_MODULES(GUILE, guile-2.0, have_guile=yes,' I'm far from an autotools guru, so if anyone knows a way around this, please let me know. Thank you, Chris -- Chris Sutcliffe http://emergedesktop.org http://www.google.com/profiles/ir0nh34d |
From: Chris S. <ir0...@gm...> - 2012-08-25 23:08:15
|
On 25 August 2012 12:30, Chris Sutcliffe wrote: > On 24 August 2012 13:11, Earnie Boyd wrote: >> On Fri, Aug 24, 2012 at 12:08 PM, Chris Sutcliffe wrote: >>>> And third, if you must use the Posix 'configure's script to build, my >>>> reading of the script is that you should be able to pass the option >>>> "--with-guile=no" to configure and build without Guile. >>> >>> This unfortunately doesn't help as the pkg-config call still remains >>> in the configure script. >>> >>> Thoughts? >> >> IIRC, there are environment variables that can be set to remove the >> need for pkg-config. I'll have to research for it. > > I haven't come across anything on Google for it. The specific error > I'm getting is: > > /src/make/make-3.82.90-mingw32-cvs-20120823-1/src/make/configure: line > 8403: PKG_PROG_PKG_CONFIG: command not found > /src/make/make-3.82.90-mingw32-cvs-20120823-1/src/make/configure: line > 8415: syntax error near unexpected token `GUILE,' > /src/make/make-3.82.90-mingw32-cvs-20120823-1/src/make/configure: line > 8415: ` PKG_CHECK_MODULES(GUILE, guile-2.0, have_guile=yes,' > > I'm far from an autotools guru, so if anyone knows a way around this, > please let me know. I've created a local patch that disables the pkg-config call and disabled guile support. In terms package naming, as suggested by Keith, I've used: make-3.82.90-mingw32-cvs-20120823-1-*.tar.lzma But I'm not sure if this is correct? Instead should it be: make-3.82.90-cvs-20120823-1-mingw32-*.tar.lzma As this form seems more in keeping with the existing make-*-mingw32 packages. Also, I've seen the emails and read that we've officially switched to git, which raises a couple of questions for me: 1. What git should I use? 2. Has the installer been updated to use git, or is it still cvs based? Please let me know. Chris -- Chris Sutcliffe http://emergedesktop.org http://www.google.com/profiles/ir0nh34d |
From: Earnie B. <ea...@us...> - 2012-08-26 01:31:14
|
On Sat, Aug 25, 2012 at 7:08 PM, Chris Sutcliffe <ir0...@gm...> wrote: > > Also, I've seen the emails and read that we've officially switched to > git, which raises a couple of questions for me: > 1. What git should I use? > 2. Has the installer been updated to use git, or is it still cvs based? I use the msysgit release but remove the msys-1.0.dll from it's bin directory. I installed to c:\opt\git and add /c/opt/git/bin to the end of my PATH. -- Earnie -- https://sites.google.com/site/earnieboyd |
From: Keith M. <kei...@us...> - 2012-08-26 13:19:23
|
On 26/08/12 00:08, Chris Sutcliffe wrote: > In terms package naming, as suggested by Keith, I've used: > > make-3.82.90-mingw32-cvs-20120823-1-*.tar.lzma > > But I'm not sure if this is correct? It is. > Instead should it be: > > make-3.82.90-cvs-20120823-1-mingw32-*.tar.lzma No. > As this form seems more in keeping with the existing make-*-mingw32 > packages. The latter form may not be definitively incorrect; mingw-get may still accept it as a valid package name, but it will not identify it as a CVS snapshot. As a result, chronological sorting in release order may not work as you expect. OTOH, the former pattern is definitively correct, will be so identified, and will sort accordingly. -- Regards, Keith. |