Re: .ONESEHLL not working as expected in 3.82

2013-04-29 Thread Eli Zaretskii
> From: Paul Smith > Cc: bug-make@gnu.org > Date: Sun, 28 Apr 2013 14:37:29 -0400 > > > My plan was to write dlopen and dlsym, and add them to > > w32/compat/posixfcn.c. But I need to understand the semantics of > > global_dl in order to do that correctly. > > It's up to you how you think it be

Re: .ONESEHLL not working as expected in 3.82

2013-04-29 Thread Eli Zaretskii
> From: Paul Smith > Cc: bug-make@gnu.org > Date: Sun, 28 Apr 2013 15:15:09 -0400 > > I think it pseudo-code it would look something like this: > > if (posix-shell) > { > ...strip out @-+ from LINE... > } > #ifdef WINDOWS32 > if (need a batch file) > { > ...write LINE

Re: .ONESEHLL not working as expected in 3.82

2013-04-28 Thread Eli Zaretskii
> From: Paul Smith > Cc: bug-make@gnu.org > Date: Sun, 28 Apr 2013 16:01:05 -0400 > > I guess I thought you were writing a batch file, > then invoking the shell with the batch file name as the command to run. > E.g., "command.com " vs. "perl " etc. I am naive > but it seems like that should work

Re: .ONESEHLL not working as expected in 3.82

2013-04-28 Thread Paul Smith
On Sun, 2013-04-28 at 22:41 +0300, Eli Zaretskii wrote: > > I think the implementation you have is not quite right. I think the > > parsing of the @-+ stuff is common across all platforms if we have a > > shell, so you don't need the "else /* non-posix shell */". > > I do need a separate code, be

Re: .ONESEHLL not working as expected in 3.82

2013-04-28 Thread Eli Zaretskii
> From: Paul Smith > Cc: bug-make@gnu.org > Date: Sun, 28 Apr 2013 15:15:09 -0400 > > The goal of this code in the if-statement is to implement a special case > allowing ONESHELL to be easier to add in the case where you DO have a > standard shell. In that case, and ONLY in that case, we remove

Re: .ONESEHLL not working as expected in 3.82

2013-04-28 Thread Eli Zaretskii
> From: Paul Smith > Cc: bug-make@gnu.org > Date: Sun, 28 Apr 2013 14:37:29 -0400 > > On Sun, 2013-04-28 at 20:19 +0300, Eli Zaretskii wrote: > > > From: Paul Smith > > > Cc: bug-make@gnu.org > > > Date: Sat, 27 Apr 2013 16:58:54 -0400 > > > > > > On Sat, 2013-04-27 at 23:00 +0300, Eli Zaretski

Re: .ONESEHLL not working as expected in 3.82

2013-04-28 Thread Paul Smith
On Sun, 2013-04-28 at 21:14 +0300, Eli Zaretskii wrote: > > From: Paul Smith > > Cc: make-...@gnu.org, bug-make@gnu.org > > Date: Sat, 27 Apr 2013 12:54:10 -0400 > > > > On Sat, 2013-04-27 at 19:17 +0300, Eli Zaretskii wrote: > > > The .ONESHELL feature is now supported on MS-Windows, for the def

Re: .ONESEHLL not working as expected in 3.82

2013-04-28 Thread Paul Smith
On Sun, 2013-04-28 at 20:19 +0300, Eli Zaretskii wrote: > > From: Paul Smith > > Cc: bug-make@gnu.org > > Date: Sat, 27 Apr 2013 16:58:54 -0400 > > > > On Sat, 2013-04-27 at 23:00 +0300, Eli Zaretskii wrote: > > > That would be nice, indeed. > > > > OK, pushed. > > Thanks! But I see you kept g

Re: .ONESEHLL not working as expected in 3.82

2013-04-28 Thread Eli Zaretskii
> From: Paul Smith > Cc: make-...@gnu.org, bug-make@gnu.org > Date: Sat, 27 Apr 2013 12:54:10 -0400 > > On Sat, 2013-04-27 at 19:17 +0300, Eli Zaretskii wrote: > > The .ONESHELL feature is now supported on MS-Windows, for the default > > Windows shell (cmd.exe) or compatible replacements, in the

Re: .ONESEHLL not working as expected in 3.82

2013-04-28 Thread Eli Zaretskii
> From: Paul Smith > Cc: bug-make@gnu.org > Date: Sat, 27 Apr 2013 16:58:54 -0400 > > On Sat, 2013-04-27 at 23:00 +0300, Eli Zaretskii wrote: > > That would be nice, indeed. > > OK, pushed. Thanks! But I see you kept global_dl and the call to dlopen with the 1st argument NULL. What is the pur

Re: .ONESEHLL not working as expected in 3.82

2013-04-27 Thread Paul Smith
On Sat, 2013-04-27 at 23:00 +0300, Eli Zaretskii wrote: > That would be nice, indeed. OK, pushed. You should be able to simply write a new load_objects() function and drop it in. Or put it into a w32 file or whatever. ___ Bug-make mailing list Bug-m

Re: .ONESEHLL not working as expected in 3.82

2013-04-27 Thread Eli Zaretskii
> From: Paul Smith > Cc: bug-make@gnu.org > Date: Sat, 27 Apr 2013 15:32:22 -0400 > > Well, we already maintain a list of modules that are loaded in > the .LOADED variable. Although it's not written like that today, I have > no problem changing the code to check that variable to see whether the

Re: .ONESEHLL not working as expected in 3.82

2013-04-27 Thread Paul Smith
I took with make-w32 list off. On Sat, 2013-04-27 at 22:18 +0300, Eli Zaretskii wrote: > I added a similar facility to Gawk, but there a problem was much > simpler, because Gawk itself was tracking the loaded extensions in > platform-independent code. So my emulation of dlopen didn't need to > su

Re: .ONESEHLL not working as expected in 3.82

2013-04-27 Thread Eli Zaretskii
> From: Paul Smith > Cc: make-...@gnu.org, bug-make@gnu.org > Date: Sat, 27 Apr 2013 14:28:18 -0400 > > On Sat, 2013-04-27 at 20:55 +0300, Eli Zaretskii wrote: > > Note: there's one more major feature in current git repo that needs to > > be made available on Windows: dynamic loading of extension

Re: .ONESEHLL not working as expected in 3.82

2013-04-27 Thread Paul Smith
On Sat, 2013-04-27 at 20:55 +0300, Eli Zaretskii wrote: > Note: there's one more major feature in current git repo that needs to > be made available on Windows: dynamic loading of extensions. That is > my highest priority for Make todo list. Yes. I wonder if there are features of gnulib which ma

Re: .ONESEHLL not working as expected in 3.82

2013-04-27 Thread Eli Zaretskii
> From: Paul Smith > Cc: make-...@gnu.org, bug-make@gnu.org > Date: Sat, 27 Apr 2013 12:54:10 -0400 > > Also, I wonder if you have a few minutes to go through the open Windows > bugs in Savannah and make a comment or whatever to those which are still > waiting (some are waiting for other people,

Re: .ONESEHLL not working as expected in 3.82

2013-04-27 Thread Eli Zaretskii
> Date: Mon, 30 Aug 2010 17:09:51 +0100 > From: "Anjum Naseer" > > I have built the 3.82 version of GNU Make using the Microsoft Visual C++ > compiler and it seems to work fine. > However, I cannot get it to work correctly with the .ONESHELL option. > I created a dummy makefile (dummy.mak) with t