setup.exe's README patched to mention needed packages bison and flex.
To successfully build setup.exe, after downloading the files via: $ cvs -z3 -d :pserver:[EMAIL PROTECTED]:/cvs/cygwin-apps co setup two additional packages are required. These packages are bison and flex. I made a patch to the README. $ cvs -z3 -d :pserver:[EMAIL PROTECTED]:/cvs/cygwin-apps diff -uN patch.20070922 and the patch is included below. Hope this helps, Chris Lent [EMAIL PROTECTED] Adjunct Associate Professor of Computer Science, Advisor to First-Year Engineering Students, Manager, Louis and Jeanette Brooks Engineering Design Center (BEDC) Tel: +1.212.353.4350 - Index: setup/README === RCS file: /cvs/cygwin-apps/setup/README,v retrieving revision 2.39 diff -u -r2.39 README --- setup/README21 Feb 2007 07:05:18 - 2.39 +++ setup/README22 Sep 2007 11:20:46 - @@ -6,6 +6,8 @@ - Setup should build out-of-the-box on any Cygwin environment that has all the required packages installed: + - bison + - flex - gcc-mingw-g++ - make - mingw-zlib
RE: Cygwin Installation Problems on Windows Vista (gnuplot.sh, texhash and .bashrc: Bad address)
lent wrote: Hi, Please point out if I'm wrong or misinformed... I'm trying to trace down the Vista cygwin setup.exe /etc/postinstall/gnuplot.sh hang forever at 99% problem. Well, I think I was wrong about pointing fingers at install-info. The install-info was a guess and hunting a bit more we find this lovely weblog: http://conorcahill.blogspot.com/2007/07/cygwin-on-microsoft-vista.html Conor's Web Log of Esoterica: Cygwin on Microsoft Vista In particular: Emphasis added Wednesday, July 04, 2007 http://conorcahill.blogspot.com/2007/07/cygwin-on-microsoft-vista.html Cygwin on Microsoft Vista I've run into a few problems using http://www.cygwin.com Cygwin on http://www.microsoft.com/windows/products/windowsvista/ Microsoft Vista on my new laptop: The installation hung during the post-install step /etc/postinstall/gnuplot.sh. http://www.google.com/search?hl=enamp;q=cygwin+postinstall+hang+gnuplotamp;btnG=Google+Search Researching this problem on the google found an http://www.cygwin.com/ml/cygwin/2007-04/msg00753.html article on the cygwin mailing list which worked around the problem by setting the Windows XP compatibility mode on the installation executable. I wasn't comfortable with this solution as it might cause things to not work well later on Vista. So I poked around a bit, turned on the Command Line output for the Processes tab in the Windows Task Manager and found that the script was hanging on /usr/bin/texhash, which rebuilds a directory listing used by Tex. I was able to run the command successfully on the cygwin command line, but it was still hung in the installation process. So I used Task Manager to kill the texhash process and the installation continued to a later step postinstall-ec-fonts-mftraced.sh where it was trying to run mktexlsr - which is the same program. I again used Task Manager to kill that process and the installation now went on to a succesfull completion. Following the install, I went back and ran the texhash program manually, which did require me to change the mode of the files /var/cache/fonts/ls-R and /usr/share/texmf/ls-R files which had been left read-only when I killed the process. Everything seems to be working fine now. This description matches, and I believe we also saw the postinsall-ec-fonts-mftraced.sh failure as well. Wish I had remember the Command Line option. Darn! Well, so perhaps the culprit is texhash. Or maybe the victim, as I saw another weird thing with this particular install. I had access to the user's machine again and found in /var/log a number of files. $ find . . ./var ./var/log ./var/log/apache2 ./var/log/setup.log ./var/log/setup.log.full ./var/log/setup.log.postinstallXa01604 ./var/log/setup.log.postinstallXa04116 ./var/log/setup.log.postinstallXa04144 ./var/log/setup.log.postinstallXa04492 ./var/log/setup.log.postinstallXa04892 Looking through these we see quite a few messages of the form: /usr/bin/bash: /cygdrive/c/Users/srtg9/.bashrc: Bad address From: /var/log/setup.log.full (starting at line 3239) 2007/09/19 11:15:15 xemacs-mule-sumo 2007/09/19 11:15:15 xemacs-sumo 2007/09/19 11:15:15 xemacs-tags 2007/09/19 11:15:15 xerces-c-devel 2007/09/19 11:15:15 XmHTML 2007/09/19 11:15:15 xpm-nox 2007/09/19 11:15:16 running: C:\cygwin\bin\bash.exe -c /etc/postinstall/gnuplot. sh /usr/bin/bash: /cygdrive/c/Users/srtg9/.bashrc: Bad address 2007/09/19 11:26:55 running: C:\cygwin\bin\bash.exe -c /etc/postinstall/gsl.sh /usr/bin/bash: /cygdrive/c/Users/srtg9/.bashrc: Bad address install-info: menu item `gsl-ref' already exists, for file `gsl-ref' install-info: menu item `gsl-ref' already exists, for file `gsl-ref' install-info: menu item `gsl-ref' already exists, for file `gsl-ref' install-info: menu item `gsl-ref' already exists, for file `gsl-ref' install-info: menu item `gsl-ref' already exists, for file `gsl-ref' install-info: menu item `gsl-ref' already exists, for file `gsl-ref' 2007/09/19 11:27:00 running: C:\cygwin\bin\bash.exe -c /etc/postinstall/gtk+-devel.sh /usr/bin/bash: /cygdrive/c/Users/srtg9/.bashrc: Bad address I am guessing Bad address would result from trying to execve() a .bashrc and getting an EFAULT. The EFAULT seems come from some problem loading the .bashrc (or perhaps the .bashrc filename in an execve() call?). Rather odd :-) Chris still guessing Lent -- View this message in context: http://www.nabble.com/Cygwin-Installation-Problems-on-Windows-Vista-tf3542482.html#a12835293 Sent from the Cygwin Users mailing list archive at Nabble.com. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Cygwin Installation Problems on Windows Vista (killing sh.exe helps)
For getting the installation to keep going, killing off an sh.exe process via Task Manager's End Process, moves things along. This also seems to need to be done for texf (I think that was the name) package. At least we get to the final setup screen this way :-) Chris Lent Kevin Hilton-3 wrote: Here are the two files I found broken on the installation: gnuplot.sh postinstall-ec-fonts-mftraced.sh And just for kicks How do I manually change the passwd and group files. Although under windows Im listed as an administrator, cygwin states my group as none. And Im unable to chmod chgroup these two files. Never had this problem with XP. -- Kevin Hilton -- 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/ -- View this message in context: http://www.nabble.com/Cygwin-Installation-Problems-on-Windows-Vista-tf3542482.html#a12780123 Sent from the Cygwin Users mailing list archive at Nabble.com. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Cygwin Installation Problems on Windows Vista (killing sh.exe helps)
Dave Korn wrote: On 19 September 2007 16:42, lent wrote: Hi Dave, thanks for the quick reply. Sorry, but I wasn't able to find the solution you refer to for the problem of setup.exe hanging in Windows Vista. Where can I find it? For getting the installation to keep going, killing off an sh.exe process via Task Manager's End Process, moves things along. This also seems to need to be done for texf (I think that was the name) package. Hell, you can make the whole thing move along even better, by simply killing 'setup.exe' instead of sh.exe. Sure, it may not be correct, but at least it's fast, eh? Or you could wait for it to finish doing whatever vital job it was doing. Your choice. At least we get to the final setup screen this way :-) Works my way too, *and* with the added advantage you don't end up with a semi-broken installation. I'm new to the cygwin development community and would love to chase this problem down and resolve it once and for all. Is there a way to log the shell scripts as they are run from setup.exe? On the semi-broken installation: Actually, the problem was that the whatever vital job that /etc/postinstall/gnuplot.sh was doing never completed. 30 minutes of wait time by multiple Vista users on multiple brands of spanking new laptops indicates some sort of interaction bug of these shell scripts (or the programs they run) with the wonders of Vista. This hang at 99% forever symptom persists even with setting the Properties of setup.exe to run in Windows XP(SP2) compatibility mode. It's a very disappointing installation experience for novice programmers. Our XP and Windows 2000 users do not have these problems as setup.exe completes just fine. Do I want to kill any part of a carefully crafted installation process? Of course not :-) The problem is if the user kills setup.exe, they wind up with a more broken installation, and lack the Cygwin Desktop icon and the Cygwin Start Menu entry. Killing sh.exe (hopefully the right one) moves the installation process past the block of /etc/postinstall/gnuplot.sh. Our reason for using Cygwin is to teach young engineering students about C programming in a command line environment. If they can't install it on their brand new laptop, I have a difficult time having them use it :-) Thanks again for your attention to this annoying bug. Chris Lent cheers, DaveK -- View this message in context: http://www.nabble.com/Cygwin-Installation-Problems-on-Windows-Vista-tf3542482.html#a12786663 Sent from the Cygwin Users mailing list archive at Nabble.com. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Cygwin Installation Problems on Windows Vista (gnuplot.sh and install-info)
Hi,
Please point out if I'm wrong or misinformed...
I'm trying to trace down the Vista cygwin setup.exe
/etc/postinstall/gnuplot.sh hang forever at 99% problem.
The current /etc/postinstall/gnuplot.sh contains the line:
/usr/bin/install-info --dir-file=/usr/share/info/dir
--info-file=/usr/share/info/gnuplot.info.gz
From Googling about, the install-info part seems to be the part of the shell
scripts that is hanging.
The install-info command is supposed to insert the info format information
about gnuplot into the indexing file /usr/share/info/dir. The info
format stuff is basically plain text with ^_'s ('\x1F' characters) as
section markers and ^? (DEL) as field separators in the index at the end of
the info file. The file is GZIP'd, to save space. The gnuplot.info.gz
gunzip's fine on my XP machine, so a corrupt distribution file seems
unlikely.
So perhaps the problem is the install-info.exe program banging into some
Vista difference.
The install-info.exe program seems to be texinfo package, as shown by:
http://cygwin.com/cgi-bin2/package-grep.cgi?grep=install-info.exe
which yields:
http://cygwin.com/cgi-bin2/package-cat.cgi?file=texinfo%2Ftexinfo-4.8a-1grep=install-info.exe
This seems to imply that the package version is something like texinfo
4.8a-1.
Installing the source for the texinfo 4.8a-1 , we find the file:
/usr/src/texinfo-4.8a-1/util/install-info.c
See Lines 604-643 at end of this post:
My guess is that the popen is not working right.
Pipe emulation is often cranky. I can imagine Vista breaking something.
Or perhaps as all postinstall steps are not finished at that point in
setup.exe, so perhaps gzip is unavailable at that point in the setup.exe's
initial environment.
Or perhaps the hang is related to the fact that install-info.exe reads the
entire file into memory, xmalloc'ing along the way.
I expect to have a Vista machine available again soon to check this out.
Any suggestions on best investigative tactics?
Lines 604-643:
if (!compression_program)
compression_program = local_compression_program;
if (data[0] == '\x1f' data[1] == '\x8b')
#if STRIP_DOT_EXE
/* An explicit .exe yields a better diagnostics from popen below
if they don't have gzip installed. */
*compression_program = gzip.exe;
#else
*compression_program = gzip;
#endif
else if(data[0] == 'B' data[1] == 'Z' data[2] == 'h')
#ifndef STRIP_DOT_EXE
*compression_program = bzip2.exe;
#else
*compression_program = bzip2;
#endif
else if(data[0] == 'B' data[1] == 'Z' data[2] == '0')
#ifndef STRIP_DOT_EXE
*compression_program = bzip.exe;
#else
*compression_program = bzip;
#endif
else
*compression_program = NULL;
if (*compression_program)
{ /* It's compressed, so fclose the file and then open a pipe. */
char *command = concat (*compression_program, -cd ,
*opened_filename);
if (fclose (f) 0)
pfatal_with_name (*opened_filename);
f = popen (command, r);
if (f)
*is_pipe = 1;
else
pfatal_with_name (command);
}
else
{ /* It's a plain file, seek back over the magic bytes. */
if (fseek (f, 0, 0) 0)
--
View this message in context:
http://www.nabble.com/Cygwin-Installation-Problems-on-Windows-Vista-tf3542482.html#a12791093
Sent from the Cygwin Users mailing list archive at Nabble.com.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
