public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* <no subject>
@ 2002-06-10  2:21 Thomas Mellman
  2002-06-10  3:07 ` Syslog (was: <no subject>) Bjoern Kahl AG Resy
  0 siblings, 1 reply; 19+ messages in thread
From: Thomas Mellman @ 2002-06-10  2:21 UTC (permalink / raw)
  To: cygwin

I can't find any reference to syslogd for CYGWIN, although there is a syslog(1).
Isn't this daemon necessary to write a /var/log/messages file?

I ask because I'm still trying to get inetd to work, and I've gotten so far:

   $ telnet $(uname -n)
   Trying xxx.xxx.xxx.xxx ...
   Connected to myhost.domain
   Escape character is '^]'.
   Connection closed by foreign host.

and I wanted to try to enable debugging for telnetd in /etc/inet.conf, but I can't
make out where it might be going to.

-- 

----------------
Thomas Mellman
thomas@mellman.net
______________________________________________________________________________
All inclusive! 100 MB Speicher, SMS 50% gunstiger, 32 MB Attachment-Gro?e, 
Preisvorteile und mehr unter http://club.web.de/?mc=021104


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Syslog (was: <no subject>)
  2002-06-10  2:21 <no subject> Thomas Mellman
@ 2002-06-10  3:07 ` Bjoern Kahl AG Resy
  2002-06-10  3:25   ` Tony Arnold
  0 siblings, 1 reply; 19+ messages in thread
From: Bjoern Kahl AG Resy @ 2002-06-10  3:07 UTC (permalink / raw)
  To: Thomas Mellman; +Cc: cygwin


 Hello!

On Mon, 10 Jun 2002, Thomas Mellman wrote:

> I can't find any reference to syslogd for CYGWIN, although there
> is a syslog(1).
> Isn't this daemon necessary to write a /var/log/messages file?

 AFAIK all syslog-messages are send to the NT-syslog-service. I
 dont know how it is named in the english version of NT, but in
 the german NT it is named "Ereignisanzeige", so probably "event-viewer"
 or some thing like that in the english versions of NT.


 Bjoern

-- 
+---------------------------------------------------------------------+
| Dipl.-Phys. Bjoern Kahl +++ AG Embedded Systems and Robotics (RESY) |
| Informatics Faculty +++ Building 48 +++ University of Kaiserslautern|
| phone: +49-631-205-2654 +++ www: http://resy.informatik.uni-kl.de   |
+---------------------------------------------------------------------+



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Syslog (was: <no subject>)
  2002-06-10  3:07 ` Syslog (was: <no subject>) Bjoern Kahl AG Resy
@ 2002-06-10  3:25   ` Tony Arnold
  2002-06-10  7:29     ` Nicholas Wourms
  2002-06-10 10:22     ` Christopher Faylor
  0 siblings, 2 replies; 19+ messages in thread
From: Tony Arnold @ 2002-06-10  3:25 UTC (permalink / raw)
  To: Bjoern Kahl AG Resy; +Cc: cygwin

Dear All,

On Mon, 10 Jun 2002, Bjoern Kahl AG Resy wrote:

> On Mon, 10 Jun 2002, Thomas Mellman wrote:
>
> > I can't find any reference to syslogd for CYGWIN, although there
> > is a syslog(1).
> > Isn't this daemon necessary to write a /var/log/messages file?
>
>  AFAIK all syslog-messages are send to the NT-syslog-service. I
>  dont know how it is named in the english version of NT, but in
>  the german NT it is named "Ereignisanzeige", so probably "event-viewer"
>  or some thing like that in the english versions of NT.

I recall a question posted by Chris Faylor some time ago asking if the
community wanted continued support for syslogd in Cygwin. As there was no
demand for it at the time, the support was dropped.

Having thought about it since, I can see some good reasons for having it:

	1) Being able to grep a log file and otherwise process it with
UNIX like tools would be a great advantage. I don't know of anyway to look
at the NT event log using non Windoze tools (and if you could, the
messages are not that friendly).

	2) The ability to send logging to a central syslog server as you
can on UNIX systems would also be useful. We currently centralise our
logging and we than analyse the log to detect attempted intrusion
patterns. extending this to Windows boxes would be very useful.

Just my 2 pen'orth.

Regards,
Tony.
-- 
Tony Arnold, Deputy to the Head of COS Division, Manchester Computing,
University of Manchester, Oxford Road, Manchester M13 9PL.
T: +44 (0)161 275 6093, F: +44 (0)870 136 1004, M: +44 (0)773 330 0039
E-mail: tony.arnold@man.ac.uk, Home: http://www.man.ac.uk/Tony.Arnold


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Syslog (was: <no subject>)
  2002-06-10  3:25   ` Tony Arnold
