Re: RFP: texmf
Re: renaming the package. Don't do this *yet*. a) there is no urgency in doing so, b) setup can't help at this point, and using ncurses as a reference point, it could have been worse, and ncurses has _no_ knobs to twiddle and get wrong, which tex* does AFAIK. setup will be able to help, probably the release-after-next. Rob
Re: string.h vs string.h usage
Pavel Tsekov wrote: Any opinions on this topic ? Btw one thing - I've found many #include strings.h in the latest sources - shouldn't this be changed to #include string.h ? mingw doesnt have strings.h. Btw It seems that if you have string.h you dont need strings.h (I'm under the impression that string.h include strings.h on linux) Does this sound reasonable ? Right, MinGW provides string.h not strings.h because MS doesn't provide strings.h. I dunno. Setup builds with -mno-cygwin with FAIK uses all mingw headers, so I don't know whether that is needed or not. Thats probably better asked on-list :}. Setup, strace, possibly more build with the -mno-cygwin switch picking up the MinGW headers. Yes but it gives various include paths from cygwin build and newlib build - this means that you compile only in this environment (i.e. winsup env). If you try only mingw it wont work :) However I've fixed that for me locally There should be nothing to fix. If there is then you've done something wrong in the setup or building the program. Using -mno-cygwin should only give you MinGW headers and never the Cygwin headers. The only way I can think of that this would happen is if you also added a -I/usr/include to the gcc build options or if you modified the gcc source and rebuilt it yourself. Earnie. _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Re: string.h vs string.h usage
Earnie Boyd wrote: Yes but it gives various include paths from cygwin build and newlib build - this means that you compile only in this environment (i.e. winsup env). If you try only mingw it wont work :) However I've fixed that for me locally There should be nothing to fix. If there is then you've done something wrong in the setup or building the program. Using -mno-cygwin should only give you MinGW headers and never the Cygwin headers. The only way I can think of that this would happen is if you also added a -I/usr/include to the gcc build options or if you modified the gcc source and rebuilt it yourself. By fixing I mean replacing strings.h with string.h :) Btw it doesnt pick only mingw headers - check the makefile - i uses the option -isystem and supplies a bunch of include header file dirs from newlib and winsup.
Re: string.h vs string.h usage
egor duda wrote: Hi! Wednesday, 05 December, 2001 Pavel Tsekov [EMAIL PROTECTED] wrote: SUSv2 mandates both strings.h and string.h mingw declares strcasecmp() in string.h while SUSv2 says it should be in strings.h Afaik str[n]case is and BSD-ism :) Btw here is what glibc on redhat 7.1 says. /* We don't need and should not read this file if string.h was already read. The one exception being that if __USE_BSD isn't defined, then these aren't defined in string.h, so we need to define them here. */ i believe mingw headers should be fixed/updated.
RE: problem with make
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Christopher Faylor Sent: Tuesday, December 04, 2001 4:57 PM To: [EMAIL PROTECTED] Subject: Re: problem with make On Tue, Dec 04, 2001 at 08:14:04PM +1100, Robert Collins wrote: - Original Message - From: Ralf Habacker [EMAIL PROTECTED] Does anyone have an idea for fixing this ? I have no problem to fix this, if somebody could give me a direction where I have to look on. Use linux or get the KDE team to fix their makefiles. You _could_ try the cygwin=case_insensitive (spelling?) flag. The core problem though is that that use they are making of the filesystem is invalid for case insensitive filesystems - and windows isn't the only one around. Also, please use [EMAIL PROTECTED] for this type of bug reporting. This is not an applicable topic for cygwin-apps. From the mailing list page: cygwin-apps: a by-approval developers list for discussing issues regarding applications that are distributed with the Cygwin DLL. Is make an application distributed with cygwin ? :-) Regards Ralf
Re: string.h vs string.h usage
=== - Original Message - From: Earnie Boyd [EMAIL PROTECTED] egor duda wrote: Hi! Wednesday, 05 December, 2001 Pavel Tsekov [EMAIL PROTECTED] wrote: SUSv2 mandates both strings.h and string.h Wrong documentation base. You must use MSDN for MinGW. mingw declares strcasecmp() in string.h while SUSv2 says it should be in strings.h i believe mingw headers should be fixed/updated. No, MinGW headers are correct according to MSDN. Perhaps the problem here is that strcasecmp doesn't exist in the MinGW world. From what I find, strcasecmp is a BSD addition to even POSIX. That said, MinGW supports ANSI functions only. I'll change setup to use string.h globally then. If need be we can roll our own strcasecmp. Rob
Re: string.h vs string.h usage
On Wed, Dec 05, 2001 at 03:39:38PM +0300, egor duda wrote: Hi! Wednesday, 05 December, 2001 Pavel Tsekov [EMAIL PROTECTED] wrote: PT egor duda wrote: Hi! Wednesday, 05 December, 2001 Pavel Tsekov [EMAIL PROTECTED] wrote: SUSv2 mandates both strings.h and string.h mingw declares strcasecmp() in string.h while SUSv2 says it should be in strings.h PT Afaik str[n]case is and BSD-ism :) it doesn't matter as long as standard defines it. please note that it doesn't marked as obsolete -- usage of those functions is supposedly pretty portable. mingw doesn't have to adhere to this standard! I can't believe that I've woken up to a huge thread about this trivial issue. Can't we just rename strings.h to string.h in setup sources? What's the big frigging deal here? Why does every thread that touches setup.exe have to be so torturous? cgf
Re: string.h vs string.h usage
egor duda wrote: Hi! Wednesday, 05 December, 2001 Earnie Boyd [EMAIL PROTECTED] wrote: EB egor duda wrote: Wednesday, 05 December, 2001 Pavel Tsekov [EMAIL PROTECTED] wrote: SUSv2 mandates both strings.h and string.h EB Wrong documentation base. You must use MSDN for MinGW. why? i can understand this wrt w32api, but for c runtime? correct me if i'm wrong, but i was thinking that mingw is basically a portability toolkit just like cygwin, with only difference that it doesn't possess portability layer and uses native dlls. The runtime is MS VC RT.DLL of course the file name is without the spaces. that said, when i port some program that's written portably in the sense complies with SUSv2, i suppose that it'd be ported without much fuss, if it doesn't use functions not provided by crtdll/msvcrt. Right, but the only headers that MinGW-runtime care about are the ones described by MS. MinGW has always been and will always be ANSI compliant only. Porting UNIX programs to Win32 is the point of Cygwin not of MinGW. the problem with -mno-cygwin here is that afaics there's no easy way to prevent gcc from looking into standard places when it's looking for headers. with true native mingw gcc everything's ok. but when we use cygwin gcc with -mno-cygwin, and application includes strings.h, gcc will include cygwin's header. it'd give no warnings or errors until it comes to linking and we'll see a bunch of __impure_ptr undefined. mingw declares strcasecmp() in string.h while SUSv2 says it should be in strings.h i believe mingw headers should be fixed/updated. that is, if mingw doesn't really provide any of the functions declared in strings.h (a quick look at msvcrt/crtdll exports made me think it doesn't), it may just provide an empty one. it'd solve -mno-cygwin problems and won't break anything in mingw world. EB No, MinGW headers are correct according to MSDN. Perhaps the problem EB here is that strcasecmp doesn't exist in the MinGW world. then it's not clear to me why it's declared in mingw's string.h Ok, I just looked. It's in the string.h header and is provided from an add-on library libmoldname.a (MSVCRT.DLL version). I understand your point Egor and will take this up further in the MinGW-dvlpr list. These add-ons from prior maintainers have stepped on me and the MinGW team before. The simplest fix for now is to just add a strings.h that simply includes string.h. Earnie. _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Re: cygutils: Category
Robert Collins wrote: - Original Message - From: Earnie Boyd [EMAIL PROTECTED] Keeping backward compatible/useable behaviour for a) Local installs from directories without setup.ini files, and That user must deal with those themselves. Nice in theory. If that was truely the case I could delete an entire source file and remove some problematic logic from setup.exe. Unfortunately, last I heard we do have to support those users. b) packages that for (whatever) reason don't have a category. If they are required as part of the Base setup then the category is simply Base. No. Packages without a category have either been added manually to a cached setup.ini, or have been added without a setup.hint. In either case we dont' want them appearing under the Base category - they are NOT officially sanctioned base packages that *we here* want to appear there. http://sources.redhat.com/ml/cygwin-developers/2001-06/msg00098.html is the message where Misc is suggested by cgf. I see, I chimed in on that thread. I didn't know though it would be a required download. Hopefully, this can be remedied in the future. Can I suggest we change the setup behavior please? Sure. You get to deal with the users though :}. That's easy, just ignore them. ;) Eventually someone will figure it out and help those who can't. True, true. Yep, Chris' experiment earlier this year proved to me that I could just stop posting on the users list to deal with other matters. I still read the posts in the digest mode, particularly if it has an interesting subject header. Earnie. _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Re: RFP: texmf
- Original Message - From: Jan Nieuwenhuizen [EMAIL PROTECTED] How long would it take to phase them out? A fresh setup.ini that doesn't mention tetex-beta would make tetex-beta invisible? Hmm, but then we'd need a 'conflicts:' setup hint or so, and locally cached setup.ini's could generate trouble. The package will not disappear if it's not in setup.ini. It's still present in installed.db. The _only_ way to force an uninstall of a package is when we support conflicts: which will come AFTER we support package-dependency-install-oredering (Which BTW allows the installation of an empty package to replace the old one as a safe upgrade path). Anyway, the best part is the fact that tetex-beta/bin gets a rebuild, and we're talking. Of course, the renaming should be a bonus, not a pain. Yes. And it would need some testing too. Phasing-out packages will be a needed feature at some point, but maybe not highest priority now. What about pre/postremove scripts, eg? Testing? Thats what the end users do isn't it :} Rob
Re: [REQ] apache-1.3.22 package available
Yep :]. ok, convinced me, I'll be re-packaging today. OpenBSD also does this. IMO it's the best way for apache because a) /var is appropriate for user modified data files for applications, and b) www is easily associated with apache, AND can be reused if apache is removed and (pick favorite alternative) installed. who is going to use something other than apache, good damn it! :)) c) /etc/apache is nicely contained for the plethora of files apache used to have, (and with SSL can have) yet is clearly configuration data. Corinna's standard configure line as quoted in http://www.cygwin/com/setup.html probably does most of this automatically. I'd also like to suggest that the home page in the package be altered to say what platform its running on (if it doesn't already :}). no it doesn't, but the Apache Server String is set to say: Apache/1.3.22 (Cygwin) module1 ... :)), so we _are_ known to have Apache running on Cygwin. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
cygutils: Category
Chuck, Misc as a category acts like base: things in it always install. I guess this isn't documented clearly anywhere except the cygdev archives, so I'll correct that soon. Can I suggest that the cygutils packages belongs in (shock horror) Utils ? Rob
Re: cygutils: Category
Robert Collins wrote: Chuck, Misc as a category acts like base: things in it always install. Uhm, why? I missed this conversation evidently. IMNSHO, Base should be the only required install. Misc are niceties that make the job easier but aren't required. I guess this isn't documented clearly anywhere except the cygdev archives, so I'll correct that soon. Can I suggest that the cygutils packages belongs in (shock horror) Utils ? Can I suggest we change the setup behavior please? Earnie. _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
RE: New devel to-do item (release all pressed keyboard keys on focus loss)
I suppose for this the solution would be to make winSendKeyEvent
do nothing if
its fDown already matches the array element
Nah, you can't do that because we sometimes call winSendKeyEvent multiple
times from winwndproc/winWindowProc()/WM_KEYDOWN if the key has a repeat
count.
But I can do it when both are *false*. This goes over my earlier patch:
--- winkeybd.c~ Tue Dec 4 16:42:28 2001
+++ winkeybd.c Wed Dec 5 16:39:49 2001
@@ -439,7 +439,12 @@
winSendKeyEvent (DWORD dwKey, Bool fDown)
{
xEvent xCurrentEvent;
-
+
+ /* Ignore ups without a preceding down. This happens when a keystroke
+ causes X to gain focus. */
+ if (!fDown !g_fKeyStates[dwKey])
+return;
+
ZeroMemory (xCurrentEvent, sizeof (xCurrentEvent));
xCurrentEvent.u.u.type = fDown ? KeyPress : KeyRelease;
I'm kinda confused here. You need to add an ErrorF () to WM_KEYDOWN and
WM_KEYUP to see if the doubled key message is being sent again immediately
after we regain focus.
Here is my XWin.log:
keydown #16 at 22939
keyup #16 at 23250
keydown #17 at 23320
keyup #17 at 23570
keydown #18 at 23680
keyup #18 at 23981
keydown #19 at 24091
keyup #19 at 24412
keydown #16 at 24452
keyup #16 at 24752
keydown #17 at 24792
Simulating release of key #17!
killfocus at 24862
setfocus at32363
keyup #45 at 32483
killfocus at 42017
And here is my xterm after the setfocus at 32363 ms:
$ qwerqww
'w' is key #17. The only thing that could be happening is that xterm is
outsmarting itself by doing something with its own killfocus. My preference is
to let xterm users deal. We're used to it. :-)
I doubt
whether I can figure it out completely without a major time investment.
This is your baby now, and you're making good progress. Don't be
discouraged. These things take time to work out correctly.
Without your help, I would probably lose patience.
-John
Re: install error
how about putting bunzip2 (if you have it) in a directory in the PATH Nidhi Bhatia wrote: I am having problems Installing XFree86. When attempting to extract the extract.exe.bz2 archive using the following command: bunzip2 extract.exe.bz2 the following error occurs: BASH: bunzip2: command not found I have followed the instructions in the user's guide and do not know how to correct this. Should I redownload something again? _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
setup.exe
Hi, How you tell setup.exe to download to a local directory the absolute latest of EVERYTHING. By default full appears to come up with mostly skip for each item. It is rather difficult to go through the full list item by item, clicking through the available versions to pick the latest one, and do it before the mirror site times out waiting for you and disconnects. I am running setup 2.125.2.10 on win98se. === John Daniel Doucette, Sr. Software Designer J. J. MacKay Canada Limited Halifax R D Office 1046 Barrington Street, 1st Floor Halifax, Nova Scotia Canada B3H 2R1 Phone: 902.423.7727 x222 Fax: 902.422.8108 Web:www . jjmackay . ca Email: john . doucette @ jjmackay . ca === -- 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/
cygwin1.dll
where can I download just the lastest cygwin1.dll? or can u email it to me?please? -- 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 1.3.6 + bash 2.05a-2 + command completion
Hi, I tried to take a shot at this. But I did not manage to compile the cygwin source. I'm not sure how to do that. I also failed to compile the cygcheck program to find a possible missfeature in that program. And at the moment I don't have the time to find out what is going wrong with that. But as has shown is that it is the traversing of the path. That is trying to find files in paths that does not exist. I guess that it has something to do with opendir/readdir. If I have time tonight I'll try to compare diffrences between 1.3.5-3 and 1.3.6 source. But if I interperet the ChangeLog correctly the changes on the opendir/readdir part is quite large. Jens Yllman Robert Collins wrote: FWIW I think that cygwin is dying, not bash. However, as I haven't looked at the code Rob === - Original Message - From: Yllman, Jens [EMAIL PROTECTED] To: Robert Collins [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, December 05, 2001 11:39 PM Subject: Re: cygwin 1.3.6 + bash 2.05a-2 + command completion Hi, The ChangeLog reports the following. 2001-11-24 Christopher Faylor [EMAIL PROTECTED] * fhandler_disk_file.cc (fhandler_cygdrive::readdir): Avoid reporting inaccessible drives. Maybe bash expect to get something like invalid drive or something. I've not checked bash. And I've not traced anything. Just this quick look at the ChangeLog. There is also other notes about fhandler_disk_file.cc in the ChangeLog. * fhandler_disk_file.cc (fhandler_disk_file::opendir): Set nohandle flag on dummy fd. I don't know if anybody can look into it. I don't have any more time. About the reason for me testing with sh also and not only bash was to see that it realy is bash handling of tab that crashes and not the stty settings or something like that. Jens Yllman Robert Collins wrote: === - Original Message - From: Yllman, Jens [EMAIL PROTECTED] Hi, Yes, I have a /cygdrive/x in my path that is not always maped. When I map it it works fine. Ok, in my mind that conforms the way to reproduce. I don't have time at the moment (sigh, I wish I did, I really do) to debug this myself though. Rob Uniweb ABPhone: +46 8 626 42 00 P O Box 745 FAX:+46 8 626 42 01 S-191 27 SOLLENTUNA SWEDEN http://www.uniweb.se/ -- 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: GCC : -static option does not generate statically linked executable
[EMAIL PROTECTED] wrote: Hi, I am trying to generate an executable, using gcc -static option. The generated file is dynamically linked! As if the -static option was simply ignored. The output of cygcheck is as follows : Error: could not find libX11.dll C:\cygwin\bin\cygwin1.dll C:\WINNT\System32\KERNEL32.dll C:\WINNT\System32\ntdll.dll C:\cygwin\bin\cygtcl80.dll C:\WINNT\System32\USER32.dll C:\WINNT\System32\GDI32.dll C:\WINNT\System32\ADVAPI32.dll C:\WINNT\System32\RPCRT4.dll C:\cygwin\bin\cygtk80.dll C:\WINNT\System32\COMDLG32.DLL C:\WINNT\System32\SHELL32.dll C:\WINNT\System32\COMCTL32.dll One can see that the X11 DLL library is not found : however, I use the -static option of gcc, before the -lX11 stuff, as mentioned in the documentation. I expect the compiler to link against libX11.a, so what happens? Any idea would be greatly appreciated, -static will cause the linker to link against a static lib IF POSSIBLE. However, it really just means hunt for '.a' instead of '.dll.a' or '.dll' .dll.a == import lib for a dll .dll == the linker has a limited ability to link directly to a dll *without* using an import lib. .a == static lib (mostly *) (*) The problem: many packages -- including X -- name their *import* libs using the .a suffix. So, when you specify -static, the linker diligently links against the .a file == an import lib == and you get a dynamically linked executable. When this sort of behavior happens, it's usually becuase there IS no static library at all -- you CAN'T link statically. (The X libraries are a good example; cygwin-xfree project does NOT provide static libs.) Also, note that you can't link a cygwin program *fully* statically -- at minimum, it will require cygwin1.dll... As far as your particular can't find libX11.dll problem -- add /usr/X11R6/bin to your system PATH. --Chuck -- 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: [ANNOUNCEMENT] New on sourceware: cygutils-0.9.7-1
I used setup to download the latest files and this cygutils was included. When I ran setup to install the files, I selected Skip for this particular package. Each time I run Setup, I still have to click Skip for the cygutils package. Is there a way to make Setup always skip this package along with the numerous other pakcages I choose not to install? And please don't tell me, Install everything because I don't want to do that. Regards, rotaiv At 12/05/2001 03:47 AM, Charles Wilson wrote: cygutils-0.9.7-1 has been uploaded to the Cygwin net distribution. cygutils provides a collection of small -- and hopefully useful -- utilities. This package started life as the misc package from the CygUtils website, but has been renamed and has a new home: http://www.neuro.gatech.edu/users/cwilson/cygutils-package/ It provides: ascii.exebanner.exe cal.exe dump.exe namei.exe conv.exe u2d.exe unix2dos.exe d2u.exedos2unix.exe putclip.exe getclip.exe The source package provides: semtool.exe semstat.exe semtool.exe msgtool.exe (these are not distributed in binary form because they require the cygipc package -- which is not part of the official cygwin distribution. There are good reasons for this; search the mailing list archives if you're curious) --Chuck 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. Save it and run setup, answer the questions and pick up 'cygutils' from the 'Devel' category. Note that downloads from sources.redhat.com (aka cygwin.com) aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update. In the US, ftp://mirrors.rcn.net/mirrors/sources.redhat.com/cygwin/ is a reliable high bandwidth connection. In Japan, ftp://ftp.u-aizu.ac.jp/pub/gnu/gnu-win32/ is already updated. In DK, http://mirrors.sunsite.dk/cygwin/ is usually up-to-date. If one of the above doesn't have the latest version of this package you can either wait for the site to be updated or find another mirror. Please send questions or comments to the Cygwin mailing list at: [EMAIL PROTECTED] . If you want to subscribe go to: http://cygwin.com/lists.html I would appreciate if you would use this mailing list rather than emailing me directly. This includes ideas and comments about the setup utility or Cygwin in general. If you want to make a point or ask a question the Cygwin mailing list is the appropriate place. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** To unsubscribe to 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] -- 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/ -- 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: [ANNOUNCEMENT] New on sourceware: cygutils-0.9.7-1
rotaiv wrote: I used setup to download the latest files and this cygutils was included. When I ran setup to install the files, I selected Skip for this particular package. Each time I run Setup, I still have to click Skip for the cygutils package. Is there a way to make Setup always skip this package along with the numerous other pakcages I choose not to install? And please don't tell me, Install everything because I don't want to do that. It's a packaging bug. I put cygutils in the Misc category which is always installed. I have now moved it to the Utils category, so setup should remember your skipped it. Just wait for the change to propogate thru the mirror system.. --Chuck -- 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: Debug version of cygwin dll
Hi! Wednesday, 05 December, 2001 Peter Buckley [EMAIL PROTECTED] wrote: PB You need to bunzip2 and untar the src, then cd to PB /usr/src/cygwin-1.3.5-3 (or wherever you extracted it to) and do the PB following: PB mkdir build PB cd build PB ../configure PB make PB make install please, don't make wrong suggestions! this way is _wrong_. for a correct way, check the FAQ, particularly question How do I rebuild the tools on my NT box? cygwin sources also contain a file how-to-debug-cygwin.txt which contains several debugging hints. Egor.mailto:[EMAIL PROTECTED] ICQ 5165414 FidoNet 2:5020/496.19 -- 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: -mno-cygwin and SDL
[EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: Hi, I downloaded and compiled SDL-1.2.3 from source in cygwin, and suprisingly I got it to work. Then I tried to set -mno-cygwin so that the app would work outside of Cygwin, but I get: $ make win gcc test1.C -mno-cygwin -I /usr/include -lglut32 -lglu32 -lopengl32 -lSDL -o exec/test1.exe The line above should be changed like this: gcc test1.C -mno-cygwin -I /usr/include -o exec/test1.exe -lglut32 -lglu32 -lopengl32 -lSDL Read the FAQ on cygwin.com it contains a topic on WinMain@16. I tried your suggestion, but I get the same error. I also looked at the FAQ, it did not give me any clues either. Shawn Lindberg I modified my compile commands as per the SDL FAQ so that they it is now: gcc test1.C -mno-cygwin -I /usr/include -o exec/test1.exe -lglut32 -lglu32 -lopengl32 `sdl-config --cflags --libs` However, now I get the errors: In file included from /usr/include/SDL/SDL_rwops.h:35, from /usr/include/SDL/SDL.h:37, from test1.C:19: /usr/include/stdio.h:157: type specifier omitted for parameter /usr/include/stdio.h:158: type sepcifier omitted for parameter .. and so on for lines 159, 189, 194-197, 246-252. Any ideas? Shawn Lindberg -- 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/
Still gcc problems
I have further circumscribed the problem: gcc cprogram.c -o cprogram.exe- v creates the following output, i.e. it trys to run the following programs: Reading specs from /usr/lib/gcc-lib/i686-pc-cygwin/2.95.3-5/specs gcc version 2.95.3-5 (cygwin special) *** cpp0.exe ** /usr/lib/gcc-lib/i686-pc-cygwin/2.95.3-5/cpp0.exe -lang-c -v -D__GNUC__=2 -D __G NUC_MINOR__=95 -D_X86_=1 -D_X86_=1 -Asystem(winnt) -Acpu(i386) -Amachine(i38 6) - Di386 -D__i386 -D__i386__ -Di686 -Dpentiumpro -D__i686 -D__i686__ -D__pentiu mpro -D__pentiumpro__ -D__stdcall=__attribute__((__stdcall__)) -D__cdecl=__attri bute __((__cdecl__)) -D_stdcall=__attribute__((__stdcall__)) -D_cdecl=__attribute __(( __cdecl__)) -D__declspec(x)=__attribute__((x)) -D__CYGWIN32__ -D__CYGWIN__ - Duni x -D__unix__ -D__unix -isystem /usr/local/include -idirafter /usr/include -idira fter /usr/include/w32api cprogram.c /cygdrive/c/WINDOWS/TEMP/ccpUMpgI.i cc1.exe *** /usr/lib/gcc-lib/i686-pc-cygwin/2.95.3-5/cc1.exe /cygdrive/c/WINDOWS/TEMP/ccpUM pgI.i -quiet -dumpbase cprogram.c -version -o /cygdrive/c/WINDOWS/TEMP/ccQWXPQA. s ** as.exe /usr/lib/gcc-lib/i686-pc-cygwin/2.95.3-5/../../../../i686-pc-cygwin/bin/as.e xe -o /cygdrive/c/WINDOWS/TEMP/ccZB1x2B.o /cygdrive/c/WINDOWS/TEMP/ccQWXPQA.s * collect2.exe * /usr/lib/gcc-lib/i686-pc-cygwin/2.95.3-5/collect2.exe -Bdynamic --dll-search -pr efix=cyg -o cprogram.exe /usr/lib/crt0.o -L/usr/local/lib -L/usr/lib -L/usr/lib/ w32api -L/usr/lib/gcc-lib/i686-pc-cygwin/2.95.3-5 /cygdrive/c/WINDOWS/TEMP/ccZB1 x2B.o -lgcc -lcygwin -luser32 -lkernel32 -ladvapi32 -lshell32 -lgcc *** However, if I run these programs with the given parameters (exactly) manually, it shows that already cpp0.exe (the preprocessor) creates the following output: * BASH: syntax error near unexpected token `-Asystem(w' * Has anybody an idea? -- 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/
Bash Scripts
Cygwin developers, I am running cygwin on a NT box. I am trying to create a script which will rcp files in a directory from one host to another. After inserting the appropriate commands, I return to the prompt and type the file name. But nothing happens, I simply get another prompt. Can You think of a reason for this. The script contains the following !#/bin/bash rcp f:/clarify/*.txt 155.201.191.102:/mydir permissions on script are; -rwxr-xr-x 1 abramk None 44 Dec 3 15:33 test Thanks Kevin This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. -- 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: questions on dlopen
On Wed, Dec 05, 2001 at 02:45:04PM +0100, [EMAIL PROTECTED] wrote: I try to port a tool 'ccmalloc' for detection of memory leaks to Win32 via cygwin. At the moment this tool is known to compile on Linux and Solaris only. If you want to have a look on it: http://www.inf.ethz.ch/personal/biere/projects/ccmalloc/ You can also try ElectricFence, which checks for bad memory accesses; see my revised patch here: http://sources.redhat.com/ml/cygwin/2001-11/msg00269.html which also has a link to the earlier discussion of how Vadim Egorov originally patched ElectricFence (which may help you in porting ccmalloc to Cygwin). John -- John Peacock Director of Information Research and Technology Rowman Littlefield Publishing Group 4720 Boston Way Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5747 -- 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: dll not found, bad entry point problems
Bob Calco wrote: Hello all: I'm a windows guy, trying out this Cygwin thing. I downloaded cygwin on both my laptop and my desktop, with all the devel tools and such and a bunch of utilities. I'm having problems on my laptop -- which has the same version of just about everything as my desktop -- that I'm not having on my desktop. 1. Typing vim [enter] in the bash shell (to attempt to run the VIM editor) warns me ominously that The procedure entry point bind_textdomain_codeset could not be located in the dynamic link library cygintl.dll. 2. Typing cvs -? [enter] in the bash shell (to attempt to run CVS help (or any other CVS option)) complains that The dynamic link library libgdbm.dll could not be found in the specified path. WRT # 1, this is not a problem on my desktop. Known setup bug. 28th time this has been reported/asked about this week. run setup again on your laptop. It will update your system to the most recent versions -- the bug was it installed OLD versions (of cygintl.dll, for instance). WRT # 2, I did a search for the libgdbm.dll on both machines and found, in both cases, the libgdbm.dll.a file in the cygwin/lib directory. You're looking for cygwin/bin/cyggdbm.dll. If it isn't there, reinstall the gdbm package. If it IS there, then you need to add C:\cygwin\bin to your SYSTEM path. --Chuck -- 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: -mno-cygwin and SDL
mailbox:/C|/Program Files/Netscape/Users/earnie_boyd/Mail/Inbox.sbd/Cygwin.sbd/Cygwin Users?id=1007584625.12707.ezmlm%40cygwin.comnumber=15322648part=1.31 I just had this discussion this morning on cygwin-apps. You can't add -I/usr/include when using -mno-cygwin. -mno-cygwin causes the MinGW header files to be used and not Cygwin's on purpose. Circumventing that will cause you to fail. MinGW only supports ANSI C as MS sees it with a few add-ons. DON'T -I/usr/include WHEN USING -mno-cygwin. Earnie. ---BeginMessage--- [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: Hi, I downloaded and compiled SDL-1.2.3 from source in cygwin, and suprisingly I got it to work. Then I tried to set -mno-cygwin so that the app would work outside of Cygwin, but I get: $ make win gcc test1.C -mno-cygwin -I /usr/include -lglut32 -lglu32 -lopengl32 -lSDL -o exec/test1.exe The line above should be changed like this: gcc test1.C -mno-cygwin -I /usr/include -o exec/test1.exe -lglut32 -lglu32 -lopengl32 -lSDL Read the FAQ on cygwin.com it contains a topic on WinMain@16. I tried your suggestion, but I get the same error. I also looked at the FAQ, it did not give me any clues either. Shawn Lindberg ---End Message--- -- 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: Bash Scripts
The script should start #!/bin/bash, not !#/bin/bash ;-) -Collin On Wed, 5 Dec 2001 [EMAIL PROTECTED] wrote: Cygwin developers, I am running cygwin on a NT box. I am trying to create a script which will rcp files in a directory from one host to another. After inserting the appropriate commands, I return to the prompt and type the file name. But nothing happens, I simply get another prompt. Can You think of a reason for this. The script contains the following !#/bin/bash rcp f:/clarify/*.txt 155.201.191.102:/mydir permissions on script are; -rwxr-xr-x 1 abramk None 44 Dec 3 15:33 test Thanks Kevin This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. -- 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/ -- 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: Bash Scripts
As someone has already pointed out !#/bin/bash should be #!/bin/bash. It looks like your problem is that your script is named test. Try typing ./test and then try man test --Mark - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, December 05, 2001 4:41 PM Subject: Bash Scripts Cygwin developers, I am running cygwin on a NT box. I am trying to create a script which will rcp files in a directory from one host to another. After inserting the appropriate commands, I return to the prompt and type the file name. But nothing happens, I simply get another prompt. Can You think of a reason for this. The script contains the following !#/bin/bash rcp f:/clarify/*.txt 155.201.191.102:/mydir permissions on script are; -rwxr-xr-x 1 abramk None 44 Dec 3 15:33 test Thanks Kevin This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. -- 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/ -- 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/
cygwin-1.3.6-4 released
I'm back home and took a look at the completion bug. The fix was simple so I released a new version of cygwin. Thanks, Robert, for providing precise instructiosn for duplicating the problem. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: experimental texmf packages
Robert Collins wrote: do porting. So the point is that if RPM had been contributed, and you maintain *just that one package* as an official package (Hey, Chuck this goes for you too :}) Yeah, but I don't have that itch. Sorry, but I don't really *care* about rpm itself. I just liked the multidirectory format it used to separate the various source code/build script pieces, which is why my original packaging proposal said things like /usr/src/cygwin/SPECS/ and whatnot. I also got somewhat frustrated with it about a year ago. I was working quite a bit with Michael Ring, who was *supposed* to provide official dllized ports of berk db, and then provide a port of rpm, but he wandered off into the weeds and I haven't heard anything about that since Nov 2000. He did port some stuff and put it in a private directory on sourceware in Sep 2000 (check cygwin-apps archive), but nothing since then... Anyway, that experience kinda burned me on the whole hey guys let's all use rpm bandwagon... --Chuck -- 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: No username for userid?
try mkpasswd -l /etc/passwd -Collin Descartes was sitting in a bar. The bartender comes up and asks if he wants another. I think not, he says, and promptly vanishes. On Wed, 5 Dec 2001, Daniel Rosenzweig wrote: I just installed (using setup.exe) cygwin on an NT 4 machine The sh prompt tells me that I don't have a username --- when I do an 'id' I get a uid, but no name... when I try to rlogin (even with -l )it tells me that I don't have a username... I have a $USERNAME btw. There is no /etc/passwd file... Any ideas how can I get a username! (Are there really 'logins' for Cygwin?) Thanks. - Daniel Rosenzweig [EMAIL PROTECTED] The URLs below are placed by NetZero - not me. Sign Up for NetZero Platinum Today Only $9.95 per month! http://my.netzero.net/s/signup?r=platinumrefcd=PT97 -- 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/ -- 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/
cygwin 1.3.6-3 and xemacs
I read on this list that someone else had problems with xemacs crashing with 1.3.6. Here is my experience with 1.3.6-3 and xemacs 21.4.5: anytime I try to visit a file, xemacs simply exits with code 1. It doesn't crash (at least according to gdb). It simply exits. Going back to 1.3.5-x fixes the problem. I'll try and figure out some more info and get back to the list with it. -- Ryan T. Sammartino ([EMAIL PROTECTED]) http://members.shaw.ca/ryants/ In every non-trivial program there is at least one bug. -- 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: No longer can compile w/ -mno-cygwin
I had the same problem and discovered that /usr/include/mingw and /usr/lib/mingw were essentially empty. I corrected the problem by re-installing the mingw and mingw-runtime packages (in the Devel group). HTH, Dave Weber, Neil wrote: I just upgraded my Cygwin installation and the C++ program that I used to compile no longer compiles. -- 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: Debug version of cygwin dll
Hallo Polley, Am 2001-12-05 um 22:30 schriebst du: ./configure make if this is the incorrect way to do it? This script is from Ch. Wilson (The Master of Puppets;) Ciao, Gerrit P. Haasemailto:[EMAIL PROTECTED] -- =^..^= cygwin-build 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: Benchmarking tools
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Piyush Kumar Sent: Wednesday, December 05, 2001 5:26 AM To: Cygwin@Cygwin. Com Subject: Benchmarking tools Anyone has any compilation of any benchmarking tools like lmbench on cygwin? Look into the thread http://cygwin.com/ml/cygwin/2001-11/msg01903.html Regards Ralf Habacker Thanks, --Piyush -- 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/ -- 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: problem with make (from cygwin-apps)
-Original Message- From: Robert Collins [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 05, 2001 2:03 PM To: Ralf Habacker; [EMAIL PROTECTED] Subject: Re: problem with make - Original Message - From: Ralf Habacker [EMAIL PROTECTED] ... Does anyone have an idea for fixing this ? I have no problem to fix this, if somebody could give me a direction where I have to look on. ... Also, please use [EMAIL PROTECTED] for this type of bug reporting. This is not an applicable topic for cygwin-apps. From the mailing list page: cygwin-apps: a by-approval developers list for discussing issues regarding applications that are distributed with the Cygwin DLL. Is make an application distributed with cygwin ? :-) Yes, but you missed the REST of the paragraph: This list is intended for discussing solutions. It is not for it would be nice type of musings. Use the main cygwin mailing list for that. Copmare that with cygwin: a high volume list for discussion of just about all things Cygwin-related. If you have questions about how to use Cygwin, or any of its tools (bash, gcc, make, etc.), this is the list for you. There is one exception to the all things cygwin nature of this list: questions about the Cygwin XFree86 project should go to the cygwin-xfree mailing list (see below). Are you saying that the text about cygwin-apps is confusing? The only problem may be to identify the category. Somebody think this is a bug (as I have done), and others say this is a feature. Perhaps it is both. Now after I have recognized the true reason for this, I'm thinking this is a feature, because this isn't a bug of make and your right. So please, would you move this thread to cygwin. Regards Ralf -- 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: Old Thread: Cygwin Performance
-Original Message- From: Tim Prince [mailto:[EMAIL PROTECTED]] Sent: Sunday, December 02, 2001 10:58 PM To: Ralf Habacker Cc: Cygwin Subject: Re: Old Thread: Cygwin Performance The QueryPerformance() calls are still giving 1.00 second timing resolution on an AthlonMP box (should be better than 10 microseconds on most other boxes, with correct usage), but their use appears to be truer to the original lmbench than the cygwin gettimeofday() with its 1.00 second resolution. I believed there were deficiencies in the way lmbench uses QueryPerformance(), preserving only 31 bits of clock ticks from the time of initialization, but I didn't succeed in showing any better way. -- 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/
