Sorry, problem solved...
$ cygcheck -c libgs9
Cygwin Package Information
Package Version Status
libgs9 9.23-1 OK
$ cygcheck -l libgs9
/usr/bin/cyggs-9.dll
$ ls -l /usr/bin/cyggs-9.dll
-rwxr-xr-x 1 avenger None 11816979 Jun 29 2016 /usr/bin/cyggs-9.dll
Hello!
I got into this problem that ghostscript refuses to upgrade.
If I try to run a rtf2ps.sh I used to do frequently, I'm getting this:
Looking for the error I see somebody mentioning it should be under
/usr/share/gs/*. I have only /usr/share/ghostscript/*, and it looks like
the same. The
On Fri, 20 Jul 2018 15:35:21 +0200
João Eiras wrote:
> #include
> #include
> int main () {
> int fd = open("/dev/stdout", O_WRONLY);
> printf("Opened stdout: %d\n", fd);
> return 0;
> }
>
> Unfortunately, this freezes. The problem (I think) is because
> /dev/stdout is a pipe, so the open() call
On 7/20/2018 11:52 AM, Brian Inglis wrote:
> Are you using a terminal that does not provide a console interface?
> That is a pipe; Cygwin terms look like this:
>
On 21 July 2018 at 02:59, Heavenly Avenger wrote:
> My results match Brian Inglis', not João Eiras'. I run cygwin from a putty
> sessio
My results match Brian Inglis', not João Eiras'. I run cygwin from a
putty session (using putty's cygtermd little proxy) if that matters.
On 7/20/2018 11:52 AM, Brian Inglis wrote:
On 2018-07-20 07:17, João Eiras wrote:
$ [[ -p /dev/stdin ]] && echo pipe || echo nopipe
nopipe
Interesting, it
On 07/17/2018 08:52 PM, BloomingAzaleas wrote:
Reply to Steven Penny :
no mis-behaving: this is intended behavior - you yourself have given
workarounds: either redirect output to a file that can be later
read, or pipe to
command grouping ala {} or () and read stdin from inside the
On 2018-07-20 03:01, Mark Geisert wrote:
> renzhihao (A) wrote:
>> I am writing to apply for becoming a new cygwin mirror. The following is
>> the relevant information of our mirror.
>> HTTP: http://mirrors.huaweicloud.com/cygwin/
>> HTTPS: https://mirrors.huaweicloud.com/cygwin/
>> Bandwidth: 1000
On 2018-07-20 07:17, João Eiras wrote:
>>> $ [[ -p /dev/stdin ]] && echo pipe || echo nopipe
>>> nopipe
>
> Interesting, it's always a pipe for me. What about ls ?
>
> $ ls -l /dev/stdin
> prw--- 1 user None 0 Jun 4 15:54 /dev/stdin
Are you using a terminal that does not provide a console i
Hi.
On linux now and then I call a program passing "/dev/stdout" as output
file parameter, so the data is output in the terminal.
For instance, something tiny in C.
#include
#include
int main () {
int fd = open("/dev/stdout", O_WRONLY);
printf("Opened stdout: %d\n", fd);
return 0;
}
Unfortuna
>> $ [[ -p /dev/stdin ]] && echo pipe || echo nopipe
>> nopipe
Interesting, it's always a pipe for me. What about ls ?
$ ls -l /dev/stdin
prw--- 1 user None 0 Jun 4 15:54 /dev/stdin
>> $ [[ -t /dev/stdin ]] && echo term || echo noterm
>> noterm
The '-t' operator is used with file descripto
Hi. I see this:
$ [[ -p /dev/stdin ]] && echo pipe || echo nopipe
nopipe
$ [[ -t /dev/stdin ]] && echo term || echo noterm
noterm
Am I missing something? I tested various scenarios and stdin is never a pipe,
neither a tty for me.
--
David Macek
smime.p7s
Description: S/MIME Cryptographi
On 2018-07-20 14:01, Corinna Vinschen wrote:
On Jul 20 01:00, Houder wrote:
L.S.,
This STC fails to compile on Cygwin for x86_64:
// gcc -Wall -o stc-fenv stc-fenv.c
// Linux: gcc -Wall -o stc-fenv stc-fenv.c -lm
#define _GNU_SOURCE
#include
int main()
{
fesetenv(FE_DFL_ENV);
feseten
Hi.
I'm trying to figure out the best way to detect when my program is
being piped data.
So far I've used in linux often "[[ -p /dev/stdin ]]". During an
interactive session, /dev/stdin will be a character device, not a
pipe, and if stdin is closed ( command 0<&- ) then it's nothing.
But in cygw
On Jul 20 01:00, Houder wrote:
> L.S.,
>
> This STC fails to compile on Cygwin for x86_64:
>
> // gcc -Wall -o stc-fenv stc-fenv.c
> // Linux: gcc -Wall -o stc-fenv stc-fenv.c -lm
> #define _GNU_SOURCE
> #include
>
> int main()
> {
> fesetenv(FE_DFL_ENV);
> fesetenv(FE_NOMASK_ENV);
> }
renzhihao (A) wrote:
To whom it may concern,
I am writing to apply for becoming a new cygwin mirror. The following is the
relevant information of our mirror.
HTTP: http://mirrors.huaweicloud.com/cygwin/
HTTPS: https://mirrors.huaweicloud.com/cygwin/
Bandwidth: 1000Mbit/s
Location: Shenzhen Ci
On 2018-07-20 01:00, Houder wrote:
L.S.,
This STC fails to compile on Cygwin for x86_64:
// gcc -Wall -o stc-fenv stc-fenv.c
// Linux: gcc -Wall -o stc-fenv stc-fenv.c -lm
#define _GNU_SOURCE
#include
int main()
{
fesetenv(FE_DFL_ENV);
fesetenv(FE_NOMASK_ENV);
}
64-@@ gcc -Wall -o st
To whom it may concern,
I am writing to apply for becoming a new cygwin mirror. The following is the
relevant information of our mirror.
HTTP: http://mirrors.huaweicloud.com/cygwin/
HTTPS: https://mirrors.huaweicloud.com/cygwin/
Bandwidth: 1000Mbit/s
Location: Shenzhen City, Guangdong Province,
17 matches
Mail list logo