@ 2002-06-10  7:29     ` Nicholas Wourms
  2002-06-10  7:41       ` Corinna Vinschen
  2002-06-10 10:22     ` Christopher Faylor
  1 sibling, 1 reply; 19+ messages in thread
From: Nicholas Wourms @ 2002-06-10  7:29 UTC (permalink / raw)
  To: Tony Arnold, Bjoern Kahl AG Resy; +Cc: cygwin

--- Tony Arnold <tony.arnold@man.ac.uk> wrote:
> I recall a question posted by Chris Faylor some time ago asking if the
> community wanted continued support for syslogd in Cygwin. As there was
> no
> demand for it at the time, the support was dropped.
> 
> Having thought about it since, I can see some good reasons for having
> it:
> 
> 	1) Being able to grep a log file and otherwise process it with
> UNIX like tools would be a great advantage. I don't know of anyway to
> look
> at the NT event log using non Windoze tools (and if you could, the
> messages are not that friendly).

This would be a definite plus in that catagory!

> 
> 	2) The ability to send logging to a central syslog server as you
> can on UNIX systems would also be useful. We currently centralise our
> logging and we than analyse the log to detect attempted intrusion
> patterns. extending this to Windows boxes would be very useful.
> 

I completely agree, plus it could also allow customization of which
messages are logged and which are sent to the console.

So you have my vote for this functionality :-).

Cheers,
Nicholas

__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Syslog (was: <no subject>)
  2002-06-10  7:29     ` Nicholas Wourms
@ 2002-06-10  7:41       ` Corinna Vinschen
  2002-06-10  7:46         ` Nicholas Wourms
  0 siblings, 1 reply; 19+ messages in thread
From: Corinna Vinschen @ 2002-06-10  7:41 UTC (permalink / raw)
  To: cygwin

On Mon, Jun 10, 2002 at 05:47:18AM -0700, Nicholas Wourms wrote:
> I completely agree, plus it could also allow customization of which
> messages are logged and which are sent to the console.
> 
> So you have my vote for this functionality :-).

There's just the problem that we don't want Cygwin to rely on
a running syslogd.  syslogd isn't an integral part of the OS
(as on U*X systems) while the NT event log is.  Well, on NT.
On 9x we have the ugly syslog file workaround.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Syslog (was: <no subject>)
  2002-06-10  7:41       ` Corinna Vinschen
@ 2002-06-10  7:46         ` Nicholas Wourms
  2002-06-10  8:22           ` Corinna Vinschen
  0 siblings, 1 reply; 19+ messages in thread
From: Nicholas Wourms @ 2002-06-10  7:46 UTC (permalink / raw)
  To: cygwin


--- Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
> On Mon, Jun 10, 2002 at 05:47:18AM -0700, Nicholas Wourms wrote:
> > I completely agree, plus it could also allow customization of which
> > messages are logged and which are sent to the console.
> > 
> > So you have my vote for this functionality :-).
> 
> There's just the problem that we don't want Cygwin to rely on
> a running syslogd.  syslogd isn't an integral part of the OS
> (as on U*X systems) while the NT event log is.  Well, on NT.
> On 9x we have the ugly syslog file workaround.
> 
> Corinna
Corinna,

If you are going to emulate *n*x, you are going have to run some
processes.  Memory is cheap, and certainly the syslogd wouldn't use that
much, would it?  Also, it's not like you couldn't have the messages fall
back to the NTeventlog or Ugly-syslog, should the service not be started
or fail.  I bet it would even be possible to have syslogd pass messages to
the NT Event Log, as well.  Anyhow, the concept of running a full blown
installation of cygwin w/o any additional processes will be moot once
cygserver becomes mainstream.  IMHO, the NT Event Log is not very
extensible and, of course, is proprietary.  Just my 2 cents...

Cheers,
Nicholas

__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Syslog (was: <no subject>)
  2002-06-10  7:46         ` Nicholas Wourms
