Mail Archives: djgpp/2012/07/31/08:15:06
Hi,
On Saturday, July 28, 2012 10:35:02 AM UTC-5, USA Choice User wrote:
> On Jul 12, 7:58 pm, rugx DOT DOT DOT AT gmail DOT com wrote:
>
> > ========================================
> > --- callproc.c 2011-01-08 19:45:14 +0000
> > +++ callproc.new 2012-07-07 19:37:48 +0000
> > @@ -929,6 +929,10 @@
> > int fd;
> >
> > BLOCK_INPUT;
> > +
> > + char* rugxulo = strstr(tempfile,".xxx");
> > + if (rugxulo) strncpy(rugxulo,".XXX",4);
> > +
> > fd = mkstemp (tempfile);
> > UNBLOCK_INPUT;
> > if (fd == -1)
> > ========================================
>
> Sorry I took so long to reply. I finally got Emacs
> 23.3 so it will compile using DJGPP on Windows 98SE,
> with LFN set to "Y". Following your version suggestion,
> I only had to make one change--I substituted GCC 4.4.4
> for GCC 4.7.0. I also substituted GPP 4.4.4 for GPP
> 4.7.0 for consistency.
Normally I hate the idea of using billions of different versions of the same tool, but in this case it's almost unavoidable.
> However, I can't figure out how or where to splice
> in your patch, in callproc.c. I did find the file
> in the source folder, but to me at least it's not
> obvious how to fix it (I'm not a C programmer yet,
> but I can figure things out and follow directions).
>
> If you could walk me through the process I'd
> appreciate it. Thanks.
It's just a diff file from DIFF.EXE that can be manually typed in (see section beginning at line 929 of callproc.c) or just use PATCH.EXE, e.g. "patch -i rugxulo.dif", then it should build.
Really, I hate the idea that end users have to recompile anything, esp. if that's not their thing, hence the binary patch (technically easier to apply but inferior overall). But I admit I didn't really make that automated either. Oh well.
DJGPP doesn't come with diff.exe or patch.exe by default, so you'll have to grab them separately.
http://na.mirror.garr.it/mirrors/djgpp/beta/v2gnu/dif32br3.zip
http://na.mirror.garr.it/mirrors/djgpp/beta/v2gnu/pat261b.zip
- Raw text -