RE: Anyone trying 1.5.0 for anything other than managed mode?
> From: Danilo Turina [mailto:[EMAIL PROTECTED] > > Gary R. Van Sickle wrote: > >>I've been using 1.5.0 for my large build environment since it was > >>released. No problems yet. > > > > > > Same story here, with one exception, discussed later. I > used all the latest > > [test] libs, bash, etc at work all day today, rebuilt gcc from cvs, > > re-autox-ed source trees, everything works. > > > > The exception: The "-" and "+" keys on the keypad are > giving me *two* "-"'s or > > "+"'s at the bash prompt. The "/" and "*" keys are fine, > as are the rest of the > > keypad keys, and the non-keypad "+" and "-". It's not the > new bash, since I'm > > seeing it at home too and I don't have the new bash here yet. > > I have 1.3.22 (no 1.5.0 at all) and I experience the same problem, so > it's not related to 1.5.0. Me three. Output of cygcheck -s -v attached. Ross Smith .. Pharos Systems, Auckland, New Zealand "Remember when we told you there was no future? Well, this is it." -- Blank Reg Cygwin Win95/NT Configuration Diagnostics Current System Time: Fri Jul 18 08:38:01 2003 Windows 2000 Professional Ver 5.0 Build 2195 Service Pack 3 Path: ~\bin d:\personal\projects\bin D:\cygwin\lib\qt3\bin D:\cygwin\usr\local\bin D:\cygwin\bin D:\cygwin\bin d:\Program Files\Microsoft Hardware\Keyboard\ d:\bin d:\winbin D:\cygwin\bin D:\cygwin\usr\local\bin D:\cygwin\usr\local\lib d:\Program Files\Common Files\Crystal Decisions\2.0\bin\NOTES\ d:\Program Files\Common Files\Crystal Decisions\2.0\bin\NOTES\DATA\ d:\WINNT\system32 d:\WINNT d:\WINNT\system32\WBEM d:\Program Files\Microsoft Visual Studio\Common\Tools\WinNT d:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin d:\Program Files\Microsoft Visual Studio\Common\Tools d:\Program Files\Microsoft Visual Studio\VC98\bin d:\Program Files\Microsoft Visual Studio\Common\VSS\win32 d:\Program Files\Seagate Software\NOTES\ d:\Program Files\Seagate Software\NOTES\DATA\ d:\PROGRA~1\Borland\Delphi5\Projects\Bpl d:\PROGRA~1\Borland\vbroker\jre\Bin d:\PROGRA~1\Borland\vbroker\Bin d:\PROGRA~1\Borland\Delphi5\Bin d:\PROGRA~1\Borland\Delphi6\Bin d:\PROGRA~1\Borland\Delphi6\Projects\Bpl d:\Program Files\Microsoft SQL Server\80\Tools\BINN d:\nvidia\cg\compiler\bin D:\cygwin\usr\X11R6\bin D:\cygwin\bin\id.exe output (nontsec) UID: 400(rosss) GID: 401(mkpasswd) 544(Administrators) 545(Users) 401(mkpasswd) D:\cygwin\bin\id.exe output (ntsec) UID: 400(rosss) GID: 401(mkpasswd) 544(Administrators) 545(Users) 401(mkpasswd) SysDir: D:\WINNT\System32 WinDir: D:\WINNT CYGWIN = `ntsec' C_INCLUDE_PATH = `/usr/local/include' HOME = `D:\cygwin\home\administrator' LIBRARY_PATH = `/usr/local/lib' MAKE_MODE = `unix' PWD = `/usr/bin' USER = `rosss' ALLUSERSPROFILE = `D:\Documents and Settings\All Users' APPDATA = `D:\Documents and Settings\rosss\Application Data' CG_BIN_PATH = `D:\nvidia\cg\compiler\bin' CG_INC_PATH = `D:\nvidia\cg\compiler\include' CG_LIB_PATH = `D:\nvidia\cg\compiler\lib' CI_HOLOS_CLI = `D:\Program Files\Seagate Software\Open Olap\' COLORFGBG = `default;default' COLORTERM = `rxvt-xpm' COLUMNS = `120' COMMONPROGRAMFILES = `D:\Program Files\Common Files' COMPUTERNAME = `ACHERNAR' COMSPEC = `D:\WINNT\system32\cmd.exe' CPLUS_INCLUDE_PATH = `/usr/local/include' CPUOPTS = `-march=athlon-xp -m3dnow -mmmx -msse -mno-sse2 -mfpmath=sse' DDKROOT = `d:\NTDDK' DISPLAY = `:0' HISTFILESIZE = `2000' HISTIGNORE = `&' HISTSIZE = `2000' HOMEDRIVE = `D:' HOMEPATH = `\' INCLUDE = `D:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\include\' LESS = `-iqs' LIB = `D:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\Lib\' LINES = `60' LOGONSERVER = `\\PNZSUPPORT' LS_COLORS = `di=33:ex=31' MANPATH = `:/usr/ssl/man:/usr/lib/qt3/doc/man' MSDEVDIR = `D:\Program Files\Microsoft Visual Studio\Common\MSDev98' NUMBER_OF_PROCESSORS = `1' NVSDK_MEDIA_PATH = `D:\nvidia\cg\viewer\MEDIA' OS2LIBPATH = `D:\WINNT\system32\os2\dll;' OS = `Windows_NT' PAGER = `less' PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH' PROCESSOR_ARCHITECTURE = `x86' PROCESSOR_IDENTIFIER = `x86 Family 6 Model 6 Stepping 2, AuthenticAMD' PROCESSOR_LEVEL = `6' PROCESSOR_REVISION = `0602' PROGRAMFIL
RE: ld -r errors with C++ objects
> From: Brian R. Gaeke [mailto:[EMAIL PROTECTED] > > When I link two particular .o files together into a new relocatable > (using ld -r) I get errors from ld, instead of a new .o file. This > happens in many of our C++ projects, but only on Cygwin. I have > reduced the test cases significantly. ld doesn't speak C++. Use g++ to link C++ modules. Ross Smith .. Pharos Systems, Auckland, New Zealand "Remember when we told you there was no future? Well, this is it." -- Blank Reg -- 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/
File permission problems with new cygwin dll
I just upgraded to the new cygwin dll and gcc, and I seem to be running into some of the same problems reported by others. (Yes, I know ntsec is now enabled by default.) First problem: chmod doesn't work. Whenever I try to use it, I just get "chmod: changing permissions of `foo': Invalid argument". Second problem: gcc doesn't set execute permission on the .exe files it creates. For the moment I've "solved" the problems by switching off ntsec (CYGWIN=nontsec in the system variables), so I don't urgently need a solution. I've seen other people report similar problems, but nobody has suggested a solution (at least to the ones that weren't due to simple ignorance of ntsec). -- Ross Smith .. Pharos Systems, Auckland, New Zealand This has been a test of the emergency broadcasting system. If this had been a real emergency, we would have all fled in terror, and you would not have been notified. -- 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/
RE: File permission problems with new cygwin dll
> From: Christopher Faylor [mailto:[EMAIL PROTECTED]] > > On Thu, Oct 17, 2002 at 11:09:31AM +1300, Ross Smith wrote: > >I just upgraded to the new cygwin dll and gcc, and I seem to > be running > >into some of the same problems reported by others. (Yes, I know ntsec > >is now enabled by default.) > > > >First problem: chmod doesn't work. Whenever I try to use it, > I just get > >"chmod: changing permissions of `foo': Invalid argument". > > As a guess, that would probably be an indication that your /etc/passwd > is out of sync with your Windows account. Rerunning mkpasswd > may help. Thanks. After some trial and error with the mkpasswd options, I managed to get passwd & group files that worked. However, I've had to revert to the old cygwin dll after all, because of another bug. There's some strange breakage that makes redirection with >> not work with non-cygwin programs. If you take any command-line program that writes to stdout -- plain old "hello world" will do fine -- compile it with gcc, and run it several times with >> somefile, then you get a file containing several copies of "hello world", as you'd expect. But if you compile it with Visual C++ instead, then instead of appending to the file, it just overwrites the beginning of the file every time. This just started with the new dll, so it's something to do with the changes between 1.3.12-4 and 1.3.13-2. -- Ross Smith .. Pharos Systems, Auckland, New Zealand This has been a test of the emergency broadcasting system. If this had been a real emergency, we would have all fled in terror, and you would not have been notified. -- 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/
RE: File permission problems with new cygwin dll
> From: Christopher Faylor [mailto:cgf@;redhat.com] > > On Thu, Oct 17, 2002 at 03:17:11PM +1300, Ross Smith wrote: > >If you take any command-line program that writes to stdout > -- plain old > >"hello world" will do fine -- compile it with gcc, and run it several > >times with >> somefile, then you get a file containing several copies > >of "hello world", as you'd expect. But if you compile it with Visual > >C++ instead, then instead of appending to the file, it just > overwrites > >the beginning of the file every time. > > Should be fixed in cvs. I'm generating a snapshot. > > The problem was caused by this change from Pavel Tsekov: > > http://sources.redhat.com/ml/cygwin-cvs/2002-q3/msg00064.html > > I had a nagging feeling that this was a problem when it was > checked in. > > My fix still keeps this patch but it resets file pointers > before execing > a new process. That seems to work. Thank you! -- Ross Smith .. Pharos Systems, Auckland, New Zealand This has been a test of the emergency broadcasting system. If this had been a real emergency, we would have all fled in terror, and you would not have been notified. -- 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/
RE: cygwin with opengl
> From: James Shaw [mailto:[EMAIL PROTECTED]] > > You had two postings. The most recent said: > > I cannot compile a file.c where there is the > following > > include : > GL\glut.h GL\glu.h GL\gl.h It's probably the backslashes. -- Ross Smith .. Pharos Systems, Auckland, New Zealand "I write science fiction and fantasy for a living. The science fiction is labelled 'Technical proposal', and the fantasy is labelled 'Budget estimate'." -- Jordin Kare -- 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/
RE: Mixing / and \ path separators
> From: Christopher Faylor [mailto:[EMAIL PROTECTED] > > On Wed, Mar 12, 2003 at 11:08:27PM +0100, Anton Ertl wrote: > > > >If so, how should I deal with path names where parts of the path come > >from ordinary windows users? > > Either tell your Windows users to use forward slashes, tell them to > specify the path name using windows specs like f:\cygwin\foo\bar, > or change the backslashes to slashes. Wouldn't cygwin_conv_to_posix_path() and its relatives be a more general solution? -- Ross Smith .. Pharos Systems, Auckland, New Zealand "It's never too soon to start planning, and, in fact, it's usually too late." -- Chad Orzel -- 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/
RE: Installing cygwin NOT from web
> From: Robert Collins [mailto:[EMAIL PROTECTED] > > On Fri, 2003-03-14 at 06:17, Charles D. Russell wrote: > > > Igor Pechtchanski wrote: > > > > >>FYI, setup has a "Download from Internet" mode which > creates the cache > > >>without actually installing. > > > > But as I understand it, setup.exe ignores the cache and > looks only at what > > has been actually installed. So if you don't get all the > files you want in a > > single session, and don't install, then you have problems. > > [EMAIL PROTECTED]@!!!@ > > It would be nice, for a *correct* statement not to be *incorrectly* > corrected. > > Run Setup. > Choose Download from Internet at the appropriate time. > In the 'Category' View, clikck on the word default to the > right of All. > Click again, until it shows 'reinstall'. > Now, switch to Full view, and observe that every installed package is > marked as 'retrieve'. > > Tada - one populated cache. > > Note: this will redownload everything, even if it is already in the > cache. I'm confused. Isn't that exactly what Charles said? It ignores the cache and re-downloads everything? -- Ross Smith .. Pharos Systems, Auckland, New Zealand "It's never too soon to start planning, and, in fact, it's usually too late." -- Chad Orzel -- 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/
RE: Installing cygwin NOT from web
> From: Robert Collins [mailto:[EMAIL PROTECTED] > > On Fri, 2003-03-14 at 07:59, Ross Smith wrote: > > > From: Robert Collins [mailto:[EMAIL PROTECTED] > > > > > > On Fri, 2003-03-14 at 06:17, Charles D. Russell wrote: > > > > > But as I understand it, setup.exe ignores the cache and > > > looks only at what > > > > has been actually installed. So if you don't get all the > > > files you want in a > > > > single session, and don't install, then you have problems. > ... > > > Note: this will redownload everything, even if it is > already in the > > > cache. > > > > I'm confused. Isn't that exactly what Charles said? It ignores the > > cache and re-downloads everything? > No. > Charles said that setup *ignores* the caches and skips what is > installed. > I said that setup will redownload what is in the cache. I still don't understand the difference. He says it ignores the cache and downloads it all again. You say it ignores the cache and downloads it all again. Exactly the same thing. -- Ross Smith .. Pharos Systems, Auckland, New Zealand "It's never too soon to start planning, and, in fact, it's usually too late." -- Chad Orzel -- 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/
RE: Mixing / and \ path separators
> From: Christopher Faylor [mailto:[EMAIL PROTECTED] > > On Thu, Mar 13, 2003 at 04:51:24PM -0500, Christopher Faylor wrote: > >On Fri, Mar 14, 2003 at 08:46:13AM +1300, Ross Smith wrote: > >>> From: Christopher Faylor [mailto:[EMAIL PROTECTED] > >>> > >>> On Wed, Mar 12, 2003 at 11:08:27PM +0100, Anton Ertl wrote: > >>> > > >>> >If so, how should I deal with path names where parts of > the path come > >>> >from ordinary windows users? > >>> > >>> Either tell your Windows users to use forward slashes, > tell them to > >>> specify the path name using windows specs like f:\cygwin\foo\bar, > >>> or change the backslashes to slashes. > >> > >>Wouldn't cygwin_conv_to_posix_path() and its relatives be a more > >>general solution? > > > >Good point. It probably is, if that option is available. > > I'm sorry. No. Let me take that back. > > I think what is being done is that someone is typing /usr\local/bin. > cygwin_conv_to_posix_path is not the right solution here. That would > end up creating something like /cygdrive/c/usr/local/bin which is > probably not what's intended. I should have been more explicit -- I meant applying it to the user-supplied possibly-Windows-style part of the path _before_ merging it with the program-supplied rest of the path to make an absolute path. -- Ross Smith .. Pharos Systems, Auckland, New Zealand "It's never too soon to start planning, and, in fact, it's usually too late." -- Chad Orzel -- 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/
RE: Installing cygwin NOT from web
> From: Robert Collins [mailto:[EMAIL PROTECTED] > > On Fri, 2003-03-14 at 09:10, Ross Smith wrote: > > > > No. > > > Charles said that setup *ignores* the caches and skips what is > > > installed. > > > I said that setup will redownload what is in the cache. > > > > I still don't understand the difference. He says it ignores > the cache > > and downloads it all again. You say it ignores the cache > and downloads > > it all again. Exactly the same thing. > > He says it ignores the cache and DOES NOT download it again. He said: > But as I understand it, setup.exe ignores the cache and looks only at > what has been actually installed. So if you don't get all the files > you want in a single session, and don't install, then you have > problems. That seems quite clear to me. Setup ignores what's in the cache; anything that's already in the cache but wasn't installed will be downloaded again, unnecessarily. -- Ross Smith .. Pharos Systems, Auckland, New Zealand "It's never too soon to start planning, and, in fact, it's usually too late." -- Chad Orzel -- 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/
Re: Comparative Performance of C++ Compilers (including gcc cygming special)
Alex Vinokur wrote: Three extra jobs for copyfile.cpp, g++ (Mingw32 Interface), > No optimization. ^^^ So the results are completely meaningless. -- Ross Smith .. Pharos Systems, Auckland, New Zealand *** Divide by cucumber error. Please reinstall universe and reboot. *** -- 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: undefined reference to `__gxx_personality_sj0'
> From: Dan Kyhl [mailto:[EMAIL PROTECTED]] > > yes maybe. > I installed and compiled gcc 3.03, but I get this error both > with 2.95.3 > and 3.03. > Maybe my different paths are not setup up correctly! I got the same error after installing gcc 303. It turned out that the static libstdc++ was still being searched for in /usr/lib first, so it was picking up the old one from gcc 295. I fixed it by setting the LIBRARY_PATH environment variable to /usr/local/lib, so it would search there first and find gcc 303's libstdc++ first. I don't know why it does this; gcc should search the library directory appropriate to its install prefix (/usr/local by default) first, but it doesn't seem to do that on Cygwin. I have the same setup on my Linux box (gcc 295 in /usr, 303 in /usr/local) and everything works fine there. (I originally thought it was because Linux uses a dynamic libstdc++, but some testing showed that it still worked with static libraries, so I don't know what's going on with Cygwin.) -- 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/
RE: Next version of setup.exe
> From: Robert Collins [mailto:[EMAIL PROTECTED]] > > We've branched the next version of setup.exe, and created a > snapshot for anyone willing to be our guinea pigs. > > It is accessible via > http://www.cygwin.com/setup-snapshots/setup-20020225.exe. > > Please use this, and report any bugs back to us. We know of > one with large fonts, that will be rectified shortly, but we > want to ensure that no functional bugs exist. All going well > this will be the default setup.exe by the end of the week! I just tried it and everything seems to be OK. (OS is Windows 2000.) There were a couple of minor points that may not actually be bugs but seem a little odd. One is the big blank space on the left of the first window, which looks suspiciously as though there was meant to be an image there. (Screenshot: http://storm.net.nz/~ross/temp/cygwin1.png) The other is that downloaded packages are being saved under a directory named for the download site, instead of all going into common "contrib" and "latest" directories as they used to. Was this intentional? (Screenshot: http://storm.net.nz/~ross/temp/cygwin2.png) Thanks for all your efforts! -- 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/
RE: Help changing dir with spaces- Uncle!
> From: Ehud Karni [mailto:[EMAIL PROTECTED]] > > On Wed, 27 Feb 2002 20:19:42 +0100, Jonathan Gift > <[EMAIL PROTECTED]> wrote: > > > > BTW, just how cool is Cygwin? First I heard of it was just > a short time ago. > > Really like having a great shell again? > > Cygwin is "cool"! I'm using it for more than 2 years and it made > my life much easier on M$Windows front. I port programs from UNIX > in a matter of minuets Yes, it really helps us waltz through the development process, without making a song and dance about it. (Sorry. Couldn't resist. :-) ) > and I can use (almost) all the GNU tools. > > We must all thank the small Cygwin team and the few long time > volunteers who help them. -- 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/
RE: Strange behavior
> From: Chuck Allison [mailto:[EMAIL PROTECTED]]
>
> I have a simple Rational number class and have discovered
> weird behavior
> with Cygwin's g++. If you look at the very short main program in file
> rtest2.cpp, you will see by the output that g++ get's the
> wrong answer for
>
> r1 / r2 == Rational(2,3); // should be true
>
> even though it prints as 2/3! Borland and Microsoft get it
> right. Any ideas?
> All code atached.
[relevant bit of code]
inline bool operator==(const Rational& r1, const Rational& r2)
{
return r1.toDouble() == r2.toDouble();
}
This is nothing to do with Cygwin, or g++ for that matter. You're
comparing floating point numbers. Of course it's not reliable! If
other compilers happened to give you an exact equality on that
particular combination of arguments, it was pure luck.
--
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/
RE: /cygdrive wierdness
> From: Chris January [mailto:[EMAIL PROTECTED]] > > Using Cygwin DLL 1.3.10. Likewise. (On Win2K.) > 1. Close all Cygwin programs > 2. Open bash > 3. Type: cd /cygdrive > 4. Type ls > I get a listing of C:\ instead > 5. Type bash > 6. Type: cd /cygdrive > 7. Type ls > I get a listing of available drives as I should. > > Can someone else confirm this is a problem? Not here. I get the list of drives always. -- 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/
RE: /cygdrive wierdness
> From: Chris January [mailto:[EMAIL PROTECTED]] > > > > From: Chris January [mailto:[EMAIL PROTECTED]] > > > > > > Using Cygwin DLL 1.3.10. > > > > Likewise. (On Win2K.) > > > > > 1. Close all Cygwin programs > > > 2. Open bash > > > 3. Type: cd /cygdrive > > > 4. Type ls > > > I get a listing of C:\ instead > > > 5. Type bash > > > 6. Type: cd /cygdrive > > > 7. Type ls > > > I get a listing of available drives as I should. > > > > > > Can someone else confirm this is a problem? > > > > Not here. I get the list of drives always. > Are you sure you closed all Cygwin programs? Yes. I just tried it again after rebooting to make sure. (My drive prefix is /win instead of /cygdrive, but I don't suppose that would make any difference.) -- 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/
RE: /cygdrive wierdness
> From: Larry Hall (RFK Partners, Inc) [mailto:[EMAIL PROTECTED]] > > At 05:30 PM 3/7/2002, Ross Smith wrote: > > > From: Chris January [mailto:[EMAIL PROTECTED]] > > > > > > > > From: Chris January [mailto:[EMAIL PROTECTED]] > > > > > > > > > > Using Cygwin DLL 1.3.10. > > > > > > > > Likewise. (On Win2K.) > > > > > > > > > 1. Close all Cygwin programs > > > > > 2. Open bash > > > > > 3. Type: cd /cygdrive > > > > > 4. Type ls > > > > > I get a listing of C:\ instead > > > > > 5. Type bash > > > > > 6. Type: cd /cygdrive > > > > > 7. Type ls > > > > > I get a listing of available drives as I should. > > > > > > > > > > Can someone else confirm this is a problem? > > > > > > > > Not here. I get the list of drives always. > > > Are you sure you closed all Cygwin programs? > > > >Yes. I just tried it again after rebooting to make sure. > >(My drive prefix is /win instead of /cygdrive, but I don't > >suppose that would make any difference.) > > Sorry to belabor the point but do you run any Cygwin > services? No. -- 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/
statfs() and file system types
How do I interpret the statfs.f_type field? The header says "see below" but there's nothing below. -- 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/
RE: ./config -luser32 error, but libuser32.a is in the usr/lib/w32api directory
> From: Dan Browning [mailto:[EMAIL PROTECTED]] > > At 08:56 PM 3/20/2002 -0500, you wrote: > >At 08:52 PM 3/20/2002, Dan Browning wrote: > > > > > >The "c:\cygwin\usr\lib\w32api" DOES actually exist in > windows, but I > > could not access that directory within the cygwin shell: > > > > > >$ cd /usr/lib/w32api > > >bash: cd: /usr/lib/w32api: No such file or directory > > > > > >However, if I copy "c:\cygwin\usr\lib\w32api" to > c:\cygwin\lib, then > > everything works (like what Luke said). > > > > > >So what I think we're dealing with here is, "why can't > cygwin see the > > c:\cygwin\usr\lib\w32api directory"? > > > > > >Sounds like a permissions problem to me. What does ls -l > /usr/lib/w32api > >show? > > > > $ ls -l /usr/lib/w32api > ls: /usr/lib/w32api: No such file or directory > > Perhaps it has something to do with the /usr/lib -> /lib > mounting? http://cygwin.com/faq/faq.html#SEC61 It looks as though the w32api directory has been put under the real /usr/lib (== c:\cygwin\usr\lib) instead of under the mounted directory (/usr/lib == c:\cygwin\lib) (which is where it is on my system). When the mount point is set up, this renders invisible anything actually existing under the mount-point directory. Whether this would have been caused by a setup bug or pilot error I couldn't guess. -- 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/
RE: limit for # of items created with "new" ?
From: Hans Horn [mailto:[EMAIL PROTECTED]]
>
> // an element of a linked list
> typedef struct node {
> node (int _v, node* _n) : v(_v), next(_n) {}
> int v;
> node* next;
> };
I'm surprised that compiled; the typedef shouldn't be there.
> int main (int argc, char** argv) {
> // allocate descriptions of points
> char** points = new char*[NUM_POINTS]; assert(points);
The assert is superfluous; new is guaranteed never to return null.
> for (int i = 0; i < NUM_POINTS; i++) {
> points[i] = new char[2800]; assert(points[i]);
> }
You're allocating 2800 bytes for each of 85000 entries; that's 238
megabytes so far. You said earlier that it failed when you tried it
with 1.6 million objects (which I take to mean that was the value of
NUM_POINTS). I'm not surprised; that would have tried to allocate
four and a half gigabytes of memory!
> [ lots of code snipped ]
I also recommend that you start learning about the standard library;
you're reinventing a lot of wheels here.
--
Ross Smith .. Pharos Systems, Auckland, New Zealand
"C++ is to programming as sex is to reproduction. Better ways might
technically exist but they're not nearly as much fun." - Nikolai Irgens
--
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/
RE: limit for # of items created with "new" ?
> From: Emil Briggs [mailto:[EMAIL PROTECTED]]
>
> On Tuesday 24 September 2002 10:28 pm, Ross Smith wrote:
> > From: Hans Horn [mailto:[EMAIL PROTECTED]]
> >
> > > // an element of a linked list
> > > typedef struct node {
> > > node (int _v, node* _n) : v(_v), next(_n) {}
> > > int v;
> > > node* next;
> > > };
> >
> > I'm surprised that compiled; the typedef shouldn't be there.
> >
> > > int main (int argc, char** argv) {
> > > // allocate descriptions of points
> > > char** points = new char*[NUM_POINTS]; assert(points);
> >
> > The assert is superfluous; new is guaranteed never to return null.
> >
>
> Except when you are out of memory.
No. It throws a std::bad_alloc exception.
--
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/
Small patch to opengl header
The current Cygwin GL header (/usr/include/GL/gl.h) declares the functions for the "colour subtable" GL extension, but doesn't declare the GL_EXT_color_subtable flag. This causes SDL to fail to compile (it assumes the subtable extension isn't there and tries to declare its own version). The patch is trivial: 1093a1094 > #define GL_EXT_color_subtable 1 2053a2055 > #define GL_EXT_color_subtable 1 -- Ross Smith .. Pharos Systems, Auckland, New Zealand This has been a test of the emergency broadcasting system. If this had been a real emergency, we would have all fled in terror, and you would not have been notified. -- 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/
RE: ld -r errors with C++ objects
> From: Brian R. Gaeke [mailto:[EMAIL PROTECTED] > > > > When I link two particular .o files together into a new > relocatable > > > (using ld -r) I get errors from ld, instead of a new .o file. This > > > happens in many of our C++ projects, but only on Cygwin. I have > > > reduced the test cases significantly. > > > > ld doesn't speak C++. Use g++ to link C++ modules. > > Thanks for the advice. I tried using g++ for the link step. > Ordinarily > that results in ld complaining that it can't find WinMain, which makes > sense because I am trying to link two .o files which do not constitute > an entire program. > > I tried passing the -r option to ld using g++'s -Wl,-r option, so that > it would not expect to see WinMain; that resulted in an error > very similar > to the one that I got before when I simply used ld -r. Are you using -Ur? If not, RTFM. If you are, I'm out of suggestions. Ross Smith .. Pharos Systems, Auckland, New Zealand "Remember when we told you there was no future? Well, this is it." -- Blank Reg -- 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: gcc -dM -E -xc /dev/null & g++ -dM -E -xc /dev/null
Rick Rankin wrote: --- Christopher Faylor <[EMAIL PROTECTED]> wrote: On Mon, Oct 13, 2003 at 07:22:28AM +0200, Alex Vinokur wrote: gcc -dM -E -xc /dev/null and g++ -dM -E -xc /dev/null produce the same output. Is this a feature or a bug? It is not a bug. Try it on linux. How can one know that g++ (not gcc) is invoked? Isn't the __cplusplus define a feature of c++? I'm too lazy to check if this is a g++ extension but I'd be surprised if it was. Yes, it's defined in section 16.8 (Predefined macro names) of the ANSI/ISO standard. The original poster was using the -xc flag, which tells the compiler that the following source file is to be read as C regardless of the file name. I'd expect exactly the same preprocessor output from both frontends in that case. -- Ross Smith .. Pharos Systems, Auckland, New Zealand "I virtually never go out of the house with less computing power on my person than the entire North American continent circa 1973." -- Charlie Stross -- 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: fopen with UTF-8 chars in filenames
Igor Peshansky wrote: On Fri, 17 Mar 2006, Paul J. Lucas wrote: On Fri, 17 Mar 2006, Christopher Faylor wrote: Cygwin doesn't provide _wfopen. 1. I install Cygwin. 2. It's in stdio.h that gets installed as part of the Cygwin install. No, actually it's in stdio.h that's part of MinGW (and is installed as part of Cygwin only because Cygwin's gcc has a built-in MinGW cross-compiler). Just in case anyone out there is still interested in the actual question... :) The Right Way to do this (open a file whose name is given in UTF-8), or as close to a Right Way as you can get under the circumstances, is to use iconv() to convert the file name to the local multibyte character set, and then use plain fopen() on that. In iconv_open(), use "utf-8" for the source character set, and an empty string for the target character set. (This isn't 100% portable; the Posix standard doesn't specify the character set names that can be used in iconv_open(). Every implementation understands "utf-8", but some use "char" instead of "" to mean "the local multibyte character set, whatever that happens to be".) If your file name contains characters that can't be represented in the local MBCS, you're out of luck. Cygwin only supports multibyte file names (not Cygwin's fault, it's a Posix limitation); to use the full Unicode character set in a file name you have no choice but to fall back on the Windows API. (You can use both the Windows and Cygwin APIs in the same program, that doesn't cause any problems, other than to portability.) Technically the above procedure also contains a race condition, since it's theoretically possible for the native multibyte character set to change (via the system's locale settings) between the calls to iconv() and fopen(). Again, this is a problem in the Posix API and can't be portably worked around. If you don't care about portability and just want something that works with Cygwin, you might as well just use the Windows API. -- 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: "ls" finds file1 but "ls file1" does not
Charles D. Russell wrote: Eric Blake wrote: mv -v "$f" " ` echo $f | tr A-Z a-z ` " EVIL - you are moving "FOO" to " foo " (Windows strips trailing spaces, but not leading spaces, so it is really moving to " foo"). YOU ARE ADDING SPACES to the filename. Fix your script so that there are no spaces between "` and `". _ Thought it was clever of me to make that little ` visible to my old eyes. I always use $(...) instead; it's equivalent to `...` and much easier to read. -- Ross Smith .. Pharos Systems, Auckland, New Zealand "Carelessly planned projects take three times longer to complete than expected. Carefully planned projects take four times longer to complete than expected, mostly because the planners expect their planning to reduce the time it takes." -- Anon. -- 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: make fails always on invalid path "C:cygwinusrinclude"
Patrick Graebel wrote: Where does this weird include path come from? Is there something misconfigured in my Cygwin environment? Here is the line that is printed by various makefiles: gcc: C:cygwinusrinclude: No such file or directory I'd bet that, somewhere in your setup, you've got "C:\cygwin\usr\include" where it should be either "C:\\cygwin\\usr\\include" or "C:/cygwin/usr/include". -- Ross Smith .. Pharos Systems, Auckland, New Zealand "Carelessly planned projects take three times longer to complete than expected. Carefully planned projects take four times longer to complete than expected, mostly because the planners expect their planning to reduce the time it takes." -- Anon. -- 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: Reloaded Win XP, now need to reload cygwin - sorta
Vidiot wrote: Jason reponded: The reason you need to update your permissions is because Windows ties permissions to a unique SSID for each user. When you reinstall, even if you set up the same user names, the SSIDs associated with them are different. Ah, a hidden thing I never have had to deal with. It's not a Windows specific thing. You get exactly the same effect on Unix if you install a new system and end up with a different userid number for an old user name. I wouldn't know how to change ownership permission of Windoze files, since I've never had to do it, nor have I ever seen along the lines of chown. Well, you can just use Cygwin's chown and chmod. They update Windows file ownership and permissions perfectly well. If you need to handle aspects of the Windows permission system that don't map well to the simpler Unix one, you can look into getfacl/setfacl, but if you're only trying to get the permissions right from Cygwin's point of view, that shouldn't be necessary. -- 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: Request for running a test application
Here are a few more for you: This is a USB hard drive (NTFS formatted): Device Type: 7 Characteristics: 20 Volume Name: Serial Number : 483542439 Max Filenamelength : 255 Filesystemname : Flags : 700ff FILE_CASE_SENSITIVE_SEARCH : TRUE FILE_CASE_PRESERVED_NAMES : TRUE FILE_UNICODE_ON_DISK: TRUE FILE_PERSISTENT_ACLS: TRUE FILE_FILE_COMPRESSION : TRUE FILE_VOLUME_QUOTAS : TRUE FILE_SUPPORTS_SPARSE_FILES : TRUE FILE_SUPPORTS_REPARSE_POINTS: TRUE FILE_SUPPORTS_REMOTE_STORAGE: FALSE FILE_VOLUME_IS_COMPRESSED : FALSE FILE_SUPPORTS_OBJECT_IDS: TRUE FILE_SUPPORTS_ENCRYPTION: TRUE FILE_NAMED_STREAMS : TRUE FILE_READ_ONLY_VOLUME : FALSE FILE_SEQUENTIAL_WRITE_ONCE : FALSE FILE_SUPPORTS_TRANSACTIONS : FALSE This is my iPod (Windows formatted, connected by USB): Device Type: 7 Characteristics: 121 Volume Name: Serial Number : 3926698352 Max Filenamelength : 255 Filesystemname : Flags : 6 FILE_CASE_SENSITIVE_SEARCH : FALSE FILE_CASE_PRESERVED_NAMES : TRUE FILE_UNICODE_ON_DISK: TRUE FILE_PERSISTENT_ACLS: FALSE FILE_FILE_COMPRESSION : FALSE FILE_VOLUME_QUOTAS : FALSE FILE_SUPPORTS_SPARSE_FILES : FALSE FILE_SUPPORTS_REPARSE_POINTS: FALSE FILE_SUPPORTS_REMOTE_STORAGE: FALSE FILE_VOLUME_IS_COMPRESSED : FALSE FILE_SUPPORTS_OBJECT_IDS: FALSE FILE_SUPPORTS_ENCRYPTION: FALSE FILE_NAMED_STREAMS : FALSE FILE_READ_ONLY_VOLUME : FALSE FILE_SEQUENTIAL_WRITE_ONCE : FALSE FILE_SUPPORTS_TRANSACTIONS : FALSE This is a virtual hard drive on a VMWare virtual machine, accessed via network: Device Type: 7 Characteristics: 10 Volume Name: <> Serial Number : 2966230284 Max Filenamelength : 255 Filesystemname : Flags : 2700ff FILE_CASE_SENSITIVE_SEARCH : TRUE FILE_CASE_PRESERVED_NAMES : TRUE FILE_UNICODE_ON_DISK: TRUE FILE_PERSISTENT_ACLS: TRUE FILE_FILE_COMPRESSION : TRUE FILE_VOLUME_QUOTAS : TRUE FILE_SUPPORTS_SPARSE_FILES : TRUE FILE_SUPPORTS_REPARSE_POINTS: TRUE FILE_SUPPORTS_REMOTE_STORAGE: FALSE FILE_VOLUME_IS_COMPRESSED : FALSE FILE_SUPPORTS_OBJECT_IDS: TRUE FILE_SUPPORTS_ENCRYPTION: TRUE FILE_NAMED_STREAMS : TRUE FILE_READ_ONLY_VOLUME : FALSE FILE_SEQUENTIAL_WRITE_ONCE : FALSE FILE_SUPPORTS_TRANSACTIONS : TRUE This is a CD image (.iso file) mounted with Microsoft's Virtual CDROM tool: Device Type: 2 Characteristics: 23 Volume Name: Serial Number : 2471649833 Max Filenamelength : 221 Filesystemname : Flags : 80001 FILE_CASE_SENSITIVE_SEARCH : TRUE FILE_CASE_PRESERVED_NAMES : FALSE FILE_UNICODE_ON_DISK: FALSE FILE_PERSISTENT_ACLS: FALSE FILE_FILE_COMPRESSION : FALSE FILE_VOLUME_QUOTAS : FALSE FILE_SUPPORTS_SPARSE_FILES : FALSE FILE_SUPPORTS_REPARSE_POINTS: FALSE FILE_SUPPORTS_REMOTE_STORAGE: FALSE FILE_VOLUME_IS_COMPRESSED : FALSE FILE_SUPPORTS_OBJECT_IDS: FALSE FILE_SUPPORTS_ENCRYPTION: FALSE FILE_NAMED_STREAMS : FALSE FILE_READ_ONLY_VOLUME : TRUE FILE_SEQUENTIAL_WRITE_ONCE : FALSE FILE_SUPPORTS_TRANSACTIONS : FALSE -- 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/
http://cygwin.com/ needs a link updated
Corinna, http://cygwin.com/ mentions Latest Cygwin DLL release version is 1.5.25-7 but the 1.5.25-7 link refers to the 1.5.24 release. It should point to http://cygwin.com/ml/cygwin-announce/2007-12/msg00036.html right? -Ross -- 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: long_int vs int byte sizes
On 2014-04-08 03:51, Corinna Vinschen wrote: On Apr 7 09:39, Eric Blake wrote: C99 5.2.4.2.1 Sizes of integer types requires CHAR_BIT to be 8 or larger, UCHAR_MAX to be 255 or larger, USHRT_MAX to be 65535 or larger (oh, so I was wrong above; 8-bit short is not allowed), UINT_MAX to be 65535 or larger, ULONG_MAX to be 4294967295 or larger, and ULLONG_MAX to be 18446744073709551615 or larger. C99 actually requires that? Wow. Modern times... It was already required in C89; the only change in C99 was the addition of long long. Ross Smith -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [1.7] Invalid UTF8 while creating a file -> cannot delete?
Corinna Vinschen wrote: However, if we default to UTF-8 for a subset of languages anyway, it gets even more interesting to ask, why not for all languages? Isn't it better in the long run to have the same default for all Cygwin installations? I'm really wondering if we shouldn't simply default to UTF-8 as charset throughout, in the application, the console, and for the filename conversion. Yes, not all applications will work OOTB with chars > 0x7f, but it was always a bug to make any assumptions for non-ASCII chars in the C locale. Applications can be fixed, right? In support of this plan, it occurs to me that any command line applications that don't speak UTF-8 would presumably be showing the same behaviour on Linux (e.g. odd column widths). Since one of Cygwin's main goals is providing a Linux-like environment on Windows, I don't think Cygwin developers should feel obliged to go out of their way to do _better_ than Linux in this regard. -- Ross Smith -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Directory existence prevents .exe execution
Luke, I think the fundamental point that you're missing here is that Cygwin is intended to be a subspecies of Unix, not a subspecies of Windows. I'm not familiar with Ici, but if it currently has both Windows and Unix versions, you should expect the Unix version, not the Windows version, to be appropriate for Cygwin. If it's currently Windows-only and doesn't have a Unix version, it's very unlikely to just work as a native Cygwin build without considerable effort. You should expect that porting code from Windows to Cygwin will take an effort comparable to porting it to Linux. -- 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/
Upgrading to cygwin 1.7.6 vs gcc 4.5
I've installed the experimental gcc 4.5 packages (because that's the version I'm using in all my other development environments, and it's nice not to have to target multiple compiler versions any more), but now that cygwin dll 1.7.6 is out, I can't seem to find a way to upgrade cygwin without also downgrading gcc. In the installer, if I select Current I get the new cygwin but the old gcc, while if I select Experimental, it keeps the new gcc but doesn't offer me the new cygwin. At the moment I'm sticking with the old cygwin, because the gcc upgrade is more important to me than the cygwin upgrade. Is there some way I'm missing to select both, or do I just have to accept that I can't upgrade anything else until the official gcc 4.5 is ready? -- Ross Smith -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: gcc-6.3.0-2 (x86/x86_64)(Test)
On 2017-07-28 02:49, Ken Brown wrote:
On 6/29/2017 7:16 AM, JonY wrote:
gcc-6.3.0-2 has been uploaded for Cygwin. It is marked as a test version.
JonY,
I assume you want some feedback on this.
I've been testing gcc-6.3.0-2 with binutils-2.28-3, on both x86 and
x86_64, by rebuilding several of my packages. So far I've built
texlive, emacs, and icu. There have been no problems, and all builds
have passed their test suites.
Ken
gcc 6.3 works fine for me unless I use threads. Any C++ program that
uses std::thread (and worked with the previous gcc) will fail. Simple
example:
#include
#include
void payload() {
std::cout << "Thread\n";
}
int main() {
std::cout << "Start\n";
std::thread t(payload);
t.join();
std::cout << "Done\n";
}
Build and run with:
g++ thread.cpp -o thread && ./thread || echo Fail
This will print Fail, indicating that the executable errored out.
There's no other output. Sorry, I'm not familiar enough with gcc
debugging to narrow down the error further.
Code that uses raw pthreads instead of the C++ API works fine.
(I'm running 64-bit Cygwin on Windows 8.1.)
Ross Smith
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: gcc-6.3.0-2 (x86/x86_64)(Test)
On 2017-07-28 09:19, Marco Atzeri wrote:
On 27/07/2017 23:04, Ross Smith wrote:
gcc 6.3 works fine for me unless I use threads. Any C++ program that
uses std::thread (and worked with the previous gcc) will fail. Simple
example:
#include
#include
void payload() {
std::cout << "Thread\n";
}
int main() {
std::cout << "Start\n";
std::thread t(payload);
t.join();
std::cout << "Done\n";
}
Build and run with:
g++ thread.cpp -o thread && ./thread || echo Fail
This will print Fail, indicating that the executable errored out.
There's no other output. Sorry, I'm not familiar enough with gcc
debugging to narrow down the error further.
Code that uses raw pthreads instead of the C++ API works fine.
(I'm running 64-bit Cygwin on Windows 8.1.)
Ross Smith
it works for me on W7-64
./thread || echo "fail"
Start
Thread
Done
$ g++ --version
g++ (GCC) 6.3.0
That's interesting. Maybe I have something wrong with my installation? I
updated the gcc-core, gcc-g++, and libgcc1 packages to the 6.3 test
version; was there something else I needed? (I found those by searching
the installed package list in the Cygwin installer for gcc or g++, and
seeing which ones offered the option of updating to 6.3; there doesn't
seem to be any way of checking what you actually need in a case like this.)
Ross Smith
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: gcc-6.3.0-2 (x86/x86_64)(Test)
On 2017-07-28 09:45, Ken Brown wrote:
On 7/27/2017 5:39 PM, Ross Smith wrote:
On 2017-07-28 09:19, Marco Atzeri wrote:
On 27/07/2017 23:04, Ross Smith wrote:
gcc 6.3 works fine for me unless I use threads. Any C++ program that
uses std::thread (and worked with the previous gcc) will fail. Simple
example:
#include
#include
void payload() {
std::cout << "Thread\n";
}
int main() {
std::cout << "Start\n";
std::thread t(payload);
t.join();
std::cout << "Done\n";
}
Build and run with:
g++ thread.cpp -o thread && ./thread || echo Fail
This will print Fail, indicating that the executable errored out.
There's no other output. Sorry, I'm not familiar enough with gcc
debugging to narrow down the error further.
Code that uses raw pthreads instead of the C++ API works fine.
(I'm running 64-bit Cygwin on Windows 8.1.)
Ross Smith
it works for me on W7-64
./thread || echo "fail"
Start
Thread
Done
$ g++ --version
g++ (GCC) 6.3.0
That's interesting. Maybe I have something wrong with my installation?
I updated the gcc-core, gcc-g++, and libgcc1 packages to the 6.3 test
version; was there something else I needed? (I found those by
searching the installed package list in the Cygwin installer for gcc
or g++, and seeing which ones offered the option of updating to 6.3;
there doesn't seem to be any way of checking what you actually need in
a case like this.)
Click the test button when running setup. You'll see several other
packages with versions 6.3.0-2, including libstdc++6.
Thanks! Yes, turns out I was missing some packages. Everything works
now. Sorry for the false alarm!
Ross Smith
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: gcc-7.3.0-2 (x86/x86_64)(Test)
On 2018-05-05 22:00, JonY wrote:
gcc-7.3.0-2 has been uploaded for Cygwin. This version is for testing.
Java support has been removed from upstream GCC, GCJ is no longer available.
Changes since -1:
* Enabled libstdc++ filesystem feature as requested by Nuno Lopes.
I've updated gcc-core, gcc-g++, and libstdc++ to 7.3.0-2,
but the filesystem library still doesn't seem to be working:
#include
#include
using namespace std::experimental;
int main() {
filesystem::path p("expfs.cpp");
std::cout << p.string() << " " << filesystem::exists(p) << "\n";
}
$ g++ -std=c++1z expfs.cpp -o expfs
/tmp/ccV1QAAo.o:expfs.cpp:(.text$_ZNSt12experimental10filesystem2v16existsERKNS1_4pathE[_ZNSt12experimental10filesystem2v16existsERKNS1_4pathE]+0x11):
undefined reference to
`std::experimental::filesystem::v1::status(std::experimental::filesystem::v1::path
const&)'
/tmp/ccV1QAAo.o:expfs.cpp:(.text$_ZNSt12experimental10filesystem2v16existsERKNS1_4pathE[_ZNSt12experimental10filesystem2v16existsERKNS1_4pathE]+0x11):
relocation truncated to fit: R_X86_64_PC32 against undefined symbol
`std::experimental::filesystem::v1::status(std::experimental::filesystem::v1::path
const&)'
/tmp/ccV1QAAo.o:expfs.cpp:(.text$_ZNSt12experimental10filesystem2v14pathC1IA10_cS2_EERKT_[_ZNSt12experimental10filesystem2v14pathC1IA10_cS2_EERKT_]+0x5d):
undefined reference to
`std::experimental::filesystem::v1::path::_M_split_cmpts()'
/tmp/ccV1QAAo.o:expfs.cpp:(.text$_ZNSt12experimental10filesystem2v14pathC1IA10_cS2_EERKT_[_ZNSt12experimental10filesystem2v14pathC1IA10_cS2_EERKT_]+0x5d):
relocation truncated to fit: R_X86_64_PC32 against undefined symbol
`std::experimental::filesystem::v1::path::_M_split_cmpts()'
collect2: error: ld returned 1 exit status
Ross Smith
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: GCC 7.3.0 -std=gnu++17 failed to getline() from std::ifstream
On 2018-06-06 09:00, Marco Atzeri wrote:
On 6/5/2018 10:32 PM, Ivan Shynkarenka wrote:
Hello
I use x64 bit Cygwin and it failed in my home, work and Appveyor. I add
cygcheck.out with my environment.
I'm sorry about misspell prefix space in my prev example. Please try the
following one:
#include
#include
int main(int argc, char** argv)
{
std::string line;
std::ifstream stream("test.cpp");
while (getline(stream, line))
std::cout << line << std::endl;
return 0;
}
g++ -std=gnu++17 test.cpp
works fine on 32 bit and 64 bit on my W7
I'm having the same problem. My test program:
#include
#include
int main() {
std::ifstream in("demo.cpp");
std::string line;
for (;;) {
std::getline(in, line);
if (! in && line.empty())
break;
std::cout << line << "\n";
}
}
$ g++ demo.cpp -std=c++17 -o demo && ./demo
Aborted (core dumped)
It's crashing on the call to std::getline(). It only happens in
-std=gnu++17 mode (or the equivalent gnu++1z, or c++17/1z). If I
compile with -std=gnu++14 or lower it works. I'm using 64-bit
Cygwin, everything updated to the current release, on Windows 8.1.
Ross Smith
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: GCC 7.3.0 -std=gnu++17 failed to getline() from std::ifstream
On 2018-06-12 02:17, Marco Atzeri wrote:
On 6/11/2018 4:11 AM, Ross Smith wrote:
On 2018-06-06 09:00, Marco Atzeri wrote:
On 6/5/2018 10:32 PM, Ivan Shynkarenka wrote:
Hello
I use x64 bit Cygwin and it failed in my home, work and Appveyor. I
add
cygcheck.out with my environment.
I'm sorry about misspell prefix space in my prev example. Please try
the
following one:
#include
#include
int main(int argc, char** argv)
{
std::string line;
std::ifstream stream("test.cpp");
while (getline(stream, line))
std::cout << line << std::endl;
return 0;
}
g++ -std=gnu++17 test.cpp
works fine on 32 bit and 64 bit on my W7
I'm having the same problem. My test program:
#include
#include
int main() {
std::ifstream in("demo.cpp");
with this change does not segfault
std::ifstream stream("demo.cpp\n");
It doesn't segfault because it doesn't open the file, because no file
named "demo.cpp\n" exists. I don't know WTF you thought you were doing
here.
Ross Smith
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: GCC 7.3.0 -std=gnu++17 failed to getline() from std::ifstream
On 2018-06-13 05:11, Christian Franke wrote:
Ivan Shynkarenka wrote:
I use x64 bit Cygwin and it failed in my home, work and Appveyor. I add
cygcheck.out with my environment.
I'm sorry about misspell prefix space in my prev example. Please try the
following one:
#include
#include
int main(int argc, char** argv)
{
std::string line;
std::ifstream stream("test.cpp");
while (getline(stream, line))
std::cout << line << std::endl;
return 0;
}
g++ -std=gnu++17 test.cpp
Could reproduce this with 32 and 64 bit Cygwin g++ 7.3.0
A comparison of preprocessor (-E) outputs shows that the "extern
template" declarations for getline() are only visible for C++ <= 14.
These are guarded by "__cplusplus <= 1402" in basic_string.tcc. This
should tell the compiler to generate new code for getline() if C++17 is
enabled instead of calling the (now incompatible) function in
cygstdc++-6.dll.
A comparison of assembly (-S) outputs shows that this does not work: If
C++17 is enabled, the compiler correctly generates local code for
getline(istream &, string &) but this code calls an external
getline(istream &, string &, char). Then the linker generates a call to
this getline() in cygstdc++-6.dll.
This is because there is a bogus prototype specialization for
getline(istream &, string &, char) in basic_string.h but no
corresponding implementation in basic_string.tcc. This has apparently an
equivalent effect as 'extern template'.
The attached patch for
/usr/lib/gcc/*-pc-cygwin/7.3.0/include/c++/bits/basic_string.h
fixes this.
Christian
Thank you! I can confirm that the patch fixes this.
Ross Smith
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
ssh patches to fix installation issues
Attached are three small patches to the following files:
/bin/ssh-host-config
/bin/ssh-user-config
/usr/doc/Cygwin/openssh-3.4p1-5.README
to fix some installation issues and better explain using sshd in Windows.
The ssh-user-config changes are due to the fact that the default cygwin
umask is 000. Maybe a .bash_profile could be created containing umask 022
when the user's home directory is first created. Just a thought.
This is the culmination of 6 hours of list perusing, and hair pulling, so
it's definitely "field tested".
Hope this helps,
Ross Smith
--- ssh-host-config.orig2002-07-07 03:07:12.0 -0700
+++ ssh-host-config 2002-10-23 16:11:12.0 -0700
@@ -164,6 +164,7 @@
if [ $_nt -gt 0 ]
then
chown system.system /var/empty
+chmod 755 /var/empty
fi
fi
--- ssh-user-config.orig2002-06-21 13:32:33.0 -0700
+++ ssh-user-config 2002-10-23 16:15:24.0 -0700
@@ -123,6 +123,8 @@
fi
fi
+chown `whoami` ${pwdhome}
+
if [ -e "${pwdhome}/.ssh" -a ! -d "${pwdhome}/.ssh" ]
then
echo "${pwdhome}/.ssh is existant but not a directory. Cannot create user
identity files."
@@ -139,6 +141,8 @@
fi
fi
+chmod 755 ${pwdhome}/.ssh
+
if [ ! -f "${pwdhome}/.ssh/identity" ]
then
if request "Shall I create an SSH1 RSA identity file for you?"
@@ -196,5 +200,8 @@
fi
fi
+chmod 600 ${pwdhome}/.ssh/*
+chmod 644 ${pwdhome}/.ssh/*.pub ${pwdhome}/.ssh/authorized_keys?
+
echo
echo "Configuration finished. Have fun!"
--- openssh-3.4p1-5.README.orig 2002-10-23 15:20:39.0 -0700
+++ openssh-3.4p1-5.README 2002-10-23 16:23:03.0 -0700
@@ -123,12 +123,53 @@
- If you want to authenticate via RSA and you want to login to that
machine to exactly one user account you can do so by running sshd
- under that user account. You must change /etc/sshd_config
- to contain the following:
+ under that user account.
+
+ * Change /etc/sshd_config to contain
RSAAuthentication yes
- Moreover it's possible to use rhosts and/or rhosts with
+ * Make sure you have executed the following:
+
+$ ssh-host-config
+$ ssh-user-config
+
+ * Due to the fact that cygwin's default umask is , you will need
+to execute the following (substituting your user name for USERNAME):
+
+ chown USERNAME ~
+ chmod 755 ~ ~/.ssh
+ chmod 600 ~/.ssh/*
+ chmod 644 ~/.ssh/*.pub ~/.ssh/authorized_keys?
+
+ * Reinstall the ssh daemon to run as the user. Execute the following
+(substituting your user name for USERNAME, and your password for
PASSWORD):
+
+ chmod 666 /var/log/sshd.log /var/empty
+ rm -fr /var/log/sshd.log /var/empty
+ touch /var/log/sshd.log
+ chmod 644 /var/log/sshd.log
+ chmod 755 /var/empty
+ chown USERNAME.None /var/empty /etc/ssh_host_* /var/log/sshd.log
+ cygrunsrv --stop sshd
+ cygrunsrv --remove sshd
+ cygrunsrv --install sshd -e "CYGWIN=glob ntsec binmode" \
+ -u USERNAME \
+ -w "PASSWORD" \
+ -d "sshd" \
+ -p /usr/sbin/sshd.exe \
+ -1 /var/log/sshd.log \
+ -2 /var/log/sshd.log \
+ -a "-e -D"
+ cygrunsrv --start sshd
+
+ * NOTE: The user will not be able to login using their Windows password.
+They will only be able to login using RSA authentication.
+
+Therefore, you will need to copy your identity.pub and id_??a.pub
+files into authorized_keys, and authorized_keys2, respectfully.
+
+ Moreover, it's possible to use rhosts and/or rhosts with
RSA authentication by setting the following in sshd_config:
RhostsAuthentication yes
ssh-host-config.diff
Description: Binary data
ssh-user-config.diff
Description: Binary data
openssh-3.4p1-5.README.diff
Description: Binary data
--
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/
RE: Running Cron on XP (NT)
C:\cygwin\usr\doc\Cygwin\cron.README states cygrunsrv -I cron -p /usr/sbin/cron -a -D Does that fail for you? > From: [EMAIL PROTECTED] [mailto:cygwin-owner@;cygwin.com]On Behalf > Of Todd Shoenfelt > > I know I've seen documentation on setting up cygwin's cron daemaon, but > I can't seem to find it. I've checked the docs, FAQ, etc... I'm > guessing it involves adding cron as a service. > > Can somebody point me to the docs for this? > > Thanks in Advance, > > Todd -- 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/
RE: Cygwin, GNU make and VC++ ?
> From: Of Igor Pechtchanski > > > > Anyway, we're making progress in being able to compile with CL.EXE, but > > we're having trouble with include files. We use the flag > > '-I/home/user/dg/include' to point to the include directory, but it > > can't find it. /home/user/dg/include makes no sense in Windows. Use: C:\home\user\dg\include or C:/home/user/dg/include instead. -Riss -- 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/
RE: Trouble with RSA authentication
/usr/doc/Cygwin/openssh-3.4p1-5.README states that RSA authentication only
works if sshd runs under a user account (as opposed to the SYSTEM account).
To that end, I've created 2 shell scripts to allow one to "switch" from
running sshd as SYSTEM to running as a user, and visa versa.
These scripts will also fix the '/var/empty' problem, so they are worthwhile
to run once, even if you will never switch.
I haven't tried it, but you could probably even have a user and a SYSTEM
daemon running at the same time, by running one of the daemons on another
port via the -p option.
Attached and inline are the scripts.
I'll also put the latest versions up at http://www.netebb.com/cygwin/.
I'd love to see these incorporated into cygwin's openssh (or at least a user
contribs) package.
I'm not a cygwin wizard, so feedback is appreciated.
-Ross
#!/bin/sh
# $Id: sshd_user.sh $
case "$1" in
-h | -he | -hel | -help | -? | --h | --he | --hel | --help | --? | /h |
/he | /hel | /help | /?)
echo Usage: $0 [username] [password] ["CYGWIN options"] ["sshd options"]
exit 1
;;
*)
;;
esac
if [ -n "$1" ]
then
USER=$1
fi
CYGRUNSRV=
if [ -n "$2" ]
then
CYGRUNSRV="-w $2"
fi
if [ -n "$3" ]
then
CYGWIN=$3
fi
SSHD=""
if [ -n "$4" ]
then
shift
shift
shift
SSHD=$*
fi
cd
if [ ! -d .ssh ]
then
echo $0: Please run ssh-user-config first to create your .ssh directory.
exit 2
fi
chown ${USER}.None . .ssh /var/empty /etc/ssh_host_* /var/log/sshd.log
chmod 755 . .ssh
chmod 600 .ssh/*
chmod 644 .ssh/*.pub .ssh/authorized_keys? /var/log/sshd.log
chmod 755 /var/empty
cygrunsrv --stop sshd
cygrunsrv --remove sshd
cygrunsrv --install sshd -e "CYGWIN=${CYGWIN}" \
-u ${USER} \
${CYGRUNSRV} \
-d "sshd as ${USER}" \
-p /usr/sbin/sshd.exe \
-1 /var/log/sshd.log \
-2 /var/log/sshd.log \
-a "-e -D ${SSHD} "
cygrunsrv --start sshd
#!/bin/sh
# $Id: sshd_system.sh $
case "$1" in
-h | -he | -hel | -help | -? | --h | --he | --hel | --help | --? | /h |
/he | /hel | /help | /?)
echo Usage: $0 [CYGWIN options...]
exit 0
;;
*)
;;
esac
if [ -n "$1" ]
then
CYGWIN="$*"
fi
SSHD=""
if [ -n "$4" ]
then
shift
shift
shift
SSHD=$*
fi
if [ ! -f /etc/ssh_host_key ]
then
echo $0: Please run ssh-host-config first to create your /etc/ssh_host_*
files.
exit 2
fi
chown SYSTEM.SYSTEM /var/empty /etc/ssh_host_* /var/log/sshd.log
chmod 600 /etc/ssh_host_*
chmod 644 /etc/ssh_host_*.pub /var/log/sshd.log
chmod 755 /var/empty
cygrunsrv --stop sshd
cygrunsrv --remove sshd
cygrunsrv --install sshd -e "CYGWIN=${CYGWIN}" \
-d "sshd as SYSTEM" \
-p /usr/sbin/sshd.exe \
-1 /var/log/sshd.log \
-2 /var/log/sshd.log \
-a "-e -D ${SSHD}"
cygrunsrv --start sshd
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:cygwin-owner@;cygwin.com]On Behalf
> Of Max Bowsher
> Sent: Thursday, October 31, 2002 4:29 AM
> To: Marcos Lorenzo; [EMAIL PROTECTED]
> Subject: Re: Trouble with RSA authentication
>
>
> Marcos Lorenzo <[EMAIL PROTECTED]> wrote:
> > I finally got sshd working!
> >
> > But I cannot authenticate via RSA. I made the keygen with ssh-keygen
> > in my winbox and copied identity.pub to authorized_keys and identity
> > in my linbox (I have the same files in both machines). I really know
> > how ssh works in linux, but I have some troubles with RSA in cygwin.
> > Below is the message that I got:
> >
> > 12:16:21 marcos@laud~ ssh -i .ssh/identity.mozart -vvv mozart.lab -1
> > debug1: Connecting to mozart.lab [163.117.144.225] port 22.
> > debug1: Trying RSA authentication with key '.ssh/identity.mozart'
> > debug1: Server refused our key.
>
> Looks like the server logs with debugging enabled will hold the necessary
> info to debug this.
>
> Max.
sshd_user.sh
Description: Binary data
sshd_system.sh
Description: Binary data
--
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/
Updated sshd install scripts
I've updated my sshd install scripts to support named options: $ sshd_system.sh -? Usage: sshd_system.sh [options] options: -P|--port port -s|--sshd "sshd options"(quotes are required) -f|--config sshd_config_file (default is /etc/sshd_config) -c|--cygwin "CYGWIN environment variable" (default is "binmode ntsec tty") -?|--help this help screen -v|--version $ sshd_user.sh -? Usage: sshd_user.sh [options] options: -u|--user username (default is the current user (ross)) -p|--password password (do not use this option to be prompted for a password) -P|--port port -s|--sshd "sshd options"(quotes are required) -f|--config sshd_config_file (default is /etc/sshd_config) -c|--cygwin "CYGWIN environment variable" (default is "binmode ntsec tty") -S|--privsep (ignore "UsePrivilegeSeparation Yes" in /etc/sshd_config) -?|--help (this help screen) -v|--version The scripts set the correct permissions on all files, and explain how to deal with UsePrivilegeSeparation Yes I've posted the scripts and a short readme at http://www.netebb.com/cygwin/ And you can download them from http://www.netebb.com/cygwin/sshd_install_scripts.tgz I hope you find them useful. -Ross -- 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/
RE: cmd.exe as telnetd login shell: "mode con LINES=24 COLS=80" has no effect..
Tom,
The Windows Telnet Service fixes the MORE and DOSKEY problems you describe.
If you want to disallow external telnet, you could block port 23, and
require users to ssh in, and then run
% telnet localhost
Of course, they'll have to enter their NTLM username/password.
You could even change their shell to be a shell script containing this
command.
Can anybody guess why cmd.exe works with the Windows Telnet Service but
fails with cygwin's ssh or telnet?
-Ross
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
> Of [EMAIL PROTECTED]
> Sent: Friday, November 29, 2002 8:10 AM
> To: [EMAIL PROTECTED]
> Subject: cmd.exe as telnetd login shell: "mode con LINES=24 COLS=80" has
> no effect..
>
>
>
>
>
> Hello:
>
> A couple of people that insist on using cmd.exe as their login shell when
> they telnet or ssh to our w2kserver.
>
> When the login shell is set to "/cygdrive/c/winnt/system32/cmd",
> and "putty" is the telnet client:
>
> 1) "more < foo" does not work, it has no clue about
> the window size.
>
> o tried "mode con LINES=24 COLS=80", when I
> then ran "mode con" it appeared to have "taken",
> but "more < foo" still did not page correctly
>
> o I tried setting LINES to no avail.
>
> o tried various combinations of "cmd" switches
> ( "/X" also "/A", did not try "/Y")
>
> 2) I would also like to enable the DOSKEY command history capability,
> "Up Arrow" literally moves the cursor 1 row up. I tried
> "doskey /reinstall" - it has no apparent effect.
>
> 3) I had to kloosh things to get the backspace to do the
> "erase" function. I wrapped cmd.exe inside a bash
> script that did a "stty erase ^H" before it started
> cmd.exe. Is there a better way?
>
> 4) If you set the shell to
> "/cygdrive/c/winnt/system32/cmd", login
> and then type "bash --login" to get a bash shell
> (dumb, but needed sometimes), bash hangs. This
> is still a mystery. To work around this I
> always start a bash session after the user exits
> cmd.exe - see below.
>
> Any help or ideas would be welcomed. I'm beginning to lean towards
> the unhappy position that we will have to use Microsoft's or
> Ataman's telnetd; I would love to avoid this.
>
> Pls understand how very much I *appreciate* the cygwin toolset, and that
> I'm an ever-so-humble day in day out, sys admin/end user of your tools.
>
> For more details on what I did see end of this e-mail.
>
> --
> thanks/regards,
> Tom
> perl -e 'print unpack("u", "\-\=\$\!R\;V1M86XN8V\]M\"\@\`\`");'
>
> --v-v--C-U-T---H-E-R-E-v-v--
> > 17:15:45 Wed Nov 27 /adm/bin/sys/s
> > C7MKES109 adm_tsr > grep build /etc/passwd|fold
> build:unused_by_nt/2000/xp:12122:12119:build,U-MKE\build,S-1-5-21-
> 1177238915-197
> 9792683-1801674531-2122:/user/build:/drv/c/adm/bin/sys/s/cmd_login_shell
> > 17:50:35 Wed Nov 27 /adm/bin/sys/s
> > C7MKES109 adm_tsr > cat /drv/c/adm/bin/sys/s/cmd_login_shell
> #!/bin/bash -
> /bin/stty erase
> /drv/c/winnt/system32/cmd
> /bin/bash --login
--
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/
expat-1.95.5: undefined reference to `XML_ParserCreate'
I'm trying to compile a simple expat program:
#include
#include
int main() {
XML_ParserCreate(NULL);
return 0;
}
but I get:
$ gcc -lexpat -L/lib expattest.c
/cygdrive/...:expattest.c: undefined reference to `XML_ParserCreate'
yet:
$ nm /lib/libexpat.a | grep XML_ParserCreate
T _XML_ParserCreate
So, I tried compiling expat from source via:
cd /usr/src
tar xvzf expat-1.95.5.tar.gz
./expat-1.95.5-1.sh conf
./expat-1.95.5-1.sh prep
./expat-1.95.5-1.sh build
And tried to build one of their examples (make check, the expat test suite,
relies on http://check.sf.net/ to be installed):
cd expat-1.95.5/.obj
$
gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -I/us
r/src/expat-1.95.5/lib -I. -lexpat -L.libs -o examples/outline.c
/usr/src/expat-1.95.5/examples/outline.c
/cygdrive/...: In function `main':
/usr/src/expat-1.95.5/examples/outline.c:60: undefined reference to
`_XML_ParserCreate'
and I *still* get the same error.
I've scanned the mailing list to no avail. What am I possibly doing wrong?
-Ross
CYGWIN_NT-5.0 DURGA 1.3.17(0.67/3/2) 2002-11-27 18:54 i686 unknown
--
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/
RE: Burning cygwin distribution CDs
> From: Laurynas Biveinis
>
> I want to burn CDs with full cygwin distribution with sources and so on.
> I've downloaded everything from
> ftp://ftp.gwdg.de/pub/linux/sources.redhat/cygwin/release, but it takes
> almost 1 GB. How should I burn it into 2 CDs so that setup.exe still
> works correctly? What directory layout should I use?
Laurynas,
I fit everything I need on 1 CD, by not including the /xfree directory
(370MB), the /release/XFree86 directory (80MB), and not including the [prev]
and [test] packages listed in setup.ini:
#!/usr/bin/perl -w
use strict;
my $dir = shift || '/hdc1/cygwin';
my $file = $dir . '/setup.ini';
open(FH, $file) || die "Can't open $file: $!";
my $prev = 0;
my $line = 0;
while () {
$line++;
if (/\[prev\]/ || /\[test\]/) {
$prev++;
next;
}
next unless $prev;
if (/^\s*$/) {
$prev = 0;
next;
}
if (/^\w+:\s*(\S+)\s+/) {
$_ = $1;
next unless m|/|;
$file = $dir . '/' . $_;
if (-e $file) {
print "deleting $file\n";
unlink($file);
}
}
}
Hope that helps,
Ross
--
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/
[ANNOUNCEMENT] Updated: email-2.5.0-1
Version 2.5.0-1 of email has been uploaded. Email is a simple command-line program to send emails. It can be configured to use either your sendmail installation or directly via SMTP. It supports binary attachments, and a simple text based address book, with groups. Also, if GnuPG is installed, it can digitally sign and encrypt outgoing emails. Changelog: - Separated e-mail name and address and only format them in the headers. Only use address surrounded by <> as per RFC 822 for the MAIL FROM: and RCPT TO: SMTP commands. - Added Dstring library which is a string library to growing strings. - Using Dstring's for reading in config file and address book. This fixes the MINBUF limitations that were happening with very long Groups in the address book. - Added ability to specify new headers on the command line. - Handle \r in address book so that Cygwin users don't have to put a comment at the end of their lines. - the --attach and --header option can be specified multiple times and also have multiple entries with comma delimeters. If you have questions or comments, please send them to the Cygwin mailing list at: cygwin@cygwin.com . *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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/
[ANNOUNCEMENT] New Package: email-2.3.0-2
The following package has recently been added to the Cygwin distribution: email-2.3.0-2: Command line sending of email, optionally with GnuPG encryption. Email is a simple command-line program to send emails. It can be configured to use either your sendmail installation or directly via SMTP. It supports binary attachments, and a simple text based address book, with groups. Also, if GnuPG is installed, it can digitally sign and encrypt outgoing emails. To update your installation, click on the "Install Cygwin now" link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Then, run setup and answer all of the questions. -Ross Smith - -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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/
[ANNOUNCEMENT] Updated: email 2.5.1-1
The cygwin email package has been updated to the current stable version 2.5.1. To ease packaging, the default configuration files that were stored in /etc/defaults/etc/email/ are now stored in /etc/defaults/etc/. The actual configuration files are still kept in /etc/email. Upstream changelog: - Fixed bug where an assert caused an abort when encrypting any message with gnupg under Cygwin. - Fixed compile errors saying SIGHUP, SIGINT or other SIG* were "undeclared - Fixed e-mail address parsing problems in which eMail would report error's such as an e-mail address was invalid. - Very small source cleanup. To update your installation, click on the "Install Cygwin now" link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Then, run setup and answer all of the questions. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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/
[ANNOUNCEMENT] Updated: cppunit-0.12.0-1
I've updated the version of cppunit to 0.12.0-1. This is a bugfix release. The Cygwin release is the vanilla version, no additional patches. === New in CppUnit 1.12.0: -- * Portability: - autogen.sh can now be run on Mac OS X (patch #1449380 contributed by Sander Temme). * MFC Test runner: - fixed bug #1498175: double click on failure would sometime not goto failed assertion in visual studio. * Documentation: - now generated with doxygen 1.4.7 new 'tabs' style. New in CppUnit 1.11.4: -- * Portability: - Support for Embedded Visual C++ 4 added. For this purpose, CppUnit now provides a very simple stream implementation if none is provided. This should also help porting on other platforms which have STL but no stream support. Just make sure that CPPUNIT_NO_STREAM is defined to 1 in your config header. * Assertion: - Added missing _MESSAGE variants for the following assertions: CPPUNIT_ASSERT_DOUBLES_EQUAL_MESSAGE CPPUNIT_ASSERT_THROW_MESSAGE CPPUNIT_ASSERT_NO_THROW_MESSAGE CPPUNIT_ASSERT_ASSERTION_FAIL_MESSAGE CPPUNIT_ASSERT_ASSERTION_PASS_MESSAGE Notes: change made to CPPUNIT_ASSERT_THROW may cause compilation error if you're expecting std::exception as it would be caught twice. Contact us if it is an issue (we don't see much use for such a test). Some assertions failure message are now more detailed (exception, expression). Thanks to Neil Ferguson who contributed this patch. - Assertion on real number now output expected and actual value using the maximum available precision instead of the previous strategy of rounding to 6 digits. Thanks to Neil Ferguson who contributed this patch. * Outputter: - XML Ouputter: patch #997006 contributed by Akos Maroy makes the 'stand-alone' attribute of the XML header optional. See XmlOutputter::setStandalone() & XmlDocument::setStandalone(). - Better integration of compiler output for gcc on Mac OS X with Xcode (contributed by Claus Broch). * MFC Test Runner - Integration with VC++ 7.0 & 7.1. Double clicking on a failure will now to the failure location in the open IDE (no add-in necessary). This was contributed by Max Quatember and Andreas Pfaffenbichler. - Progress bar: now use system color to draw border (patch from bug #1165875 contributed by Pieter Van Dyck). * QT Test Runner - Fixed display of multi-line messages (patch contributed by Karol Szkudlarek). * Compilation: - The standard pkg-config file is now generated on unix (contributed by Robert Leight). - MinGW: patch #1024428 contributed by astar, fixed compilation issue in Win32DynamicLibraryManager.cpp. - MinGW, cygwin: enable build of shared library when using libtool. patch #1194394 contributed by Stéphane Fillod. - autotool: applied patch #1076398 contributed by Henner Sudek. Quote: "This patch allows AM_PATH_CPPUNIT to accept version numbers without minor and micro version. Now you can do: AM_PATH_CPPUNIT(1.9) instead of AM_PATH_CPPUNIT(1.9.0)" - Visual Studio 2005: removed deprecated warning. * Documentation: - Corrected many typos in cookbook and money example. Thanks to all those who helped ! * Bug Fix: - cppunit.m4: patch #946302, AM_PATH_CPPUNIT doesn't report result if CppUnit is missing. - Message/SourceLine: copy constructor have been specifically implemented to ensure they are thread-safe even if std::string copy constructor is not (usually on reference count based implementation). - TestResultCollector: fixed memory leak occuring when calling reset(). * Contrib: - added XSLT for compatibility with Ant junit xml formatter. Patch #1112053 contributed by Norbert Barbosa. See xml-xsl/cppunit2junit.xsl and cppunit2junit.txt for details. - xml-xsl/report.xsl has been fixed to work with current xml output. * (Possible) Compatiblity break: - All text output is now done on cout() instead of sometime cerr & sometime cout depending on the component. - OStringStream definition has been removed from Portability.h. This means that is no longer included, and that ostringstream and string might not be defined. In practice this should have no impact since those includes have been moved to other CppUnit headers. * Notes: - CppUnit now uses the alias OStream when refering to std::ostream for portability. New in CppUnit 1.10.2: -- * Bug Fix: - Memory checker: bug #938753, array bound read in splitPathString() with substr if an empty string is passed. - Memory leaks: bug #952912, many memory leaks removed in the MFC test plug-in runner. - Crash when using CPPUNIT_TEST_SUITE_REGISTRATION with cpp
[ANNOUNCEMENT] Updated: email-3.1.2-1
I've made a new version of 'email' available for installation. This is the most recent version of email available from http://www.cleancode.org/projects/email. Changes since 2.5.1: - Minimal TLS support - Added UTF-8 support for headers and message - Added a timeout option - Fixed bug that was causing 100% CPU usage on some mailings - Fixed the "No SMTP Server specified" issue that existed on 64bit and Solaris systems - Fixed issue where mime types weren't being guessed correctly or the mime type was coming out blank - Added VCARD support - Small bug fixes *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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/
[ANNOUNCEMENT] [1.7] Updated: email-3.1.2-2
I've made a new version of 'email' available for installation. This is the most recent version of email available from http://www.cleancode.org/projects/email. Changes since 2.5.1: - Minimal TLS support - Added UTF-8 support for headers and message - Added a timeout option - Fixed bug that was causing 100% CPU usage on some mailings - Fixed the "No SMTP Server specified" issue that existed on 64bit and Solaris systems - Fixed issue where mime types weren't being guessed correctly or the mime type was coming out blank - Added VCARD support - Small bug fixes *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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/