@ 2002-06-10  8:22           ` Corinna Vinschen
  0 siblings, 0 replies; 19+ messages in thread
From: Corinna Vinschen @ 2002-06-10  8:22 UTC (permalink / raw)
  To: cygwin

On Mon, Jun 10, 2002 at 06:14:10AM -0700, Nicholas Wourms wrote:
> If you are going to emulate *n*x, you are going have to run some
> processes.  Memory is cheap, and certainly the syslogd wouldn't use that
> much, would it?  Also, it's not like you couldn't have the messages fall
> back to the NTeventlog or Ugly-syslog, should the service not be started
> or fail.  I bet it would even be possible to have syslogd pass messages to
> the NT Event Log, as well.  Anyhow, the concept of running a full blown
> installation of cygwin w/o any additional processes will be moot once
> cygserver becomes mainstream.  IMHO, the NT Event Log is not very
> extensible and, of course, is proprietary.  Just my 2 cents...

Memory is obviously not a problem but:

- The base tools needed to build programs (gcc/as/ld/etc) always
  will have to run w/o starting some service.

- Even if cygserver is becoming mainstream, Cygwin will still
  have to run nicely w/o cygserver.  No base functionality
  (e. g. fork()) may require cygserver.

- The openlog/syslog calls in the kernel should work even if
  no syslogd is running.  This will become somewhat tricky
  if each call has to check the existance of a running syslogd
  to be able to fallback to event log if it's not running (The
  connection is..., well, connectionless.  Syslog is using UDP).
  Ok, that's easy to solve...

The solution if we going to utilize syslogd has to fulfill
these requirements.  Basically Cygwin is still only an emulation
layer to allow building and running POSIX applications, not
a full substitute for an OS (even if we're not *that* far away ;-)).

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Syslog (was: <no subject>)
  2002-06-10  3:25   ` Tony Arnold
  2002-06-10  7:29     ` Nicholas Wourms
@ 2002-06-10 10:22     ` Christopher Faylor
  2002-06-10 13:15       ` Tony Arnold
  1 sibling, 1 reply; 19+ messages in thread
From: Christopher Faylor @ 2002-06-10 10:22 UTC (permalink / raw)
  To: cygwin

On Mon, Jun 10, 2002 at 10:24:12AM +0100, Tony Arnold wrote:
>Dear All,
>
>On Mon, 10 Jun 2002, Bjoern Kahl AG Resy wrote:
>
>> On Mon, 10 Jun 2002, Thomas Mellman wrote:
>>
>> > I can't find any reference to syslogd for CYGWIN, although there
>> > is a syslog(1).
>> > Isn't this daemon necessary to write a /var/log/messages file?
>>
>>  AFAIK all syslog-messages are send to the NT-syslog-service. I
>>  dont know how it is named in the english version of NT, but in
>>  the german NT it is named "Ereignisanzeige", so probably "event-viewer"
>>  or some thing like that in the english versions of NT.
>
>I recall a question posted by Chris Faylor some time ago asking if the
>community wanted continued support for syslogd in Cygwin. As there was no
>demand for it at the time, the support was dropped.

Huh?  We never, AFAIK, supported syslogd.  I don't recall ever asking if the
community wanted continued support.  I might have asked if anyone had a solution
for Windows 9x, though.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Syslog (was: <no subject>)
  2002-06-10 10:22     ` Christopher Faylor
@ 2002-06-10 13:15       ` Tony Arnold
  0 siblings, 0 replies; 19+ messages in thread
From: Tony Arnold @ 2002-06-10 13:15 UTC (permalink / raw)
  To: cygwin

On Mon, 10 Jun 2002, Christopher Faylor wrote:

> >I recall a question posted by Chris Faylor some time ago asking if the
> >community wanted continued support for syslogd in Cygwin. As there was no
> >demand for it at the time, the support was dropped.
>
> Huh?  We never, AFAIK, supported syslogd.  I don't recall ever asking if the
> community wanted continued support.  I might have asked if anyone had a solution
> for Windows 9x, though.

Must be my memory playing tricks as I cannot find the message in the mail
archives. Did you ask a question about moving code to do with syslog and
syslogd from one place to another or something along those lines? It was
probably a year ago?

Regards,
Tony.
-- 
Tony Arnold, Deputy to the Head of COS Division, Manchester Computing,
University of Manchester, Oxford Road, Manchester M13 9PL.
T: +44 (0)161 275 6093, F: +44 (0)870 136 1004, M: +44 (0)773 330 0039
E-mail: tony.arnold@man.ac.uk, Home: http://www.man.ac.uk/Tony.Arnold


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: (No Subject)
  2023-02-24  3:07   ` chrstfer
