> From: "John W. Smay"
> Cc:
> Date: Thu, 10 Oct 2013 15:48:26 -0700
>
> Eli
> > Did you try unzipping all the other executables? If unzipping grotty
> > anew helped to fix a similar problem, maybe unzipping them all will
> > solve more problems?
> I did now .. same problem repeats.
>
Hi charlie,
> now we are only getting a troff permissions error...
>
> "Groff: couldn't exec troff: Permission denied"
My only idea here would be to use soemthing like strace on Linux; it
shows the system calls made by the program to the kernel. By seeing
what requests groff.exe is making to W
Eli
Did you try unzipping all the other executables? If unzipping grotty
anew helped to fix a similar problem, maybe unzipping them all will
solve more problems?
I did now .. same problem repeats.
I nulled all the environmental variables one-by-one and removed all the mks
path entrys
Hi Keith,
> > It looks like a mismatch between the mode used to open the temporary
> > file and the mode that's then used to map a FILE* onto it with
> > fdopen.
...
> Notwithstanding that we probably do really want O_BINARY here, my
> tests on a Win7 Home Premium VM
Now that charlie has confirme
This looks just like the problem I have been having with the Windows port of
groff-1.21 groff does not have permission to run troff for some reason. I
got the port as follows:
I am loading up a new Windows 7 x64 (64 bit) computer, To particular with
groff. To a prior query about groff-1.20.1
To follow up... from the command line:
troff -v
... executes fine
Then when I try
groff -v
... it executes, but I get the troff permissions error.
-charlie
-Original Message-
From: Charlie Van Dien [mailto:char...@vandien.com]
Sent: Thursday, October 10, 2013 12:07 PM
To: 'Ralph C
[PLEASE do not remove the list address from the addressees.]
> From: "John W. Smay"
> Date: Wed, 9 Oct 2013 17:56:12 -0700
>
> I did unzip a new copy of grotty and it fixed grotty complaints, see details
> in the attachment. This did not alter groff denied access to troff.
Did you try unzipp
Thank you for all your help!
We tried the suggestion below, and the grops error has stopped, now we are only
getting a troff permissions error...
"Groff: couldn't exec troff: Permission denied"
Thinking this to be simple enough... I made sure each folder had sufficient
permissions, and I made
Hi charlie,
> Is this something I could contract for a reasonable fee? (a.k.a "not
> looking for a freebie")
Hard fiat currency!? Now you're talking. :-) Well, maybe not. See if
this works out for you.
I've took grops.exe from
http://sourceforge.net/projects/ezwinports/files/groff-1.21-w32-b
