Blue screen of death on cygwin+win98+./configure
Hi All, Im trying to install TeXmacs on my win98+cygwin laptop. First I installed the binaries for guile from the cygwin setup (I have XFree and Tex and all associated libs already) downloaded TeXmacs sources, ran ./configure and then gave a "make". I got the blue screen of death (BSD). After iterating through several BSDs, I hunted on the web and found a site that said that static linkages were a problem with the latest guile and that I must install guile 1.4.1. So I uninstalled guile, downloaded the sources for guile 1.4.1, untarred them and ran ./configure --disable-shared It runs through several checks, but never completes - insted it gives me at some point it simply gives me the blue screen of death. This time around Im not even getting past configure. Im not sure what to do now. Any advice at all would be greatly appreciated. Much thanks Bhiksha [EMAIL PROTECTED] P.S: Ive hunted on the web and faqs for answers and couldnt find any. -- 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: BSOD on cygwin
Hi, First I must apologize for my multiple posts earlier. I wasnt sure if the first one had gone through, since I never got a copy myself. So I figured Id messed up and posted again. Anyway, the problem (as I mentioned earlier) is that on my windows 98 machine, with the latest cygwin, I get a blue screen of death when I try to run "configure --disable-shared" on guile-1.4.1. (Im using 1.4.1 because Im tyring to compile TeXmacs). Ive since dug around a bit, crashed my machine a hunded times, and collected logs. I found that the configure script dies on line 4791, at a line that goes "if sort conftest.nm|uniq > conftest.ntM;then" I get an empty conftest.nmT and the machine dies. I tried running the same command from command line. The first time I ran it, my cygwin window froze (although my machine didnt die), but thereafter Ive been able to run it from command line. However, running the configure script kills the machine at the uniq again. Im attaching the configure script, the config.log, and the conftest.nm files (the conftest.nmT file I get is empty). I hope this is not bad practice, but I figure they would help find the problem. The tail of the config.log file should indicate where exactly my machine dies (every time!). Also, as per Igor Pechtchanski's suggestion, I ran a cygcheck -s -v -r and am attaching the output. Curiously, cygcheck -s -v -r gave me output the first time I ran it. Afterwards, running the command simply gives me no output at all - it simply runs silently and comes back. Im not sure why this is so - I was pretty sure it was supposed to repeat the information everytime I ran it. I hope this doesnt indicate a bug with my setup. Many thanks for any and all help in this issue. Regards, Bhiksha [EMAIL PROTECTED] On Sun, Jan 12, 2003 at 10:40:48AM -0500, Igor Pechtchanski wrote: > On Sun, 12 Jan 2003, Igor Pechtchanski wrote: > > > On Sat, 11 Jan 2003, Bhiksha Raj wrote: > > > > > Hi All, > > > > > > I hope this is not the wrong forum for this: > > > > > > Im trying to install TeXmacs on my win98+cygwin laptop. > > > First I installed the binaries for guile from the cygwin setup > > > (I have XFree and Tex and all associated libs already) > > > downloaded TeXmacs sources, ran ./configure and then > > > gave a "make". > > > I got the blue screen of death (BSD). > > > After iterating through several BSDs, I hunted on the web > > > and found a site that said that static linkages were a problem with > > > the latest guile and that I must install guile 1.4.1. So I uninstalled > > > guile, > > > downloaded the sources for guile 1.4.1, untarred them and > > > ran > > > ./configure --disable-shared > > > > > > It runs through several checks, but never completes - insted it > > > gives me at some point it simply gives me the blue screen of death. > > > This time around Im not even getting past configure. > > > > > > Im not sure what to do now. > > > Any advice at all would be greatly appreciated. > > > > > > Much thanks > > > Bhiksha > > > [EMAIL PROTECTED] > > > > Bhiksha, > > > > This is a forum for all problems with Cygwin, so your question fits in > > nicely. To answer it, Cygwin never *causes* a BSOD. It may expose or > > trigger a bug in Windows or some process running with system privileges > > (antivirus programs have been blamed a lot), but Cygwin itself doesn't > > have enough access to the low-level OS to be able to cause a BSOD. > > > > Try turning off your antivirus program(s) and see if it makes the BSOD go > > away. Another possibility is firewall or VPN software. The output of > > 'cygcheck -s -v -r' as a non-inline uncompressed text *attachment* > > wouldn't hurt, either (as indicated in <http://cygwin.com/bugs/>). > > Igor > > P.S. I'm sure you'll get more and better responses on Monday. > > Whoops! Fingers striving to be independent from the brain... Make the > above link <http://cygwin.com/bugs.html> (also at the bottom of every > message). > Igor > -- > http://cs.nyu.edu/~pechtcha/ > |\ _,,,---,,_ [EMAIL PROTECTED] > ZZZzz /,`.-'`'-. ;-;;,_ [EMAIL PROTECTED] > |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski > '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! > > Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk! > -- /usr/games/fortune > > > -- > Unsubscribe info: http://cygwin.co
Re: BSOD on cygwin
Im not sure what happened, but my problem went away. I do not have VPN or an antivirus program running - I turned those off due to some problems with other software earlier. No firewall software either - I have an external DLink firewall. For the record, here's what I did that seemed to fix things: 1. I reinstalled cygwin 1.3.8.1. "cygcheck" ran once after the reinstall, but failed again on subsequent runs. The machine still crashed when I tried to "./configure" guile. 2. The configure script was dying at a "uniq". I tried running uniq on a file, from the command line. It crashed the window (not the machine), with a windows popup message about some dll. I didnt note it down (unfortuntely). 3. I restarted another cygwin window and reran uniq on the same file. This time uniq went through. 4. I reran configure (note that I havent *changed* anything after the earlier run, when the machine crashed). It went through cleanly. 5. I double checked. 'cygcheck' also returns proper results. Since I did not actively modify anything, Im mystified why things went through after I ran uniq on the command line. Thanks, Bhiksha On Sun, Jan 12, 2003 at 07:35:44PM -0500, Larry Hall (RFK Partners, Inc) wrote: > Perhaps someone else running Win98 will be able to confirm or deny > the problems you're seeing. I'm guessing that others will only be > able to 'deny'. As mentioned, BSOD is an O/S issue/bug, which means > it's at least difficult to resolve in application software and is > certainly much better resolved in the O/S itself (or quite possibly > software drivers). Certainly in the case that the problem is caused > by drivers (and AV software uses these too), the problem software is > not necessarily installed on a 'typical' Win 98 machine, which is why > I said I expect others won't be able to confirm your results. I'd > highly recommend following Igor's suggestions. The fact that you > can't get cygcheck to run correctly for you again makes me highly > suspicious that something on your system other than Cygwin is actually > causing your problem. In my opinion, you're more likely to find the > source of your problem by looking outside of Cygwin. > > > > Larry Hall [EMAIL PROTECTED] > RFK Partners, Inc. http://www.rfk.com > 838 Washington Street (508) 893-9779 - RFK Office > Holliston, MA 01746 (508) 893-9889 - FAX > > > At 06:34 PM 1/12/2003, Bhiksha Raj wrote: > >Hi, > > > >First I must apologize for my multiple posts earlier. > >I wasnt sure if the first one had gone through, since I never > >got a copy myself. So I figured Id messed up and posted again. > > > >Anyway, > >the problem (as I mentioned earlier) is that on my windows 98 > >machine, with the latest cygwin, I get a blue screen of death > >when I try to run "configure --disable-shared" on guile-1.4.1. > >(Im using 1.4.1 because Im tyring to compile TeXmacs). > > > >Ive since dug around a bit, crashed my machine a hunded times, > >and collected logs. I found that the configure script dies > >on line 4791, at a line that goes > >"if sort conftest.nm|uniq > conftest.ntM;then" > > > >I get an empty conftest.nmT and the machine dies. > >I tried running the same command from command line. The first time > >I ran it, my cygwin window froze (although my machine didnt die), > >but thereafter Ive been able to run it from command line. > >However, running the configure script kills the machine at the > >uniq again. > > > >Im attaching the configure script, the config.log, and the > >conftest.nm files (the conftest.nmT file I get is empty). > >I hope this is not bad practice, but I figure they would help > >find the problem. > >The tail of the config.log file should indicate where exactly > >my machine dies (every time!). > >Also, as per Igor Pechtchanski's suggestion, I ran a cygcheck -s -v -r and > >am attaching the output. > > > >Curiously, cygcheck -s -v -r gave me output the first time I > >ran it. Afterwards, running the command simply gives me no output > >at all - it simply runs silently and comes back. Im not sure why > >this is so - I was pretty sure it was supposed to repeat the > >information everytime I ran it. I hope this doesnt indicate a > >bug with my setup. > > > >Many thanks for any and all help in this issue. > > > >Regards, > >Bhiksha > >[EMAIL PROTECTED] > > > > > >On Sun, Jan 12, 2003 at 10:40:48AM -0500, Igor Pechtchanski wrote: > > > On Sun,
dlopen() and libtool problems
Hi All, Im trying to compile guile-1.4.1 on my windows98+cygwin box. Ive installed all the latest libtool and auto-make utils. I run ./configure and get the following message (among others) "checking command to parse /usr/bin/nm -B output: failed" configure does find dlopen(), though. When I try to make the guile-1.4.1 package make dies with the following messages: --- libtool: link warning: `AC_LIBTOOL_DLOPEN' not used. Assuming no dlopen support. libtool: link: not configured to extract global symbols from dlreopened files gcc -g -O2 -Wall -Wmissing-prototypes -o guile.exe guile.o -Wl,--export-dynamic ./.libs/libguile.a .libs/libimp-cygltdl-3.a guile.o(.text+0x38): In function `main': /c/users/bhiksha/tmp/guile/guile-1.4.1/libguile/guile.c:74: undefined reference to `_lt_preloaded_symbols' Info: resolving _h_errno by linking to __imp__h_errno (auto-import) collect2: ld returned 1 exit status make[2]: *** [guile.exe] Error 1 I gather this is something to do with libtool(_lt_preloaded_symbols_ is from libtool I think), but Im not sure how to proceed. Any help would be greatly appreciated. Many thanks, Bhiksha -- 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: BSOD on cygwin
> It's also weird that your mount table has root (/) down three times. Twice > as . and once as C:/downloads/cygwin. True, this is strange. the "." mount entries are "binmode,cygdrive" and the c:/downloads/cygwin is only "binmode", but is not a cygdrive. Is there an fstab equivalent in cygwin that I can check? (Im a cygwin novice and dont know where to look) Thanks for the help, Bhiksha -- 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: dlopen() and libtool problems
Hi, I found a post on the gnu archives: http://mail.gnu.org/archive/html/texmacs-dev/2002-11/msg00121.html which stated specifically that guile 1.6.0 is not compatible with TeXmacs (which I want to install). The page says to use guile-1.4.1 The message was posted in Nov 2002, so I assumed the info was fairly recent. I also actually tried guile 1.6.0 right out of the box. When I tried to compile TeXmacs I got errors relating to guile (and the dreaded blue screen of death followed. My machine seems to die when cygwin encounters errors). -Bhiksha On Mon, Jan 13, 2003 at 07:02:43PM +0100, Jan Nieuwenhuizen wrote: > Bhiksha Raj <[EMAIL PROTECTED]> writes: > > > Im trying to compile guile-1.4.1 on my windows98+cygwin box. > > Ive installed all the latest libtool and auto-make utils. > > You are aware that guile-1.6 is included in Cygwin? If you really > need 1.4, you may want to look at the 1.6 source package for clues. > > As an aside, GUILE cvs HEAD should compile without patching. > > Greetings, > Jan. > -- 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/
sort kills cygwin
Hi All, Im having blue screen of death problems all around. I thought I had this beat, but no.. Anyway, Id been having BSOD problems when I ran "configure" for the guile packages. The machine only died when I ran the script, but I could not kill it by running any commands from commmand line. Ive finally isolated a command that kills my machine. Everytime I run "sort" on any data, the machine dies. sort --version does not give me a version number, but rather the node that <-VERSION> is not a file. Any idea why "sort" would cause problems? I have the latest texttools, and most system libraries are new, although I may have some old ones (older than 3 months) Many thanks, Bhiksha -- 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/