@ 2023-02-24  3:11     ` Eliot Moss
  0 siblings, 0 replies; 19+ messages in thread
From: Eliot Moss @ 2023-02-24  3:11 UTC (permalink / raw)
  To: chrstfer; +Cc: cygwin

On 2/24/2023 2:07 PM, chrstfer via Cygwin wrote:
> Moss,
> 
> Have you made any major changes to your cygwin X server settings? I tried this with a fresh install of the cygwin Xserver suite, first thing i did, but was unable to get it to work.
> 
> I assume you are using Docker Desktop? Do you have it integrated with WSL?
> 
> Thanks for the quick reply! This will be my last for the night. Don't want to flood.

I was not referring to Docker at all.

My XWin.0.log contains this:

XWin :0 -multiwindow -clipboard -wgl -ac -unixkill -listen tcp -clipboard -resize -engine 1 
-emulate3buttons 100 -dpi 144

HTH - Eliot

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: (No Subject)
  2023-02-24  2:58 ` Eliot Moss
@ 2023-02-24  3:07   ` chrstfer
  2023-02-24  3:11     ` Eliot Moss
  0 siblings, 1 reply; 19+ messages in thread
From: chrstfer @ 2023-02-24  3:07 UTC (permalink / raw)
  Cc: cygwin

Moss,

Have you made any major changes to your cygwin X server settings? I tried this with a fresh install of the cygwin Xserver suite, first thing i did, but was unable to get it to work. 

I assume you are using Docker Desktop? Do you have it integrated with WSL? 

Thanks for the quick reply! This will be my last for the night. Don't want to flood.


Chris


------- Original Message -------
On Thursday, February 23rd, 2023 at 9:58 PM, Eliot Moss <moss@cs.umass.edu> wrote:


> 
> 
> On 2/24/2023 1:51 PM, chrstfer via Cygwin wrote:
> 
> > Hi all,
> > 
> > First mail, so while I'm fairly sure it's on topic please forgive me if it isn't.
> > 
> > Has anyone tried to get a docker container with an X app in it to connect to the cygwin x server?
> > 
> > When I run startxwin after starting the wslg container the cygwin Xserver comes in at address (word?) :1 rather than :0, so the two servers can recognize each other (at least to some degree). I can run a cygwin X app in a cygwin console and get an X window, and I can run a wslg app in a wsl bash instance and get an X window, each on their respective servers. But when I set the env DISPLAY in one to the X of the other, it breaks.
> > 
> > This isn't just a stupid ask for a redundant use-case, either. The cygwin X server is vastly superior to the wslg one, at least insofar as integration with the windows 10 chrome; cygwin X windows no matter the library will snap like a regular windows window will. Anything coming out of wslg, at least when it comes to gtk3 (emacs-git) and QT4 (qutebrowser), have no native window decorations and don't snap. I've also been unable to find a way to run a docker container as a single X root window (ie to run a DE inside of a container) but I bet if I could connect to the cygwin X server that'd be fairly straightforward.
> > 
> > I'll be the first to admit I don't know too much about X so is what I'm asking even possible? (I do mainly use linux, but normally X is one of those things that i dont fiddle with much)
> > 
> > UItimately/mostly I'm just fed up of being stuck in Windows windowland at work and not having emacs-git*. At least thats how i landed on this topic, but it seems to me being able to run a docker container and have it hook into a cygwin X server that's already running would be a good feature generally. Especially if it would enable me to disable WSL again.
> > 
> > (*As an aside: while I have gotten it to compile, and it runs in the console, so many tests break that I'm afraid to even try compiling it for gtk3; so a docker container of debian stable seemed a logical next step and i half-expected it to just work, to be honest, given how seamless the rest of my cygwin experience has been recently, and I would put money on these two issues being on docker/docker-desktop/wsl, given how poor wslg's integration is despite being a microsoft project)
> 
> 
> If it's of any help in understanding this, in wsl I set DISPLAY=:0
> and can start X apps that connect to the Cygwin X server. I wonder
> if there are issues trying to run two X servers at the same time ...
> 
> Best - Eliot Moss

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: (No Subject)
  2023-02-24  2:51 (No Subject) chrstfer
