>> In groff's src/libs/libgroff/tmpname.cpp, line 105, `O_BINARY' is
>> missing.
I've added this now in the CVS repository.
> If you are doing this, you also need to ensure that O_BINARY is
> actually defined; [...]
This is already handled in header file `nonposix.h'.
Werner
Corderoy [mailto:ra...@inputplus.co.uk]
Sent: Friday, October 11, 2013 12:04 PM
To: char...@vandien.com
Cc: keithmarsh...@users.sourceforge.net; t...@tonykrier.com; groff@gnu.org
Subject: Re: [Groff] need help resolving groff error
Hi charlie,
> We tried the suggestion below, and the grops error has stopp
Hi charlie,
> We tried the suggestion below, and the grops error has stopped
Good.
> now we are only getting a troff permissions error...
>
> "Groff: couldn't exec troff: Permission denied"
As are others. You'r running groff from Perl IIRC. Does
perl -le 'system("groff -v"); print $?'
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
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
2013 12:07 PM
To: 'Ralph Corderoy'
Cc: 'keithmarsh...@users.sourceforge.net'; 't...@tonykrier.com';
'groff@gnu.org'
Subject: RE: [Groff] need help resolving groff error
Thank you for all your help!
We tried the suggestion below, and the grops error has stoppe
Ralph Corderoy'
Cc: 'keithmarsh...@users.sourceforge.net'; 't...@tonykrier.com'; 'groff@gnu.org'
Subject: RE: [Groff] need help resolving groff error
Thank you for all your help!
We tried the suggestion below, and the grops error has stopped, now we are only
gett
eroy [mailto:ra...@inputplus.co.uk]
Sent: Thursday, October 10, 2013 8:14 AM
To: char...@vandien.com
Cc: keithmarsh...@users.sourceforge.net; t...@tonykrier.com; groff@gnu.org
Subject: Re: [Groff] need help resolving groff error
Hi charlie,
> Is this something I could contract for a reasonabl
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
e] On Behalf Of
Werner LEMBERG
Sent: Wednesday, October 09, 2013 6:50 PM
To: keithmarsh...@users.sourceforge.net
Cc: char...@vandien.com; t...@tonykrier.com; groff@gnu.org
Subject: Re: [Groff] need help resolving groff error
> so this implementation, at least, does take care of setting the
> so this implementation, at least, does take care of setting the
> stream mode as O_BINARY.
In groff's src/libs/libgroff/tmpname.cpp, line 105, `O_BINARY' is
missing. Charlie, Tony, can you add this and recompile groff,
checking whether such a change solves the issue?
Werner
Hi charlie,
> > 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.
> I have versions that *were* working prior to a reprovisioning of the
> 2008R2 Server. I have lousy install docs (this is my own fau
ctory groff is using, else allow
me to force one when I invoke groff?
-charlie
-Original Message-
From: Ralph Corderoy [mailto:ra...@inputplus.co.uk]
Sent: Wednesday, October 09, 2013 3:47 PM
To: char...@vandien.com
Cc: Tony Krier; groff@gnu.org
Subject: Re: [Groff] need help resolving
On 09/10/13 21:24, Werner LEMBERG wrote:
>
>> He feels it may be related to fonts...
>
> I don't think so, cf Ralph's answer.
Which suggests that it may be related to mkstemp(3) usage.
>> we are more Windows knowledgeable.
>
> It would be great if you could help fix this since I don't use Wind
> He feels it may be related to fonts...
I don't think so, cf Ralph's answer.
> we are more Windows knowledgeable.
It would be great if you could help fix this since I don't use Windows
at all.
Werner
Hi charlie,
> we are more Windows knowledgeable.
Good, because I'm not and have investigated on Linux... :-)
> > grops::4:fatal error: fdopen: Invalid argument
I just did a simple
date | troff -Tps | grops >foo.ps
but with ltrace(1) monitoring grops so I could see what calls to
fdopen(3)
Invalid argument
Thanks!
-charlie
-Original Message-
From: werner.lemb...@gmx.de [mailto:werner.lemb...@gmx.de] On Behalf Of
Werner LEMBERG
Sent: Sunday, October 06, 2013 4:22 PM
To: char...@vandien.com
Cc: groff@gnu.org; t...@tonykrier.com
Subject: Re: [Groff] need help resolving gro
> grops::4:fatal error: fdopen: Invalid argument
You might follow this thread:
http://lists.gnu.org/archive/html/groff/2013-10/msg3.html
I think this covers your problem also.
Werner
Hello
I'm running this on a Windows 2008R2 Sever.
When a Perl (.PL) script runs the following line:
system("groff -Tps $output_file_name.tr > $output_file_name.ps");
I get the following error:
grops::4:fatal error: fdopen: Invalid argument
troff: fatal error: error writng output fil
19 matches
Mail list logo
