Re: was missing fonts? in cyg...@cygwin.com
Siegmar Gross wrote: I have upgraded Cygwin to X11R7.4. In the past I could read my e-mail via ssh and dtmail from a Solaris machine with a nice font. Now I I assume there are some warnings emitted by dtmail when it starts indicating that it can't use the font it wants to use? I would be interested to know exactly what it says. get a font which is about twice the size of the old one so that I get too few lines in my dtmail-window and therefore have to scroll a lot. I have already installed all available fonts from my mirror site without solving this problem. I don't know which fonts are not available in X11R7 which were available in X11R6. Does anybody know which font I need and where I can download the missing font for X11R7? [...] I installed the fonts from an older Cygwin distribution and used xset +fp /home/Admin/fonts/75dpi to prepend the old fonts to the font path. This solved my problem. Now I wanted to find out what was different. Therefore I compared /usr/share/fonts/75dpi and /usr/X11R6/lib/X11/fonts/75dpi from X11R7 and X11R6 (I had to gunzip the files first). Only the files encodings.dir were different. The old file contained an additional line ansi-1251 /usr/share/fonts/encodings/ansi-1251.enc.gz. Therefore I copied the file ansi-1251.enc.gz from X11R6 to /usr/share/fonts/encodings/ and rebuilt fonts.dir. Thanks very much for taking the time to investigate this. Yes, it appears the ansi-1251 encoding was removed upstream http://cgit.freedesktop.org/xorg/font/encodings/commit/?id=1963f4ab3ce7625ff687cbd4a94605aef86c7c03 I suspect a better solution might be to gunzip microsoft-cp1251.enc.gz, patch it as follows to identify ansi-1251 as an alias of that, gzip it again, and rebuild the encodings.dir file with mkfontdir -n diff --git a/microsoft-cp1251.enc b/microsoft-cp1251.enc index cb7720f..948f526 100644 --- a/microsoft-cp1251.enc +++ b/microsoft-cp1251.enc @@ -1,4 +1,5 @@ STARTENCODING microsoft-cp1251 +ALIAS ansi-1251 # This file is derived from data provided by the Unicode Consortium STARTMAPPING unicode 0x80 0x0402 # CYRILLIC CAPITAL LETTER DJE Unfortunately I had the same problem once more. With xset +fp /usr/share/fonts/75dpi/ I could solve my problem so that it probably depended on the font path. xset -q on the new machine displays Font Path: built-ins,/usr/share/fonts/misc/,/usr/share/fonts/TTF/, /usr/share/fonts/OTF,/usr/share/fonts/Type1/,/usr/share/fonts/100dpi/, /usr/share/fonts/75dpi/ and on the old machine Font Path: /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/TTF/, /usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/, /usr/X11R6/lib/X11/fonts/100dpi/ When I change the order of the font directories with xset -fp /usr/share/fonts/100dpi/ and xset fp+ /usr/share/fonts/100dpi/, I once more have a solution for my problem. Is there a reason why the order of the directories changed? Is it possible to switch the order of the directories back to the order of X11R6 in the distribution? I have some difficulty in working out what purpose (if any) the encodings.dir file in the various font directories serves, but you might try updating the encodings.dir file in all the font directories, not just in the encodings directory, rather than rearranging the font path. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Font issues on two different machines after update to latest xorg-server
William Deegan wrote: Yesterday and today I updated two different machines to the latest xorg-server version, on both machines, after the upgrade it could no longer find the fixed font. The issue went away after rolling back to 1.5.3-4. Attached is my cygcheck -s output. Please let me know if you need further info. Failing to find the fixed font should be impossible now as a fall-back version is built into the X server. It would be interesting to see the /var/log/XWin.0.log for 1.5.3-5 when it fails in this way. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Wmaker, massive handle leak with Xorg
The window manager Windowmaker has a massive handle leak, loosing about 50 handles per second, until the Windows kernel runs out of buffer memory (after 12 hours or so, then everything fails, socket api functions etc.) I think this is the same problem Volker Zell reported at January 11. I just updated my cygwin, so the problem is still present in the current software. I simply changed in startxwin.sh XWin -multiwindow -clipboard -silent-dup-error ... to XWin -clipboard -silent-dup-error sleep 2 wmaker sleep 2 ... With fvwm or twm i have no problems. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: was missing fonts? in cyg...@cygwin.com
Siegmar Gross wrote: I have upgraded Cygwin to X11R7.4. In the past I could read my e-mail via ssh and dtmail from a Solaris machine with a nice font. Now I I assume there are some warnings emitted by dtmail when it starts indicating that it can't use the font it wants to use? I would be interested to know exactly what it says. Yes, I get the following output on the Solaris machine. tyr fd1026 69 /usr/dt/bin/ttsession -c dtmail libSDtMail: Warning: Xt Warning: Missing charsets in String to FontSet conversion libSDtMail: Warning: Xt Warning: Cannot convert string -dt-interface user-medium-r-normal-s*-*-*-*-*-*-*-*-* to type FontSet tyr fd1026 70 I got the same output when I connected to Solaris from my older Cygwin installation with X11R6 (but with a small font in the dtmail window). It is necessary to start dtmail in this way due to a bug in Solaris or dtmail (I've forgotten which one was responsible), if you want to start dtmail via a ssh connection. I don't see any warnings in the window of my local Cygwin machine and I don't know if there is another place where I have to look for warnings from the X11 system. I have some difficulty in working out what purpose (if any) the encodings.dir file in the various font directories serves, but you might try updating the encodings.dir file in all the font directories, not just in the encodings directory, rather than rearranging the font path. When I remember right this was done automatically when I rebuilt the fonts.dir in /usr/share/fonts/75dpi/. Unfortunately I can't verify this because the Cygwin machine is at home and I'm in my office now. Kind regards Siegmar -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Cygwin/X (XWin) falls down when using -fp option
Jana Skleničková wrote: I upgraded to latest (I believe) version of Cygwin (uname -a=CYGWIN_NT-5.1 my_computer_name 1.5.25(0.156/4/2) 2008-06-12 19:34 i686 Cygwin) and after that I experience problem running XWin to a computer running Solaris OS, when font path is set to remote font server. [...] I get the login screen, I fill up login, then password (during these both steps I have hourglass cursor), then I get the initial Solaris screen and then everything disappears. All I have is the log that isn't much helpfull. I found out that the problem is caused by using the option -fp. When I don't set the -fp option everything works fine. Unfortunately I can't use local fonts because I have a problem with size of several windows at Solaris computer. I cannot change anything at Solaris computer, it's preservered, running CDE version 1.2. But it worked without problem with older version of Cygwin/X, I dind't upgraded it for quite a long time. You should probably look for log files in ~/.dt/ on the Solaris machine [1] You might also try logging into the Solaris host using ssh or telnet (using ssh -Y or setting DISPLAY to point to the cygwin X server) and opening an X client on the cygwin X server (started without using the -query XDMCP option) to check if that succeeds or fails in a similar fashion. [1] http://docs.sun.com/app/docs/doc/806-7492/troublelogin-30002?a=view -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: XWin with rootless option crashes on Vista
rincewind wrote: http://cygwin.com/faq/faq.using.html#faq.using.bloda Please try completely uninstalling the Logitech software, make sure you're running the current versions of Cygwin and X11, and try again. Your reply seems to be missing I've tried uninstalling this and the problem remains :-) Thanks for taking a look into my message. I have uploaded the relevant files (cygcheck and xwin.0.log). I am able to see some differences between the Xwin.log entries of successful (multiwindow) version and the failed (rootless) version. But perhaps they are directly related to the multiwindow and rootless options themselves. Is there a way I could obtain a stack trace of the crashing process on vista ?? [install gdb package] $ gdb --args XWin X-command-line-arguments [...] (gdb) run [...] (gdb) bt full To get something useful you'll probably want to use the unstripped binary I've made specially for you at [1] The instructions in the contributors guide [2] should clearly explain the process of building the X server from source. [1] ftp://cygwin.com/pub/cygwinx/XWin-1.5.3-5.exe.bz2 [2] http://x.cygwin.com/docs/cg/cygwin-x-cg.html -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: octave-3.0.3-1: mkoctfile error : mkoctfile seems to be unable to find liboctave
Hello --- Marco Atzeri marco_atz...@yahoo.it wrote: Thanks Tatsuro, give me few days, as I need to repack both octave-3.0.3-1 for cygwin-1.5 octave-3.0.3-2 for cygwin-1.7 OK! No problem. is anything else fine ? It seems that it is fine at the moment. Regards Tatsuro -- Power up the Internet with Yahoo! Toolbar. http://pr.mail.yahoo.co.jp/toolbar/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problems with pair key auth and sftp server
And exactly how did you do this? What were your answers to the questions? Is 'sshd' actually running now? about the answers I used ssh-host-config -y so every answer was yes. And the sshd is running. Except that it throws the error about the sftp-server. Hm, why is this? I switched the user to set up the key pair for my own user and not the local admin. As I do not want that the local admin can connect except for console. RSAAuth is activated by default. Why are you changing things here before you know the defaults work? RSAAuth was in the config as comment with a # in front. Why not use 'ssh-user-config' to create your user SSH config files with proper locations, permissions, etc.? I did use the ssh-user-config up front, forgot to mention. And it did not work afterwards. If you need anything like config or so let me know. -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Finding out login history
Marco Atzeri marco_atzeri at yahoo.it writes: OK, now I finally have 'last', there is a usage problem: mucn13154:~ 1 501 $ last last: /var/log/wtmp: No such file or directory Perhaps this file was removed by the operator to prevent logging last info. mucn13154:~ 1 503 $ ls -l /var/log total 6031 -rw-r--r-- 1 fischron mkgroup-l-d 0 Dec 16 10:31 cron.log drwxrwxrwx+ 2 SYSTEM root 0 Jan 20 15:02 exim -rwxrwxrwx+ 1 fischron mkgroup-l-d 285562 Jan 20 15:08 setup.log -rwxrwxrwx+ 1 fischron mkgroup-l-d 5889080 Jan 20 15:08 setup.log.full Seems as if I am out of luck here Ronald -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Finding out login history
--- Ronald Fischer ha scritto: Marco Atzeri writes: OK, now I finally have 'last', there is a usage problem: mucn13154:~ 1 501 $ last last: /var/log/wtmp: No such file or directory Perhaps this file was removed by the operator to prevent logging last info. mucn13154:~ 1 503 $ ls -l /var/log total 6031 -rw-r--r-- 1 fischron mkgroup-l-d 0 Dec 16 10:31 cron.log drwxrwxrwx+ 2 SYSTEM root 0 Jan 20 15:02 exim -rwxrwxrwx+ 1 fischron mkgroup-l-d 285562 Jan 20 15:08 setup.log -rwxrwxrwx+ 1 fischron mkgroup-l-d 5889080 Jan 20 15:08 setup.log.full Seems as if I am out of luck here Ronald RTFM man last NOTES The files wtmp and btmp might not be found. The system only logs infor-mation in these files if they are present. This is a local configura-tion issue. If you want the files to be used, they can be created with a simple touch(1) command (for example, touch /var/log/wtmp). Cheers from NXP Marco -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: syntax highlighting on Joe
On Tue, Jan 27, 2009 at 04:20, Larry Hall (Cygwin) wrote: Julio Emanuel wrote: snip I also would like to grab this opportunity to (once again) ring the service bell to whoever maintain this package 'joe'. It's my favorite (actually the only) editor in the Unix/Cygwin ^ Perhaps it's your only favorite editor but it is not the only editor in the Unix, Linux, or Cygwin environments, in case anyone gets the wrong immression. ;-) Hmmm. Right. Please patch MY mail :) sed -e 's/the only/MY only/g' environments, and that's unfortunate to see this package negleted, because this seems to be a simple packaging problem. Also, currently the upstream version is already 3.7 (TWO versions beyond the Cygwin current!). Could all this whining give us joe'ers a brand new version of this package? Pretty Please? :) If this really is just a packaging issue, you may have better luck reporting it to the cygwin-apps list (where packaging issues are on- topic). Jari has responded to things there of-late. Damn! And I knew it - sorry for the noise :( I'll send a new mail to the -apps with only the pertinent comments... Of course, if you're desperate for a newer 'joe' and aren't going to build it yourself, you can take advantage of the version packaged and announced here: http://cygwin.com/ml/cygwin-apps/2008-11/msg1.html I must have missed those mails somehow. It seems pretty interesting, but also shows that maybe Jari is not having enough time to handle these requests :( Of course, if you go this route, you can't come back to this list with your whining if something doesn't work. Perhaps it's a small price to pay. ;-) Small indeed. And you forgot the Do It Yourself way... If only I had a few free hours :) -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ Thanks for the help! Julio Costa -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Fwd: [Clamav-devel] Bug#512776: License incompatibility with libgmp (GPLv2 only linking to LGPLv3 or later)
David Billinghurst schrieb:
Reini Urban wrote:
Attached is a clamav license incompatibility bug with libgmp from the
debian lawyers. clamav might be forced to link against an older libgmp.
The switch to LGPL3 came with gmp-4.2.2, so gmp-4.2.1 would be needed
for clamav compatibility. But prev is gmp-4.2.3-1, so we might need a
new gmp-compat package based on gmp-4.2.1.
I can provide this if required, but I don't want to rush into it.
Some questions come to mind:
- what should it be called? gmp-compat?
- where should we install it? /opt/gmp-compat/{lib,include}
- would a static library suitable? No run time dependency,
and we won't be upgrading it.
Problem solved upstream. Thanks.
The next clamav version will use LibTomMath (bundled with
ClamAV) instead of libgmp.
--
Reini Urban
http://phpwiki.org/ http://murbreak.at/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: Vista - postgresql 8.2.11 - won't start, psql FATAL role does not exist
Keith Christian schrieb: I'd like to get PostgreSQL running on my Vista machine. I've been following the impatient instructions at the end of /usr/share/doc/Cygwin/postgresql-8.2.11.README as shown below: 1 Installation: 2 3 For the impatient: install as service (hard) hard is really hard 4 5 # save old database (optional) 6 pg_dumpall -g /tmp/$$pgdump-globals.sql 7 pg_dumpall /tmp/$$pgdump.sql 8 # adjust the settings in /etc/rc.d/init.d/postgresql 9 nano /etc/rc.d/init.d/postgresql 10 sysbash # /etc/rc.d/init.d/postgresql initdb 11 /etc/rc.d/init.d/postgresql install 12 /etc/rc.d/init.d/postgresql start Below is a screen capture showing what transpired: Tue Jan 27 06:04:36 (ke...@tycho) ~rm -rf /usr/share/postgresql/data/ ## (Line 9 above) - What settings should be adjusted in /etc/rc.d/init.d/postgresql for a starting Cygwin installation??? PGDATA, POSTMASTER_ARGS or INITDB_ARGS could be adjusted. ## (Line 10 above) - What is the meaning of sysbash? A shell running as SYSTEM user. Google for it. There's no program to do that automatically, just a trick to get root (SYSTEM user) access on windows. Tue Jan 27 06:06:04 (ke...@tycho) ~/etc/rc.d/init.d/postgresql initdb The files belonging to this database system will be owned by user keith. This user must also own the server process. So you initialized the database as user keith and not as SYSTEM. So the service must belong to use keith and not SYSTEM. The database cluster will be initialized with locale C. creating directory /usr/share/postgresql/data ... ok creating subdirectories ... ok selecting default max_connections ... 40 selecting default shared_buffers/max_fsm_pages ... 32MB/204800 creating configuration files ... ok creating template1 database in /usr/share/postgresql/data/base/1 ... ok initializing pg_authid ... ok initializing dependencies ... ok creating system views ... ok loading system objects' descriptions ... ok creating conversions ... ok setting privileges on built-in objects ... ok creating information schema ... ok vacuuming database template1 ... ok copying template1 to template0 ... ok copying template1 to postgres ... ok WARNING: enabling trust authentication for local connections You can change this by editing pg_hba.conf or using the -A option the next time you run initdb. Success. You can now start the database server using: /usr/sbin/postgres -D /usr/share/postgresql/data (A) or /usr/sbin/pg_ctl -D /usr/share/postgresql/data -l logfile start (B) done. ## Confusion here - The previous lines at the end of initdb (labeled A and B above) instruct the user to try one of two command lines to start Postgres. In the README file there are two lines following initdb, one ending with install and the other ending with start. How should the user proceed at this point? One of the three, preferred the one I gave in my instruction. sysbash # (analog to sudo SYSTEM) /etc/rc.d/init.d/postgresql initdb /etc/rc.d/init.d/postgresql install /etc/rc.d/init.d/postgresql start But only the manual way to start the database will work because you didn't install it as SYSTEM. So either A or B Tue Jan 27 06:10:26 (ke...@tycho) ~echo $CYGWIN ntsec binmode codepage:oem server tty Tue Jan 27 06:10:30 (ke...@tycho) ~/etc/rc.d/init.d/postgresql install - cygserver OK - ERROR CYGWIN must contain server for cygserver to work properly Hmm, this seems to be a script error on my side. Thanks. ## Something wrong with the error message above - CYGWIN does indeed contain server, see above ^ Tue Jan 27 06:11:30 (ke...@tycho) ~/etc/rc.d/init.d/postgresql start Starting PostgreSQL: - cygserver OK - ERROR CYGWIN must contain server for cygserver to work properly Tue Jan 27 06:11:40 (ke...@tycho) ~psql -U keith -d postgres psql: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket /tmp/.s.PGSQL.5432? *** ** SECTIONS OF POSTGRESQL'S LOGFILE APPEAR BELOW ** *** Tue Jan 27 06:13:51 (ke...@tycho) ~ls -l logfile -rw--- 1 keith None 297212 Jan 27 06:13 logfile Tue Jan 27 06:13:55 (ke...@tycho) ~cat -n logfile 1 LOG: database system was shut down at 2009-01-27 06:08:33 MST 2 LOG: checkpoint record is at 0/485AD0 3 LOG: redo record is at 0/485AD0; undo record is at 0/0; shutdown TRUE 4 LOG: next transaction ID: 0/593; next OID: 10820 5 LOG: next MultiXactId: 1; next MultiXactOffset: 0 6 LOG: database system is ready 73 [main] postgres 4352 _cygtls::handle_exceptions: Error while dumping state (probably corrupt ed stack) 821805 [main] postgres 4352
Re: Vista - postgresql 8.2.11 - won't start, psql FATAL role does not exist
On Tue, Jan 27, 2009 at 6:58 AM, Reini Urban rur...@x-ray.at wrote:
Keith Christian schrieb:
I'd like to get PostgreSQL running on my Vista machine.
I've been following the impatient instructions at the end of
/usr/share/doc/Cygwin/postgresql-8.2.11.README as shown below:
1 Installation:
2
3 For the impatient: install as service (hard)
hard is really hard
4
5 # save old database (optional)
6 pg_dumpall -g /tmp/$$pgdump-globals.sql
7 pg_dumpall /tmp/$$pgdump.sql
8 # adjust the settings in /etc/rc.d/init.d/postgresql
9 nano /etc/rc.d/init.d/postgresql
10 sysbash # /etc/rc.d/init.d/postgresql initdb
11 /etc/rc.d/init.d/postgresql install
12 /etc/rc.d/init.d/postgresql start
## (Line 9 above) - What settings should be adjusted in
/etc/rc.d/init.d/postgresql for a starting Cygwin installation???
PGDATA, POSTMASTER_ARGS or INITDB_ARGS could be adjusted.
So, on a typical Cygwin installation, would any of the three above
arguments have to be changed? I'd be accessing PostgreSQL from a
local BASH shell initially.
So your running it as keith.
Add the db and role keith.
$ createdb keith
$ createuser -S -R -d keith
Thanks, Rene - here is what I've tried so far:
1 --- The createdb keith command didn't work, so I didn't proceed
with createuser -S -R -d keith.
Tue Jan 27 06:39:59 (ke...@tycho) ~createdb keith
createdb: could not connect to database postgres: FATAL: role keith
does not exist
2 --- I found a sysbash script here:
wget http://www.cygwin.com/ml/cygwin/2003-09/msg01860/sysbash;
The sysbash script reported an error on line 40. I'll see if there is
an updated version somewhere. The one downloaded with wget has a
datestamp of Sep. 30, 2003.
Tue Jan 27 07:09:30 (ke...@tycho) ~./sysbash
./sysbash: line 40: 09: value too great for base (error token is 09)
Warning: Due to security enhancements, this task will run at the time
expected but not interactively.
Use schtasks.exe utility if interactive task is required ('schtasks /?'
for details).
Added a new job with job ID = 1
Status ID Day Time Command Line
---
1 Tomorrow7:09 AM cmd /c
C:\cygwin\bin\bash --login -i
at id-number /delete # - this will remove a badly set job
I know that you didn't write the sysbash script, it's unclear how to
access the SYSTEM session that's supposed to run.
Thanks for your assistance, I'll resume this tonight or tomorrow when
I have more time.
==Keith
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: [1.7] regression wrt scp?
On Mon, Jan 26, 2009 at 11:29:23AM -0500, Christopher Faylor wrote: Ok. I was pretty sure that I hadn't seen a broken pipe message at this point but I could be mistaken. That was because there wasn't really a broken pipe. I wasn't reporting EINTR correctly. This should be fixed in CVS and is in the latest snapshot. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: syntax highlighting on Joe
It worked! You can check it right here: http://www.cygwin.com/ml/cygwin/2008-07/msg00277.html -- Javier Sedano javier.sed...@gmail.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
permission problems with ssh-host-config
Hi, I have installed Cygwin on Windows XP SP3 (NTFS) with the latest patches. When I tried to configure secure shell I got the following errors. $ /usr/bin/ssh-host-config *** Info: Generating /etc/ssh_host_key *** Info: Generating /etc/ssh_host_rsa_key *** Info: Generating /etc/ssh_host_dsa_key *** Info: Creating default /etc/ssh_config file *** Info: Creating default /etc/sshd_config file *** Info: Privilege separation is set to yes by default since OpenSSH 3.3. *** Info: However, this requires a non-privileged account called 'sshd'. *** Info: For more info on privilege separation read /usr/share/doc/openssh/README.privsep. *** Query: Should privilege separation be used? (yes/no) yes *** Warning: The file /etc/passwd is not readable by all. *** Warning: Please run 'chmod +r /etc/passwd'. *** Warning: The file /etc/group is not readable by all. *** Warning: Please run 'chmod +r /etc/group'. *** ERROR: Problem with LocalSystem or Adminstrator IDs $ chmod +r /etc/passwd $ chmod +r /etc/group $ /usr/bin/ssh-host-config *** Query: Overwrite existing /etc/ssh_config file? (yes/no) yes *** Info: Creating default /etc/ssh_config file *** Query: Overwrite existing /etc/sshd_config file? (yes/no) yes *** Info: Creating default /etc/sshd_config file *** Info: Privilege separation is set to yes by default since OpenSSH 3.3. *** Info: However, this requires a non-privileged account called 'sshd'. *** Info: For more info on privilege separation read /usr/share/doc/openssh/README.privsep. *** Query: Should privilege separation be used? (yes/no) yes *** Warning: The permissions on the directory /var are not correct. *** Warning: They must match the regexp d..x..x..[xt] *** ERROR: Problem with /var directory. Exiting. $ chmod 755 /var $ /usr/bin/ssh-host-config *** Query: Overwrite existing /etc/ssh_config file? (yes/no) yes *** Info: Creating default /etc/ssh_config file *** Query: Overwrite existing /etc/sshd_config file? (yes/no) yes *** Info: Creating default /etc/sshd_config file *** Info: Privilege separation is set to yes by default since OpenSSH 3.3. *** Info: However, this requires a non-privileged account called 'sshd'. *** Info: For more info on privilege separation read /usr/share/doc/openssh/README.privsep. *** Query: Should privilege separation be used? (yes/no) yes *** Info: Note that creating a new user requires that the current account have *** Info: Administrator privileges. Should this script attempt to create a *** Query: new local account 'sshd'? (yes/no) yes *** Info: Updating /etc/sshd_config file *** Info: Added ssh to C:\WINDOWS\system32\driversc\services *** Warning: The following functions require administrator privileges! *** Query: Do you want to install sshd as a service? *** Query: (Say no if it is already installed as a service) (yes/no) yes *** Info: Note that the CYGWIN variable must contain at least ntsec *** Info: for sshd to be able to change user context without password. *** Query: Enter the value of CYGWIN for the daemon: [ntsec] ntsec tty server *** ERROR: Only [no] check_case:strict ntsec smbntsec traverse allowed. *** Query: Enter the value of CYGWIN for the daemon: [ntsec] ntsec *** Info: The sshd service has been installed under the LocalSystem *** Info: account (also known as SYSTEM). To start the service now, call *** Info: `net start sshd' or `cygrunsrv -S sshd'. Otherwise, it *** Info: will start automatically after the next reboot. *** Info: Host configuration finished. Have fun! Why doesn't the script allow the values ntsec tty server for CYGWIN any longer although cygserver needs server in CYGWIN? Nevertheless after rebooting the values are once more ntsec tty server from the Windows environment. Can somebody fix the permissions problem in the distribution? Thank you very much for your help in advance. Kind regards Siegmar -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: permission problems with ssh-host-config
On Tue, Jan 27, 2009 at 07:35:44PM +0100, Siegmar Gross wrote: Why doesn't the script allow the values ntsec tty server for CYGWIN any longer although cygserver needs server in CYGWIN? Presumably because sshd doesn't need server and it certainly doesn't need tty. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problems with pair key auth and sftp server
Benjamin, Please try to keep the quoting format. It makes it easier to follow the discussion and pick out your replies to my questions. Also, it is preferable to reply to the messages as this maintains the message threading. Benjamin Stössel wrote: And exactly how did you do this? What were your answers to the questions? Is 'sshd' actually running now? about the answers I used ssh-host-config -y so every answer was yes. And the sshd is running. Except that it throws the error about the sftp-server. Unless you had the foresight to answer 'sshd-server' when asked for a user name for the service, this won't work for you. I recommend you rerun 'ssh-host-config' without the '-y' and just answer the questions. You can just take the defaults. Hm, why is this? I switched the user to set up the key pair for my own user and not the local admin. As I do not want that the local admin can connect except for console. I'd recommend working with a local user first. RSAAuth is activated by default. Why are you changing things here before you know the defaults work? RSAAuth was in the config as comment with a # in front. That means the setting that's in the comment is the default. Why not use 'ssh-user-config' to create your user SSH config files with proper locations, permissions, etc.? I did use the ssh-user-config up front, forgot to mention. And it did not work afterwards. That's where we want to start looking at the problem then. You should reinstate things as you had them, though using a local user, and we can proceed from there, assuming changing the user running the service to 'sshd-server' doesn't resolve your problems. If you need anything like config or so let me know. I've already asked for this information: We're really going to need to know what you're doing exactly and what your configuration is: http://cygwin.com/problems.html And in case this also was glossed over: I'd really recommend using the existing utilities for configuring 'sshd' and 'ssh' and testing out your new configuration with 'ssh'. This may not be as you want it or the exact interface you're looking for but it will help narrow down the myriad of possibilities. I'd also recommend looking at the email archives for others who may have had similar issues to what you're experiencing. There's allot of OpenSSH discussion and help there. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Can't compile Screen: Undefined reference to __imp__ospeed
Installing screen-4.0.3-1 /usr/src/screen-4.0.3-1/src/screen-4.0.3/etc/mkinstalldirs /usr/src/screen-4.0.3-1/inst/usr/bin /usr/src/screen-4.0.3-1/inst`sed config.h -n -e '/define SCREENENCODINGS/s/^.*\([^]*\)/\1/p'` /usr/bin/install -c screen /usr/src/screen-4.0.3-1/inst/usr/bin/screen /usr/bin/install: cannot create regular file `/usr/src/screen-4.0.3-1/inst/usr/bin/screen.exe': No such file or directory I'm not sure why this step fails. It seems that either screen.exe or its installation directory, /usr/src/screen-4.0.3-1/inst/usr/bin, haven't been created as they should have been. I just ran this without any trouble, with --enable-colors256. However, I'm not quite sure how to test that option. Can you please give my packages a try? If they work for you, and especially the 256-color support, let me know and I'll release them to the repository. # for Cygwin 1.5: http://home.comcast.net/~andrex2/cygwin-1.5/screen/screen-4.0.3-3.tar.bz2 http://home.comcast.net/~andrex2/cygwin-1.5/screen/screen-4.0.3-3-src.tar.bz2 # for Cygwin 1.7: http://home.comcast.net/~andrex2/cygwin-1.7/screen/screen-4.0.3-4.tar.bz2 http://home.comcast.net/~andrex2/cygwin-1.7/screen/screen-4.0.3-4-src.tar.bz2 Once you've downloaded the binary package, kill all of your screen sessions, run e.g. tar -C/ -xf screen-4.0.3-3.tar.bz2 and then restart screen as usual to test. It would also be helpful if you would give a brief description for the release announcement, of what that option does and how to use it. Andrew. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: cygrunsrv autossh - tunnel does not come up
I have problems running autossh via cygrunsrv on WIN2003: /bin/cygrunsrv.exe -I AutoSSH -p /bin/autossh -a -M 2 -g2CN -R 20120:localhost:3389 -i /etc/key-rsa -p 20012 u...@192.168.100.12 -e AUTOSSH_NTSERVICE=yes -y tcpip --type auto As soon as I start the service (net start autossh) it stops. So it looks like it never came up: Autossh.log: 2009/01/08 23:26:25 autossh[10148]: starting ssh (count 1) 2009/01/08 23:26:25 autossh[10148]: ssh child pid is 9528 Host key verification failed. 2009/01/08 23:26:25 autossh[10148]: ssh exited prematurely with status 255; autossh exiting Running just ssh or autossh the tunnel comes up and stays: ssh: ssh -v -g2CN -R 20120:localhost:3389 -i /etc/key-rsa -p 20012 u...@192.168.100.12 autossh: /bin/autossh -M 2 -g2CN -R 20120:localhost:3389 -i /etc/key-rsa -p 20012 u...@192.168.100.12 There's a big difference between running it as a service like you did, and running it as a user. ... I have no idea to use a different user on cygwin than my windows domain root. Should I just edit the /etc/passwd and create a new user pointing to a new cygwin_home - /home/new-user? So I keep trying it with the my dom-root account. ... A good way to get more information about why the service fails to start would be to add -v or -vv to the ssh flags (within the argument of -a). okieh; I did the connection using -v with ssh and autossh. Looking to both outputs I see a big difference ssh: bash-3.2$ ssh -v -i /etc/ssh/tu_LAN2DMZ_rsa -g -2C -N -R 20120:localhost:3389 -p 20012 u...@192.168.100.12 OpenSSH_5.1p1, OpenSSL 0.9.8j 07 Jan 2009 debug1: Reading configuration data /home/root/.ssh/config debug1: Reading configuration data /etc/ssh_config debug1: Connecting to 192.168.100.12 [192.168.100.12] port 20012. debug1: Connection established. debug1: identity file /etc/ssh/tu_LAN2DMZ_rsa type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_4.2 debug1: match: OpenSSH_4.2 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-cbc hmac-md5 z...@openssh.com debug1: kex: client-server aes128-cbc hmac-md5 z...@openssh.com debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host '[192.168.100.12]:20012' is known and matches the RSA host key. debug1: Found key in /home/root/.ssh/known_hosts:1 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: /etc/ssh/tu_LAN2DMZ_rsa debug1: read PEM private key done: type RSA debug1: Enabling compression at level 6. debug1: Authentication succeeded (publickey). debug1: Remote connections from LOCALHOST:20120 forwarded to local address local host:3389 debug1: Requesting no-more-sessi...@openssh.com debug1: Entering interactive session. debug1: remote forward success for: listen 20120, connect localhost:3389 debug1: All remote forwarding requests processed autossh: bash-3.2$ /bin/cygrunsrv.exe -I AutoSSH -p /bin/autossh -a -v -M 2 -g2CN -R 20120:localhost:3389 -i /etc/ssh/tu_LAN2DMZ_rsa -p 20012 u...@192.168.100.12 -e AUTOSSH_NTSERVICE=yes -y tcpip --type auto 2009/01/27 22:22:35 autossh[4876]: starting ssh (count 1) 2009/01/27 22:22:35 autossh[4876]: ssh child pid is 5028 OpenSSH_5.1p1, OpenSSL 0.9.8j 07 Jan 2009 debug1: Reading configuration data /etc/ssh_config debug1: Connecting to 192.168.100.12 [192.168.100.12] port 20012. debug1: Connection established. debug1: identity file /etc/ssh/tu_LAN2DMZ_rsa type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_4.2 debug1: match: OpenSSH_4.2 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-cbc hmac-md5 z...@openssh.com debug1: kex: client-server aes128-cbc hmac-md5 z...@openssh.com debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: checking without port identifier debug1: read_passphrase: can't open /dev/tty: No such device or address debug1: permanently_drop_suid: 18 ssh_askpass: exec(/usr/sbin/ssh-askpass): No such file or directory Host key verification failed. 2009/01/27 22:22:36 autossh[4876]: ssh exited prematurely with status 255; autossh exiting After the connection is established somehow the autossh
Re: editing crontab using gvim
On Tue, Jan 27 2009, Shai wrote: On Tue, Jan 29, 2008 at 9:42 PM, Toby Allsopp x...@xxx wrote: Please don't quote email addresses on this list. See http://www.cygwin.com/acronyms/#PCYMTNQREAIYR. Also, if you'd waited two more days it would have been a bit funnier. On Tue, Jan 29 2008, Shai wrote: Hi, I have gvim installed and when I do: $ crontab -e gvim opens up my crontab. But, it opens it as readonly and saving it requires wq! but then when it exits, I see: $ crontab.exe -e crontab: no changes made to crontab EDITOR=gvim -f Without the -f, gvim runs in the background and crontab see it exit immediately without making any changes. Regards, Toby. Hi Toby, If I use your method, I get this when I try and save the file in gvim: E45: 'readonly' option is set (add ! to override) I'm guessing this probably has something to do with permissions in /tmp. I suggest you read the User's Guide and FAQ and look into it. Toby. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: [1.7] regression wrt scp?
Christopher Faylor wrote: This should be fixed in CVS and is in the latest snapshot. Confirmed that CVS fixes this problem for me. Thanks! -- Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RFD: cygwin + *native* MinGW compiler
Pursuant to a discussion on the libtool list, I'm trying to get a feel for how many cygwin users rely on the cygwin environment to drive the *native* MinGW gcc compiler. That is, incantations like this: 1a) cygwin$ some-src-pkg/configure \ --build=i686-pc-cygwin --host=mingw32 \ CC=/c/MinGW/bin/gcc.exe \ CXX=/c/MinGW/bin/g++.exe \ NM=/c/MinGW/bin/nm.exe \ DLLTOOL=/c/MinGW/bin/dlltool.exe \ OBJDUMP=/c/MinGW/bin/objdump.exe \ LD=/c/MinGW/bin/ld.exe or possibly 1b) cygwin$ export PATH=/c/MinGW/bin:$PATH cygwin$ some-src-pkg/configure \ --build=i686-pc-cygwin --host=mingw32 Note that this is *DIFFERENT* than installing a true cygwin-hosted mingw-target cross-compiler, and just doing 2) cygwin$ some-src-pkg/configure \ --build=i686-pc-cygwin --host=i686-pc-mingw32 It is ALSO different than the (deprecated, unsupported, go-away-don't-bother-us) incantation: 3) cygwin$ some-src-pkg/configure \ --build=i686-pc-cygwin --host=i686-pc-mingw32 \ CFLAGS='-mno-cygwin' I hope this is considered on-topic here, because I'm interested in the uses of the cygwin environment itself. I don't want reports of why it doesn't work, or how hard it is to get one of the incantations above to work. I just want to get an idea of how many people are currently, actually, successfully, doing something like 1a) or 1b) above. -- Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: RFD: cygwin + *native* MinGW compiler
On Tue, Jan 27, 2009 at 09:21:59PM -0500, Charles Wilson wrote: I hope this is considered on-topic here, because I'm interested in the uses of the cygwin environment itself. It's certainly on-topic. I'd be interested in the responses too. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: RFD: cygwin + *native* MinGW compiler
Charles Wilson wrote: Pursuant to a discussion on the libtool list, I'm trying to get a feel for how many cygwin users rely on the cygwin environment to drive the *native* MinGW gcc compiler. I do half of what you're asking: use Cygwin's bash shell as an environment to drive mingw32-make on MinGW-specific Makefiles. I posted here how I manage the PATH issues and such that you touch on: http://www.cygwin.com/ml/cygwin/2008-05/msg00092.html I do this only for MySQL++, a library I maintain, which targets MinGW among many other platforms. I use the MinGW sub-environment described above only as long as I need to do some test or fix for MinGW, then pop back out into a normal Cygwin environment. MySQL++ uses Bakefile to build the MinGW makefile, however, so I don't know how relevant my experience is to you. Bakefile more or less replaces libtool and automake, allowing easier porting to non-POSIX platforms. Thus, my use of Cygwin to drive the MinGW toolchain is limited to using bash as an alternative to the MinGW Prompt you get on installing MinGW. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: RFD: cygwin + *native* MinGW compiler
On 2009-01-28 02:21Z, Charles Wilson wrote: Pursuant to a discussion on the libtool list, I'm trying to get a feel for how many cygwin users rely on the cygwin environment to drive the *native* MinGW gcc compiler. I use the native MinGW compiler in a Cygwin environment, successfully, many hours every day. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: RFD: cygwin + *native* MinGW compiler
Greg Chicares wrote: On 2009-01-28 02:21Z, Charles Wilson wrote: Pursuant to a discussion on the libtool list, I'm trying to get a feel for how many cygwin users rely on the cygwin environment to drive the *native* MinGW gcc compiler. I use the native MinGW compiler in a Cygwin environment, successfully, many hours every day. A few additional questions, then: Do you use gnu-style configured projects (autoconf, automake, libtool, all that?) -- or some other build framework? Do you use cygwin's make (which version?), mingw32-make, or perhaps a cygwin build of msys's csmake/cpmake? Do you use gcc's -M* options for generating dependencies -- with mingw-gcc, these rules will be in dos format and cygwin-make-3.81 doesn't grok them? What about creating static libraries? If you use mingw's ar.exe, do you use explicit `cygpath` rules to convert unix paths to the DOS paths that version of ar can understand, or some other technique? For a hint about why I started this thread, and why I am asking these questions, see http://lists.gnu.org/archive/html/libtool-patches/2009-01/msg00163.html -- especially my failures with $ export PATH=/c/MinGW/bin:$PATH $ ../libtool/configure --build=i686-pc-cygwin --host=mingw32 This led to a suggestion that --build=cygwin --host=mingw32 should always be interpreted as: mingw32-gcc is a cygwin-hosted cross compiler, NOT the native MinGW-project supported gcc (and if it IS the native MinGW one, expect breakage). I'm not sure such a sweeping statement is accurate, or wise -- will that assumption break people's exising (working) setups? -- Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: RFD: cygwin + *native* MinGW compiler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Charles Wilson wrote: This led to a suggestion that --build=cygwin --host=mingw32 should always be interpreted as: mingw32-gcc is a cygwin-hosted cross compiler, NOT the native MinGW-project supported gcc (and if it IS the native MinGW one, expect breakage). I'm not sure such a sweeping statement is accurate, or wise -- will that assumption break people's exising (working) setups? If you're talking about configure gcc with those flags, then wouldn't that usually mean that you're cross-compiling a regular, native MinGW compiler? If you want a cygwin-hosted MinGW cross-compiler, you should be using --build=cygwin --host=cygwin --target=mingw32. I would be hesitant to change the usual meaning of build/host just for Cygwin/MinGW; I don't think we need to add to the confusion that most people have about Cygwin. Yaakov -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkl/99AACgkQpiWmPGlmQSPwWwCg2zTu9HT+7n9KllpstMDFMQSI 54kAoMO87bM+BuTptalxE3hHkP8uOYoU =7GVr -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Can't compile Screen: Undefined reference to __imp__ospeed
Thanks for looking at this, Andrew. I might have messed something up, but after extracting your build, I still don't get 256 colors within a Screen terminal. I'm using a Perl script, available at http://www.frexx.de/xterm-256-notes/data/256colors2.pl, to test whether my terminal is giving me 256 colors. It works when I run it from a vanilla bash prompt, but not from within Screen, even after I installed your build. Just to prove to myself that I actually did extract your (Cygwin 1.5) screen.exe properly, I checked the hash: e240a3ddc95d6ccaf08cfaa00fe3ab02 */usr/bin/screen.exe whereas the screen.exe I got online has the following hash: 005bde6eb8eca29f1fdf73efbd5a83a5 */screen.exe So...they are different. Maybe something *else* is wrong with my configuration. Thanks again for your help, Andrew. -Justin -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: RFD: cygwin + *native* MinGW compiler
Yaakov (Cygwin/X) wrote: Charles Wilson wrote: This led to a suggestion that --build=cygwin --host=mingw32 should always be interpreted as: mingw32-gcc is a cygwin-hosted cross compiler, NOT the native MinGW-project supported gcc (and if it IS the native MinGW one, expect breakage). I'm not sure such a sweeping statement is accurate, or wise -- will that assumption break people's exising (working) setups? If you're talking about configure gcc with those flags, No, I'm talking about configuring/compiling *other* stuff, using some gcc that is found via the normal rules (prefixing a triple to 'gcc' when specified by build/host/target options, looking in PATH, etc). then wouldn't that usually mean that you're cross-compiling a regular, native MinGW compiler? If you want a cygwin-hosted MinGW cross-compiler, you should be using --build=cygwin --host=cygwin --target=mingw32. Right, if I'm building a compiler. I'm not -- although that wasn't very clear, since the only examply I gave was Danny's incantation for building gcc, a compiler. Oops. I'm talking about building, say, ncurses so that it will run natively (that is, in the mingw environment without cygwin). The question is, what assumptions should be made about the compiler that is used to compile ncurses, when you configure ncurses using --build= --target=? Does that compiler understand /cygdrive/c/foo, or C:\foo? Only compilers and linkers have --targets. Everything else, you (cross)compile using build/host (or just host; build is implicit). So, the implication of the suggestion above is that: ../ncurses/configure --build=cygwin --host=mingw32 would mean that the gcc involved runs on the cygwin build platform, and understands /cygdrive/c/foo, but the ncurses library and tools will be native mingw32 and will only understand C:\foo. That is, it is a cygwin-mingw cross compiler. (Bringing this down to earth: specifically, when libtool is creating a wrapper executable -- say, for tic.exe -- using the cross-compiler, the wrapper exe will be a native win32 prog, and will need the DOS path to the exe it needs to wrap. Not the cygwin path -- and libtool should use cygpath to obtain that DOS path). OTOH, ../ncurses/configure --build=mingw32 --host=mingw32 would mean that the compiler TOO only understands C:\foo. That is, it is a native MinGW compiler as distributed by the MinGW team. (Back to earth: specifically, when libtool is creating a wrapper executable using this native compiler, the wrapper exe will be a native win32 prog, and will need the DOS path to the exe it needs to wrap. However, because of the oddities of MinGW $build -- it's actually msys, and has its own idea of a unix-like path -- libtool will need to convert that unix-like path to DOS format using the msys mechanism to do so. NOT cygpath). These are both logical scenarios, and represent the normal way of interpreting build/host for an cross-compile or native setup [other than the utter weirdness that is msys]. However...and here's the rub...until now the various win32 hosted platforms have been rather lax about these distinctions. So, for instance, Danny can currently get away with the following: cygwin-machine$ ../gcc/configure --build=mingw32 --host=ming32 --target=mingw32 even though $build is NOT, actually, mingw32 (or even msys). It's cygwin. Enforcing the normal interpretation will break that usage (Back to earth: because the wrong mechanism (msys-mingw, instead of the true cygwin-mingw) to convert unix-like paths to the DOS path needed by the wrapper exe will be used. Don't lie to your tools about their $build environment...) Maybe this usage *should* be broken (or strongly discouraged, with an esoteric workaround for those who insist on mistreating their tools). I dunno. Seems kinda harsh, to break something that currently works (even if it is evil) -- and the point of this thread, really, is to see how many people use cygwin + mingw in situations where they may be tempted to -- or already do -- lie to their configure scripts about $build. I would be hesitant to change the usual meaning of build/host just for Cygwin/MinGW; I don't think we need to add to the confusion that most people have about Cygwin. I don't think anyone is proposing that; I think the original suggestion actually enforces a more normal (e.g. like *nix/bsd/sol/etc) interpretation on the build/host/target triples. No more pretending that build=mingw32 when it's really cygwin; etc. -- Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