@ 2023-02-24  2:58 ` Eliot Moss
  2023-02-24  3:07   ` chrstfer
  0 siblings, 1 reply; 19+ messages in thread
From: Eliot Moss @ 2023-02-24  2:58 UTC (permalink / raw)
  To: chrstfer, cygwin

On 2/24/2023 1:51 PM, chrstfer via Cygwin wrote:
> Hi all,
> 
> First mail, so while I'm fairly sure it's on topic please forgive me if it isn't.
> 
> Has anyone tried to get a docker container with an X app in it to connect to the cygwin x server?
> 
> When I run startxwin after starting the wslg container the cygwin Xserver comes in at address (word?) :1 rather than :0, so the two servers can recognize each other (at least to some degree). I can run a cygwin X app in a cygwin console and get an X window, and I can run a wslg app in a wsl bash instance and get an X window, each on their respective servers. But when I set the env DISPLAY in one to the X of the other, it breaks.
> 
> This isn't just a stupid ask for a redundant use-case, either. The cygwin X server is vastly superior to the wslg one, at least insofar as integration with the windows 10 chrome; cygwin X windows no matter the library will snap like a regular windows window will. Anything coming out of wslg, at least when it comes to gtk3 (emacs-git) and QT4 (qutebrowser), have no native window decorations and don't snap. I've also been unable to find a way to run a docker container as a single X root window (ie to run a DE inside of a container) but I bet if I could connect to the cygwin X server that'd be fairly straightforward.
> 
> I'll be the first to admit I don't know too much about X so is what I'm asking even possible? (I do mainly use linux, but normally X is one of those things that i dont fiddle with much)
> 
> UItimately/mostly I'm just fed up of being stuck in Windows windowland at work and not having emacs-git*. At least thats how i landed on this topic, but it seems to me being able to run a docker container and have it hook into a cygwin X server that's already running would be a good feature generally. Especially if it would enable me to disable WSL again.
> 
> (*As an aside: while I have gotten it to compile, and it runs in the console, so many tests break that I'm afraid to even try compiling it for gtk3; so a docker container of debian stable seemed a logical next step and i half-expected it to just work, to be honest, given how seamless the rest of my cygwin experience has been recently, and I would put money on these two issues being on docker/docker-desktop/wsl, given how poor wslg's integration is despite being a microsoft project)

If it's of any help in understanding this, in wsl I set DISPLAY=:0
and can start X apps that connect to the Cygwin X server.  I wonder
if there are issues trying to run two X servers at the same time ...

Best - Eliot Moss

^ permalink raw reply	[flat|nested] 19+ messages in thread

* (No Subject)
@ 2023-02-24  2:51 chrstfer
  2023-02-24  2:58 ` Eliot Moss
  0 siblings, 1 reply; 19+ messages in thread
From: chrstfer @ 2023-02-24  2:51 UTC (permalink / raw)
  To: cygwin

[-- Attachment #1: Type: text/plain, Size: 2289 bytes --]

Hi all,

First mail, so while I'm fairly sure it's on topic please forgive me if it isn't.

Has anyone tried to get a docker container with an X app in it to connect to the cygwin x server?

When I run startxwin after starting the wslg container the cygwin Xserver comes in at address (word?) :1 rather than :0, so the two servers can recognize each other (at least to some degree). I can run a cygwin X app in a cygwin console and get an X window, and I can run a wslg app in a wsl bash instance and get an X window, each on their respective servers. But when I set the env DISPLAY in one to the X of the other, it breaks.

This isn't just a stupid ask for a redundant use-case, either. The cygwin X server is vastly superior to the wslg one, at least insofar as integration with the windows 10 chrome; cygwin X windows no matter the library will snap like a regular windows window will. Anything coming out of wslg, at least when it comes to gtk3 (emacs-git) and QT4 (qutebrowser), have no native window decorations and don't snap. I've also been unable to find a way to run a docker container as a single X root window (ie to run a DE inside of a container) but I bet if I could connect to the cygwin X server that'd be fairly straightforward.

I'll be the first to admit I don't know too much about X so is what I'm asking even possible? (I do mainly use linux, but normally X is one of those things that i dont fiddle with much)

UItimately/mostly I'm just fed up of being stuck in Windows windowland at work and not having emacs-git*. At least thats how i landed on this topic, but it seems to me being able to run a docker container and have it hook into a cygwin X server that's already running would be a good feature generally. Especially if it would enable me to disable WSL again.

(*As an aside: while I have gotten it to compile, and it runs in the console, so many tests break that I'm afraid to even try compiling it for gtk3; so a docker container of debian stable seemed a logical next step and i half-expected it to just work, to be honest, given how seamless the rest of my cygwin experience has been recently, and I would put money on these two issues being on docker/docker-desktop/wsl, given how poor wslg's integration is despite being a microsoft project)

Chris B

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: (no subject)
       [not found] <3E3A630C.9080803@yahoo.com>
@ 2003-01-31 15:19 ` Earnie Boyd
  0 siblings, 0 replies; 19+ messages in thread
From: Earnie Boyd @ 2003-01-31 15:19 UTC (permalink / raw)
  To: Matthew Aldous; +Cc: dj, cygwin, MinGW Users

> Date: Thu, 30 Jan 2003 13:37:03 -0500
> From: Christopher Faylor <cygwin@cygwin.com>
> To: Matthew Aldous <Matthew@Aldous.com>
> Cc: dj@redhat.com, cygwin@cygwin.com
> Subject: Re: mingw-runtime-2.3, w32api-2.1, uberbaum
> Message-ID: <20030130183703.GC7039@redhat.com>
> Reply-To: cygwin@cygwin.com
> Mime-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> 
> Please check out the project web page for links to available information
> and ports:  http://cygwin.com/ .
> 
> If you don't see what you need there, then the cygwin mailing list is
> the best place to make observations or get questions answered.
> Information on the mailing list is available at the project web page.
> 
> For your convenience, I've reset the Reply-To: address to point to the
> cygwin mailing list.  I've also Cc'ed this reply there.
> 

And since this has to do more with MinGW than with Cygwin, it's would be 
better discussed on the mingw-users@lists.sf.net list.  I likewise have 
redirected this there.

> On Thu, Jan 30, 2003 at 04:51:53PM +0100, Matthew Aldous wrote:
> 
>>Hi,
>>
>>I'm trying to build a cross compiled mingw build under netbsd 1.6 using the
>>uberbaum cvs sources, but am experiencing the errors below with pex-win32.c
>>
>>I'm using mingw-runtime-2.3 and w32api-2.1, and was wondering if there was
>>an obvious "try this" solution when using newlib..
>>

If you're building a MinGW of GCC then why are the newlib headers being 
included for the target binary?  Perhaps 
http://www.mingw.org/mingwfaq.shtml#faq-cross might help.

Earnie.

>>Thanks in advance,
>>
>>Matthew Aldous.
>>
>>gmake[1]: Entering directory 
>>`/home/user/uberbaum/obj.i386-pc-mingw32/i386-pc-mingw32/libiberty'
>>if [ x"" != x ]; then \
>>/home/user/uberbaum/obj.i386-pc-mingw32/gcc/xgcc 
>>-B/home/user/uberbaum/obj.i386-pc-mingw32/gcc/ -nostdinc 
>>-B/home/user/uberbaum/obj.i386-pc-mingw32/i386-pc-mingw32/newlib/ 
>>-isystem 
>>/home/user/uberbaum/obj.i386-pc-mingw32/i386-pc-mingw32/newlib/targ-include 
>>-isystem /home/user/uberbaum/newlib/libc/include 
>>-B/usr/local/i386-pc-mingw32/bin/ -B/usr/local/i386-pc-mingw32/lib/ 
>>-isystem /usr/local/i386-pc-mingw32/include 
>>-L/home/user/uberbaum/obj.i386-pc-mingw32/ld -c -DHAVE_CONFIG_H -O2 -g 
>>-O2 -I. -I../../../libiberty/../include  -W -Wall -Wtraditional 
>>-pedantic  ../../../libiberty/pex-win32.c -o pic/pex-win32.o; \
>>else true; fi
>>/home/user/uberbaum/obj.i386-pc-mingw32/gcc/xgcc 
>>-B/home/user/uberbaum/obj.i386-pc-mingw32/gcc/ -nostdinc 
>>-B/home/user/uberbaum/obj.i386-pc-mingw32/i386-pc-mingw32/newlib/ 
>>-isystem 
>>/home/user/uberbaum/obj.i386-pc-mingw32/i386-pc-mingw32/newlib/targ-include 
>>-isystem /home/user/uberbaum/newlib/libc/include 
>>-B/usr/local/i386-pc-mingw32/bin/ -B/usr/local/i386-pc-mingw32/lib/ 
>>-isystem /usr/local/i386-pc-mingw32/include 
>>-L/home/user/uberbaum/obj.i386-pc-mingw32/ld -c -DHAVE_CONFIG_H -O2 -g 
>>-O2 -I. -I../../../libiberty/../include  -W -Wall -Wtraditional 
>>-pedantic ../../../libiberty/pex-win32.c -o pex-win32.o
>>In file included from ../../../libiberty/pex-win32.c:35:
>>/usr/local/i386-pc-mingw32/include/io.h:144: error: conflicting types 
>>for `getcwd'
>>/home/user/uberbaum/newlib/libc/include/sys/unistd.h:49: error: previous 
>>declaration of `getcwd'
>>In file included from 
>>/home/user/uberbaum/newlib/libc/include/sys/fcntl.h:164,
>>               from /home/user/uberbaum/newlib/libc/include/fcntl.h:1,
>>               from ../../../libiberty/pex-win32.c:36:
>>/home/user/uberbaum/newlib/libc/include/sys/stat.h:125: error: 
>>conflicting types for `mkdir'
>>/usr/local/i386-pc-mingw32/include/io.h:145: error: previous declaration 
>>of `mkdir'
>>../../../libiberty/pex-win32.c: In function `pexecute':
>>../../../libiberty/pex-win32.c:188: error: `_spawnvp' undeclared (first 
>>use in this function)
>>../../../libiberty/pex-win32.c:188: error: (Each undeclared identifier 
>>is reported only once
>>../../../libiberty/pex-win32.c:188: error: for each function it appears in.)
>>../../../libiberty/pex-win32.c:188: error: `_spawnv' undeclared (first 
>>use in this function)
>>../../../libiberty/pex-win32.c:206: warning: assignment discards 
>>qualifiers from pointer target type
>>../../../libiberty/pex-win32.c:141: warning: unused variable `retries'
>>../../../libiberty/pex-win32.c:141: warning: unused variable 
>>`sleep_interval'
>>../../../libiberty/pex-win32.c:133: warning: unused parameter `this_pname'
>>../../../libiberty/pex-win32.c:134: warning: unused parameter `temp_base'
>>../../../libiberty/pex-win32.c: In function `pwait':
>>../../../libiberty/pex-win32.c:228: warning: implicit declaration of 
>>function `_cwait'
>>../../../libiberty/pex-win32.c:224: warning: unused parameter `flags'
>>gmake[1]: *** [pex-win32.o] Error 1
>>gmake[1]: Leaving directory 
>>`/home/user/uberbaum/obj.i386-pc-mingw32/i386-pc-mingw32/libiberty'
>>gmake: *** [all-target-libiberty] Error 2
>>
> 
> At 09:54 PM 1/30/2003, Jim Kleckner wrote:
> 
> 
>>Max Bowsher wrote:
>>
>>
>>>William A. Hoffman wrote:
>>
>>[snip]
>>
>>>>2. Failing that, it would be nice if the setup program had a button that
>>>>set all the values to Keep.   The problem is that if I want a new
>>>>package X, I have to click 20 other packages to Keep, or risk an
>>>>update of everything. There should be a way to update one single
>>>>package.   Is there a way?
>>>
>>>It's in CVS. The next snapshot will have it.
>>>Max.
>>
>>Thanks!  While you have the code in hand, would it be
>>possible to allow the setup window to be resized?
>>I'm constantly wanting to see more lines at once...
> 
> 
> 
> 
> Have you been reading the email archives?  I think I've heard 
> that request before! :-)
> 
> 
> 
> Larry Hall                              lhall@rfk.com
> RFK Partners, Inc.                      http://www.rfk.com
> 838 Washington Street                   (508) 893-9779 - RFK Office
> Holliston, MA 01746                     (508) 893-9889 - FAX
> 
> <div class="moz-text-flowed" style="font-family: -moz-fixed">
> Larry Hall (RFK Partners, Inc) wrote:
> 
> 
>>At 09:54 PM 1/30/2003, Jim Kleckner wrote:
>>
>>[snip ]
>>
>>>Thanks!  While you have the code in hand, would it be
>>>possible to allow the setup window to be resized?
>>>I'm constantly wanting to see more lines at once...
>>
>>Have you been reading the email archives?  I think I've heard 
>>that request before! :-)
> 
> 
> I see the answer here:
> http://sources.redhat.com/ml/cygwin/2002-11/msg00309.html
> 
> Sorry to duplicate.  I guess every single thing needs to be searched
> before replying...
> 
> Jim
> 
> </div>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

^ permalink raw reply	[flat|nested] 19+ messages in thread

* (no subject)
  1999-02-24  2:15 Celso Labinaz
@ 1999-02-28 23:02 ` Celso Labinaz
  0 siblings, 0 replies; 19+ messages in thread
From: Celso Labinaz @ 1999-02-28 23:02 UTC (permalink / raw)
  To: gnu-win32

subscribe gnu-win32 labinaz@tin.it

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


^ permalink raw reply	[flat|nested] 19+ messages in thread

* (no subject)
@ 1999-02-24  2:15 Celso Labinaz
  1999-02-28 23:02 ` Celso Labinaz
  0 siblings, 1 reply; 19+ messages in thread
From: Celso Labinaz @ 1999-02-24  2:15 UTC (permalink / raw)
  To: gnu-win32

subscribe gnu-win32 labinaz@tin.it

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

^ permalink raw reply	[flat|nested] 19+ messages in thread

* (no subject)
@ 1998-11-19 22:52 Sch5750
  0 siblings, 0 replies; 19+ messages in thread
From: Sch5750 @ 1998-11-19 22:52 UTC (permalink / raw)
  To: gnu-win32

>Dear sirs:
>		I recently dowloaded a copy of cygwin B20. When I execute it gives me a
>warning of "cannot find /tmp,please create" I went into the read me file and
>it says to type in 'makdir -p/tmp'  (from command.com) I get an error of
>cannot create file. Am I supposed to be doing this from a dos prompt or from
>the actual bash window. I've tried both and get the same message. Any help
>would be greatly appreciated. I am in the process of trying to learn th "c"
>language and need to figure out how to get the compiler to work.

														Sincerly,
													Fred Schramm
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

^ permalink raw reply	[flat|nested] 19+ messages in thread

* (no subject)
@ 1997-05-22 19:25 Neal Feller
  0 siblings, 0 replies; 19+ messages in thread
From: Neal Feller @ 1997-05-22 19:25 UTC (permalink / raw)
  To: gnu-win32

I downloaded cdk.exe from the cygnus site and got freecell. Not what I
expected. What happened?

nfeller@ccc.isd.csc.com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

^ permalink raw reply	[flat|nested] 19+ messages in thread

* (no subject)
@ 1997-05-05 16:05 Christoph Rippel
  0 siblings, 0 replies; 19+ messages in thread
From: Christoph Rippel @ 1997-05-05 16:05 UTC (permalink / raw)
  To: gnu-win32

<HTML><BODY>


</BODY>
</HTML>
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

^ permalink raw reply	[flat|nested] 19+ messages in thread

end of thread, other threads:[~2023-02-24  3:11 UTC | newest]

Thread overview: 19+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-06-10  2:21 <no subject> Thomas Mellman
2002-06-10  3:07 ` Syslog (was: <no subject>) Bjoern Kahl AG Resy
2002-06-10  3:25   ` Tony Arnold
2002-06-10  7:29     ` Nicholas Wourms
2002-06-10  7:41       ` Corinna Vinschen
2002-06-10  7:46         ` Nicholas Wourms
2002-06-10  8:22           ` Corinna Vinschen
2002-06-10 10:22     ` Christopher Faylor
2002-06-10 13:15       ` Tony Arnold
  -- strict thread matches above, loose matches on Subject: below --
2023-02-24  2:51 (No Subject) chrstfer
2023-02-24  2:58 ` Eliot Moss
2023-02-24  3:07   ` chrstfer
2023-02-24  3:11     ` Eliot Moss
     [not found] <3E3A630C.9080803@yahoo.com>
2003-01-31 15:19 ` (no subject) Earnie Boyd
1999-02-24  2:15 Celso Labinaz
1999-02-28 23:02 ` Celso Labinaz
1998-11-19 22:52 Sch5750
1997-05-22 19:25 Neal Feller
1997-05-05 16:05 Christoph Rippel

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).