Re: 1.5.18-1 gcc path weirdness
All, Sorry this isn't from my regular mailer ... - Message from x on Mon, 5 Dec 2005 17:33:22 -0600 - To: Subject:Re: 1.5.18-1 gcc path weirdness What does ls -l /usr/bin/*gcc* show you? From bash, it looks like: [EMAIL PROTECTED] /usr/bin $ ls -l /usr/bin/*gcc* -rwxrwxrwx 1 swootton Users 93717 Jun 7 17:02 /usr/bin/gcc.exe -rwxrwxrwx 1 swootton Users 16183 Jun 7 16:13 /usr/bin/gccbug -rwxrwxrwx 1 swootton Users 93717 Dec 5 16:25 /usr/bin/i686-pc-cygwin-gcc-3.4.4.exe lrwxrwxrwx 1 swootton Users 7 Dec 5 16:25 /usr/bin/i686-pc-cygwin-gcc.exe -> gcc.exe All I don't know if anyone noticed the -rwxrwxrwx 1 swootton Users 93717 Jun 7 17:02 /usr/bin/gcc.exe and -rwxrwxrwx 1 swootton Users 93717 Dec 5 16:25 /usr/bin/i686-pc-cygwin-gcc-3.4.4.exe lrwxrwxrwx 1 swootton Users 7 Dec 5 16:25 /usr/bin/i686-pc-cygwin-gcc.exe -> gcc.exe lines.. Could it be possible that you are running the Jun 7 version of gcc.exe when you are thinking that you are running the gcc pointed to by the symlink? As a WAG I think you might be and bash/cygwin is trying to figure out which command to ** actually ** use. Alan _ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ -- 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/
Question regarding perl and perl-libwin32 using the latest cygwin ... and an anomaly
All,
Is there a solution to the problem of having to use
perl -I /usr/lib/perl5/site_perl/5.8.2/cygwin-thread-multi-64int/
when executing any examples, or use the facilities in perl-libwin32. See an
example below:
[EMAIL PROTECTED] /usr/share/doc/perl-libwin32-0.191/Sound$ ./test.pl
use: not found
File '\nWin32::Sound version ,' [ '/nWin32::Sound version ,' ] does ** NOT
** exist - skipping printing this file.
File '::Sound::VERSION,' [ '::Sound::VERSION,' ] does ** NOT ** exist -
skipping printing this file.
File ' Test Program\n' [ '/usr/share/doc/perl-libwin32-0.191/Sound/ Test
Program/n' ] does ** NOT ** exist - skipping printing this file.
Finished.
File 'by Aldo Calpini <[EMAIL PROTECTED]>\n\n' [
'/usr/share/doc/perl-libwin32-0.191/Sound/by Aldo Calpini
<[EMAIL PROTECTED]>/n/n' ] does ** NOT ** exist - skipping printing this file.
Finished.
File 'Playing 'welcome.wav' synchronously...' [
'/usr/share/doc/perl-libwin32-0.191/Sound/Playing 'welcome.wav'
synchronously...' ] does ** NOT ** exist - skipping printing this file.
Finished.
./test.pl: 7: Syntax error: "(" unexpected
Note: This generates an error.
[EMAIL PROTECTED] /usr/share/doc/perl-libwin32-0.191/Sound$ perl -I
/usr/lib/perl5/site_perl/5.8.2/cygwin-thread-multi-64int/ test.pl
Win32::Sound version 0.47 Test Program
by Aldo Calpini <[EMAIL PROTECTED]>
Playing 'welcome.wav' synchronously...OK
Playing 1 second of 'welcome.wav' asynchronously...OK
Stopping sound...OK
Playing system exit sound...OK
Now it doesn't (and the sound played fine).
This is true of all the other examples under
/usr/share/doc/perl-libwin32-0.191. This tells me that I must either use the
perl -I... syntax to use the new library routines, or put this in the magic
line (haven't tried this, so I don't know if it will work - I would assume
it would).
[EMAIL PROTECTED] /usr/share/doc/perl-libwin32-0.191/Win32CORE/tests$
$ perl -I /usr/lib/perl5/site_perl/5.8.2/cygwin-thread-multi-64int/
win32core.pl
1..1
# Running under perl version 5.008002 for cygwin
# Current time local: Tue Jan 20 18:30:33 2004
# Current time GMT: Tue Jan 20 18:30:33 2004
# Using Test.pm version 1.24
ok 1
[EMAIL PROTECTED] /usr/share/doc/perl-libwin32-0.191/Win32CORE/tests$ date
Tue Jan 20 12:31:01 CST 2004
[EMAIL PROTECTED] /usr/share/doc/perl-libwin32-0.191/Win32CORE/tests$
The date/time stamp reported by win32core.pl doesn't make any sense - the
GMT does, NOT the local - I am on Central US time (as reported by date).
_
Alan Miles
ICQ#: 171006836
More ways to contact me: http://wwp.icq.com/171006836
_
--
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/
Problem with latest cygwin dll ... bash doesn't shutdown properly
All, I know that you want uncompressed attachments, but I got this when I tried doing this. Thus I gzipped them and are attaching them: Hi. This is the qmail-send program at sources.redhat.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. <[EMAIL PROTECTED]>: ezmlm-reject: fatal: Sorry, I don't accept messages larger than 10 bytes (#5.2.3) --- Enclosed are the original headers of the message. Please read below ... -----Original Message- From: Alan Miles [mailto:[EMAIL PROTECTED] Sent: January 20, 2004 23:07 To: [EMAIL PROTECTED] Subject: Problem with latest cygwin dll ... bash doesn't shutdown properly All, Prior to the latest cygwin dll release, when I typed exit in the bash console, cygwin shutdown. Now it just hangs. It won't even execute some umount commands I have in .bash_logout script. When I check the task manager, umount doesn't even appear. I renamed .bash_logout to bash_logout to temporarily disable the command, and I still get this freeze. Attached is the cygcheck outputs - one for the version that did work fine, one for the version that doesn't. Note: The following is the diff between the two (and there is very little different): 3c3 < Current System Time: Tue Jan 20 06:35:17 2004 --- > Current System Time: Tue Jan 20 11:21:08 2004 38,39c38,39 < 513(None)544(Administrators) < 545(Users) --- > 0(root) 513(None) > 544(Administrators) 545(Users) 46c46 < PWD = `/mnt/Drives/H/TransferDir/Download' --- > PWD = `/mnt/Drives/H' 693,694c693,694 < 949k 2003/09/20 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0 < "cygwin1.dll" v0.0 ts=2003/9/20 15:31 --- > 1085k 2004/01/19 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0 > "cygwin1.dll" v0.0 ts=2004/1/18 23:43 696c696 < DLL version: 1.5.5 --- > DLL version: 1.5.6 702c702 < API minor: 94 --- > API minor: 108 713,714c713,714 < Build date: Sat Sep 20 16:31:15 EDT 2003 < CVS tag: cr-0x9b --- > Build date: Mon Jan 19 00:43:36 EST 2004 > CVS tag: cr-0x9d 842c842 < cygwin 1.5.5-1 --- > cygwin 1.5.6-1 909a910 > gtypist 2.7-1 1039a1041 > perl-libwin32 0.191-1 _ Alan Miles ICQ#: 171006836 More ways to contact me: http://wwp.icq.com/171006836 _ cygcheck.out_doesnt_work.gz Description: Binary data cygcheck.out_works.gz Description: Binary data -- 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/
Diff for generic readme and generic-build script to automatically generate pkg data and file listings
All,
Was wondering if this patch got dropped, or is it on a todo list?
Alan
-Original Message-
From: Alan Miles [mailto:[EMAIL PROTECTED]
Sent: November 21, 2003 18:35
To: [EMAIL PROTECTED]
Subject: RE: Diff for generic readme and generic-build script
Igor,
New patch - basically I store the /usr/bin/basename of the Readme file
variable == > /tmp/%PKG%.README
Then I do an effective "mv -f /tmp/%PKG%.README
/usr/share/doc/Cygwin/%PKG%.README" operation. Hopefully that mitigates all
of your concerns.
-Original Message-
From: Igor Pechtchanski [mailto:[EMAIL PROTECTED]
Sent: November 19, 2003 11:55
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: Diff for generic readme and generic-build script
Alan,
The bug with 'sed -i' was that if it's unable to write to (or, rather,
"creat") "/tmp/sedGARBAGE", it assumes that the file exists and tries
another name ("/tmp/sedMOREGARBAGE"), and so on (in a loop). If /tmp is
not writeable at all, sed will loop indefinitely. As long as your script
checks only once (and redirection is usually better at handling existing
files, since you never claimed your script is reentrant), you should be
ok. You can simply replace "${ThePackageReadMeFile}.tmp" in your patch
with "/tmp/${ThePackageReadMeFile}.tmp" (or even "`mktemp -t
"${ThePackageReadMeFile}.XXXXXX"`", but you'd need to store that in a
variable).
Igor
On Tue, 18 Nov 2003, Alan Miles wrote:
> Igor,
>
> With this change I discovered a very subtle problem - the files listed
will
> show two entries instead of one for the README:
>
> /usr/share/doc/Cygwin/%PKG%.README
> /usr/share/doc/Cygwin/%PKG%.README.tmp
>
> This is due to the way where I redirected the file to.
>
> There are two solutions:
> 1/ Put the redirected temp file under /tmp, i.e., /tmp/%PKG%.README and
then
> doing a 'mv -f /tmp/%PKG%.README /usr/share/doc/Cygwin/%PKG%.README'. The
> listing won't be affected since before and after will contain the same
file
> name.
>
> 2/ Adjusting the find command to filter-out the
> /usr/share/doc/Cygwin/%PKG%.README.tmp file in its listing.
>
> Which solution would be your preference? (Unless you have another one of
> course ...)
>
> Alan
packaging_templates.diff
Description: Binary data
--
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: Diff for generic readme and generic-build script
Igor,
New patch - basically I store the /usr/bin/basename of the Readme file
variable == > /tmp/%PKG%.README
Then I do an effective "mv -f /tmp/%PKG%.README
/usr/share/doc/Cygwin/%PKG%.README" operation. Hopefully that mitigates all
of your concerns.
-Original Message-
From: Igor Pechtchanski [mailto:[EMAIL PROTECTED]
Sent: November 19, 2003 11:55
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: Diff for generic readme and generic-build script
Alan,
The bug with 'sed -i' was that if it's unable to write to (or, rather,
"creat") "/tmp/sedGARBAGE", it assumes that the file exists and tries
another name ("/tmp/sedMOREGARBAGE"), and so on (in a loop). If /tmp is
not writeable at all, sed will loop indefinitely. As long as your script
checks only once (and redirection is usually better at handling existing
files, since you never claimed your script is reentrant), you should be
ok. You can simply replace "${ThePackageReadMeFile}.tmp" in your patch
with "/tmp/${ThePackageReadMeFile}.tmp" (or even "`mktemp -t
"${ThePackageReadMeFile}.XXXXXX"`", but you'd need to store that in a
variable).
Igor
On Tue, 18 Nov 2003, Alan Miles wrote:
> Igor,
>
> With this change I discovered a very subtle problem - the files listed
will
> show two entries instead of one for the README:
>
> /usr/share/doc/Cygwin/%PKG%.README
> /usr/share/doc/Cygwin/%PKG%.README.tmp
>
> This is due to the way where I redirected the file to.
>
> There are two solutions:
> 1/ Put the redirected temp file under /tmp, i.e., /tmp/%PKG%.README and
then
> doing a 'mv -f /tmp/%PKG%.README /usr/share/doc/Cygwin/%PKG%.README'. The
> listing won't be affected since before and after will contain the same
file
> name.
>
> 2/ Adjusting the find command to filter-out the
> /usr/share/doc/Cygwin/%PKG%.README.tmp file in its listing.
>
> Which solution would be your preference? (Unless you have another one of
> course ...)
>
> Alan
packaging_templates.diff
Description: Binary data
--
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: Diff for generic readme and generic-build script
Igor, With this change I discovered a very subtle problem - the files listed will show two entries instead of one for the README: /usr/share/doc/Cygwin/%PKG%.README /usr/share/doc/Cygwin/%PKG%.README.tmp This is due to the way where I redirected the file to. There are two solutions: 1/ Put the redirected temp file under /tmp, i.e., /tmp/%PKG%.README and then doing a 'mv -f /tmp/%PKG%.README /usr/share/doc/Cygwin/%PKG%.README'. The listing won't be affected since before and after will contain the same file name. 2/ Adjusting the find command to filter-out the /usr/share/doc/Cygwin/%PKG%.README.tmp file in its listing. Which solution would be your preference? (Unless you have another one of course ...) Alan -Original Message----- From: Alan Miles [mailto:[EMAIL PROTECTED] Sent: November 18, 2003 19:05 To: [EMAIL PROTECTED] Subject: RE: Diff for generic readme and generic-build script Igor, Fixed the script patch as per your comment about -i. The `e [COMMAND]' is still valid, as replacing it with 'r -' did not work. Alan -Original Message- From: Igor Pechtchanski [mailto:[EMAIL PROTECTED] Sent: November 18, 2003 13:02 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Diff for generic readme and generic-build script On Mon, 17 Nov 2003, Alan Miles wrote: > [snip] > 7/ Note: the -i option to sed (quoting the man page for sed): > >-i[suffix], --in-place[=suffix] >edit files in place (makes backup if extension supplied) > >Extended sed command: > >`e [COMMAND]' > This command allows one to pipe input from a shell command into > pattern space. Without parameters, the `e' command executes the > command that is found in pattern space and replaces the pattern > space with the output; a trailing new-line is suppressed. > > If a parameter is specified, instead, the `e' command interprets > it as a command and sends it to the output stream (like `r' does). > The command can run across multiple lines, all but the last > ending with a back-slash. > > In both cases, the results are undefined if the command to be > executed contains a NUL character. > >These together constitute the operation of the modifications. Note: the -i option to sed is buggy, as it will go into an infinite loop if /tmp is not writable (which does happen occasionally with Cygwin). It's better to use explicit redirection and renaming instead. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton -- 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: Diff for generic readme and generic-build script
Igor, Fixed the script patch as per your comment about -i. The `e [COMMAND]' is still valid, as replacing it with 'r -' did not work. Alan -Original Message- From: Igor Pechtchanski [mailto:[EMAIL PROTECTED] Sent: November 18, 2003 13:02 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Diff for generic readme and generic-build script On Mon, 17 Nov 2003, Alan Miles wrote: > [snip] > 7/ Note: the -i option to sed (quoting the man page for sed): > >-i[suffix], --in-place[=suffix] >edit files in place (makes backup if extension supplied) > >Extended sed command: > >`e [COMMAND]' > This command allows one to pipe input from a shell command into > pattern space. Without parameters, the `e' command executes the > command that is found in pattern space and replaces the pattern > space with the output; a trailing new-line is suppressed. > > If a parameter is specified, instead, the `e' command interprets > it as a command and sends it to the output stream (like `r' does). > The command can run across multiple lines, all but the last > ending with a back-slash. > > In both cases, the results are undefined if the command to be > executed contains a NUL character. > >These together constitute the operation of the modifications. Note: the -i option to sed is buggy, as it will go into an infinite loop if /tmp is not writable (which does happen occasionally with Cygwin). It's better to use explicit redirection and renaming instead. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton packaging_templates.diff Description: Binary data -- 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/
Diff for generic readme and generic-build script
All, Based on the 1.8 version of the generic build script I would like to submit this patch, which would: 1/ the option "all" does not call "list". The fix in the patch does. 2/ The patches to both file let the PKG, VER, and REL variables in the README be automatically be filled in by the script - then maintainers won't have to manually do this. 3/ This patch fulfills the wish to have the file names be automatically be placed in the README prior to binary/src build releases. The 1.8 version heads in that direction, but the functionality isn't there. 4/ I have defined a NEWVER variable to handle the part of the original README 5/ Defined a new export variable: 'ThePackageReadMeFile' which defines the Package README file name (saves defining it twice) - both 'list' and 'install' use it 6/ I haven't renamed the routine "list", which it should be since it is a "package" readme editor 7/ Note: the -i option to sed (quoting the man page for sed): -i[suffix], --in-place[=suffix] edit files in place (makes backup if extension supplied) Extended sed command: `e [COMMAND]' This command allows one to pipe input from a shell command into pattern space. Without parameters, the `e' command executes the command that is found in pattern space and replaces the pattern space with the output; a trailing new-line is suppressed. If a parameter is specified, instead, the `e' command interprets it as a command and sends it to the output stream (like `r' does). The command can run across multiple lines, all but the last ending with a back-slash. In both cases, the results are undefined if the command to be executed contains a NUL character. These together constitute the operation of the modifications. _ Alan Miles ICQ#: 171006836 More ways to contact me: http://wwp.icq.com/171006836 _ packaging_templates.diff Description: Binary data -- 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: cygpath hangs from postinstall scripts when called like $(cygpath -S) but not otherwise
s/Win200 SP4/Win2000 SP4/g -Original Message- From: Alan Miles [mailto:[EMAIL PROTECTED] Sent: October 5, 2003 20:41 To: [EMAIL PROTECTED] Subject: RE: cygpath hangs from postinstall scripts when called like $(cygpath -S) but not otherwise All, Just to add another wrinkle: See messages: http://cygwin.com/ml/cygwin/2003-10/msg00203.html and: http://cygwin.com/ml/cygwin/2003-10/msg00202.html http://sources.redhat.com/ml/cygwin/2003-09/msg01821.html http://sources.redhat.com/ml/cygwin/2003-09/msg01823.html I did the following: 1/Copied strace into a separate area outside the cygwin tree, i.e., "H:\CygnusSolutions-Cygwin Files\strace.exe" 2/Completely uninstalled cygwin 3/Removed any remaining directory entries 4/Removed any registry entries 5/Created a Windows program shortcut "H:\CygnusSolutions-Cygwin Files\strace.exe" -o "H:\CygnusSolutions-Cygwin Files\strace.setup.txt" "H:\CygnusSolutions-Cygwin Files\setup.exe" (so I could create an strace output) 6/ Double-clicked on this shortcut. $ cygcheck /usr/bin/cygpath.exe H:/cygwin/bin/cygpath.exe H:/cygwin/bin\cygwin1.dll C:\WINNT\system32\KERNEL32.dll C:\WINNT\system32\NTDLL.DLL C:\WINNT\system32\SHELL32.DLL C:\WINNT\system32\GDI32.DLL C:\WINNT\system32\USER32.DLL C:\WINNT\system32\ADVAPI32.DLL C:\WINNT\system32\RPCRT4.DLL C:\WINNT\system32\SHLWAPI.DLL C:\WINNT\system32\msvcrt.dll C:\WINNT\system32\COMCTL32.DLL I too am running Win200 SP4. The same files, on the same machine, which previously failed, now installed fine, albeit very slowly. Thought I would add my 2c worth. Alan -Original Message- From: Igor Pechtchanski [mailto:[EMAIL PROTECTED] Sent: October 4, 2003 09:52 To: Cliff Hones Cc: [EMAIL PROTECTED] Subject: Re: cygpath hangs from postinstall scripts when called like $(cygpath -S) but not otherwise On Sat, 4 Oct 2003, Cliff Hones wrote: > I ran cygcheck on cygpath, and was surprised to discover > that it has a dependence on msvcrt (as well as cygwin1): > > $ cygcheck /bin/cygpath.exe > D:/cygwin/bin/cygpath.exe > D:/cygwin/bin\cygwin1.dll > D:\WINNT\system32\KERNEL32.dll > D:\WINNT\system32\NTDLL.DLL > D:\WINNT\system32\SHELL32.DLL > D:\WINNT\system32\GDI32.DLL > D:\WINNT\system32\USER32.DLL > D:\WINNT\system32\ADVAPI32.DLL > D:\WINNT\system32\RPCRT4.DLL > D:\WINNT\system32\SHLWAPI.DLL > D:\WINNT\system32\msvcrt.dll > D:\WINNT\system32\COMCTL32.DLL > > I thought that using the msvcrt and cygwin1 dll's in > the same executable was likely to cause crashes or hangs - > is this no longer the case, or could this be the problem > with the postinstall? > > -- Cliff Wow! Good thinking, Cliff! I think you may be on to something... ISTM that the problem could manifest itself when running from setup as opposed to from the shell because setup is a Windows program, so some MSVCRT functions may be found before the Cygwin ones... We could test by using "cygstart cygpath" or "run cygpath" or something. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton -- 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: cygpath hangs from postinstall scripts when called like $(cygpath -S) but not otherwise
All, Just to add another wrinkle: See messages: http://cygwin.com/ml/cygwin/2003-10/msg00203.html and: http://cygwin.com/ml/cygwin/2003-10/msg00202.html http://sources.redhat.com/ml/cygwin/2003-09/msg01821.html http://sources.redhat.com/ml/cygwin/2003-09/msg01823.html I did the following: 1/Copied strace into a separate area outside the cygwin tree, i.e., "H:\CygnusSolutions-Cygwin Files\strace.exe" 2/Completely uninstalled cygwin 3/Removed any remaining directory entries 4/Removed any registry entries 5/Created a Windows program shortcut "H:\CygnusSolutions-Cygwin Files\strace.exe" -o "H:\CygnusSolutions-Cygwin Files\strace.setup.txt" "H:\CygnusSolutions-Cygwin Files\setup.exe" (so I could create an strace output) 6/ Double-clicked on this shortcut. $ cygcheck /usr/bin/cygpath.exe H:/cygwin/bin/cygpath.exe H:/cygwin/bin\cygwin1.dll C:\WINNT\system32\KERNEL32.dll C:\WINNT\system32\NTDLL.DLL C:\WINNT\system32\SHELL32.DLL C:\WINNT\system32\GDI32.DLL C:\WINNT\system32\USER32.DLL C:\WINNT\system32\ADVAPI32.DLL C:\WINNT\system32\RPCRT4.DLL C:\WINNT\system32\SHLWAPI.DLL C:\WINNT\system32\msvcrt.dll C:\WINNT\system32\COMCTL32.DLL I too am running Win200 SP4. The same files, on the same machine, which previously failed, now installed fine, albeit very slowly. Thought I would add my 2c worth. Alan -Original Message- From: Igor Pechtchanski [mailto:[EMAIL PROTECTED] Sent: October 4, 2003 09:52 To: Cliff Hones Cc: [EMAIL PROTECTED] Subject: Re: cygpath hangs from postinstall scripts when called like $(cygpath -S) but not otherwise On Sat, 4 Oct 2003, Cliff Hones wrote: > I ran cygcheck on cygpath, and was surprised to discover > that it has a dependence on msvcrt (as well as cygwin1): > > $ cygcheck /bin/cygpath.exe > D:/cygwin/bin/cygpath.exe > D:/cygwin/bin\cygwin1.dll > D:\WINNT\system32\KERNEL32.dll > D:\WINNT\system32\NTDLL.DLL > D:\WINNT\system32\SHELL32.DLL > D:\WINNT\system32\GDI32.DLL > D:\WINNT\system32\USER32.DLL > D:\WINNT\system32\ADVAPI32.DLL > D:\WINNT\system32\RPCRT4.DLL > D:\WINNT\system32\SHLWAPI.DLL > D:\WINNT\system32\msvcrt.dll > D:\WINNT\system32\COMCTL32.DLL > > I thought that using the msvcrt and cygwin1 dll's in > the same executable was likely to cause crashes or hangs - > is this no longer the case, or could this be the problem > with the postinstall? > > -- Cliff Wow! Good thinking, Cliff! I think you may be on to something... ISTM that the problem could manifest itself when running from setup as opposed to from the shell because setup is a Windows program, so some MSVCRT functions may be found before the Cygwin ones... We could test by using "cygstart cygpath" or "run cygpath" or something. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton -- 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: cygpath hangs from postinstall scripts when called like $(cygpath -S) but not otherwise
All, I concur - I have a couple of private packages that I build, and then use a local copy of upset to create the setup.ini file. My packages are ** NOT ** XFree86 related, and I have the same type of $(cygpath -S) call in my postinstall scripts. They also freeze up this latest setup.exe, the 2.340.2.5 release of setup.exe everything worked properly. Interesting though, if I run "H:\CygnusSolutions-Cygwin Files\strace.exe" -o "H:\CygnusSolutions-Cygwin Files\strace.setup.txt" "H:\CygnusSolutions-Cygwin Files\setup.exe" from a Windows command short cut, then setup.exe correctly installs cygwin without any freeze ups. Alan -Original Message- From: Harold L Hunt II [mailto:[EMAIL PROTECTED] Sent: October 3, 2003 13:32 To: [EMAIL PROTECTED] Cc: cygx Subject: Re: cygpath hangs from postinstall scripts when called like $(cygpath -S) but not otherwise I should emphasize that the reason this is important is because the XFree86-bin-icons package calls cygpath in this manner and it freezes setup.exe when the postinstall or preremove script gets run. So, there is current breakage with this. It is not a hypothetical situation. Harold Harold L Hunt II wrote: > This looks like a cygpath problem, but it has something to do with the > environment in which cygpath gets run from a postinstall script. > Whomever is interested, please look into it. Whomever is not > interested, please keep your grumpy flames to yourself. > > > To demonstrate this problem, please do the following > > > 1) Save the attached file as /etc/postinstall/cygpath-hangs.sh. > > 2) Run setup.exe, select any mirror. > > 3) Choose 'keep' on the package selection page. Then, select a null > package (e.g. XFree86-base) and choose 'reinstall'. This will cause > postinstall scripts to be run, but it won't change your installed > package or force you to have to download a large package just to get > this behavior. > > 4) setup.exe will run cygpath-hangs.sh and, lo!, it will sit there (i.e. > hang) waiting for cygpath-hangs.sh to return. > > 5) Go look in /var/log/ for the most recent file following the pattern > setup.log.postinstall*. Open it. > > 6) You should see the following in the log file: > > + which which > /usr/bin/which > + cygpath -S > /cygdrive/c/WINDOWS/system32 > ++ which which > + FOO=/usr/bin/which > ++ cygpath -S > > 7) Run /etc/postinstall/cygpath-hangs.sh from a bash shell and observe > that it does not hang. > > > Summary > === > > 1) You can run 'which which' from a postinstall script without saving > its output to a variable. > > 2) You can run 'cygpath -S' (or any other flag combo) from a postinstall > script without saving its output to a variable. > > 3) You can run 'which which' from a postinstall script and save its > output to a variable (e.g. FOO=$(which which)) > > 4) If you run 'cygpath -S' from a postinstall script and save its output > to a variable (e.g. BAR=$(cygpath -S)), then cygpath will fail to return > for eternity. > > 5) cygpath's failure to return causes bash to fail to return, which > causes setup.exe to wait forever for cygpath-hangs.sh to complete. > > > There, I have proven beyond a doubt that this has absolutely nothing to > do with Cygwin/XFree86 :) > > I would appreciate any help in fixing this. > > Thanks in advance, > > Harold > > > > > #!/bin/bash -x > > which which > cygpath -S > > FOO=$(which which) > BAR=$(cygpath -S) -- 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/
FW: XFree86-bin-icons .. believe cygwin xfree86 a "red" herring ... this is I believe a cygwin problem
All, Relates to http://cygwin.com/ml/cygwin/2003-09/msg01821.html These are the cygcheck files gziped and non-full setup files gziped _ Alan Miles ICQ#: 171006836 More ways to contact me: http://wwp.icq.com/171006836 _ cygcheck_results_machine1_works.txt.gz Description: Binary data cygcheck_results_machine2_doesnt_work.txt.gz Description: Binary data setup_machine1_works.log.gz Description: Binary data setup_machine2_doesnt_work.log.gz Description: Binary data -- 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/
FW: XFree86-bin-icons .. believe cygwin xfree86 a "red" herring ... this is I believe a cygwin problem
All, This is attempt 4 - I cannot seem to get the attachment there, since I get: Hi. This is the qmail-send program at sources.redhat.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. <[EMAIL PROTECTED]>: ezmlm-reject: fatal: Sorry, I don't accept messages larger than 10 bytes (#5.2.3) <[EMAIL PROTECTED]>: ezmlm-reject: fatal: Sorry, I don't accept messages larger than 5 bytes (#5.2.3) --- Enclosed are the original headers of the message. and according to my emailer the attachment is 777kB. I did try and send the cygcheck etc. -Original Message- From: Alan Miles [mailto:[EMAIL PROTECTED] Sent: September 29, 2003 23:34 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: FW: XFree86-bin-icons .. believe cygwin xfree86 a "red" herring ... this is I believe a cygwin problem All, This is attempt 3 ... the previous attempts failed because the emailer said the messages, with the uncompressed log files was too big, and thus would send them. I have tarred and compressed them into the logs.tgz file - manifest: logs/ logs/cygcheck_results_machine1_works.txt logs/cygcheck_results_machine2_doesnt_work.txt logs/setup_machine1_works.log logs/setup_machine1_works.log.full logs/setup_machine2_doesnt_work.log logs/setup_machine2_doesnt_work.log.full Alan -Original Message- From: Alan Miles [mailto:[EMAIL PROTECTED] Sent: September 29, 2003 23:11 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: XFree86-bin-icons .. believe cygwin xfree86 a "red" herring ... this is I believe a cygwin problem All, I believe this problem relates to the items listed in http://cygwin.com/ml/cygwin/2003-09/msg01680.html - RE: Install gets to 99% and then stops http://www.cygwin.com/ml/cygwin/2003-09/msg00747.html - Setup 2.358 Hangs During Post-Install Script Additionally I have two separate machines, one fully updated on 26-Sep-2003 (which exhibits the problem) and one updated today that doesn't. Differences: 1/ The 26-Sep-2003 machine uses the ** latest ** setup.exe (files labelled machine2, doesnt_work) 2/ Today's update use the previous older version (file labelled machine1_work) 3/ I built special private install packages for 26-Sep-2003 machine which I have uses successfully for several months which do ** NOT ** involve XFree86 and these packages also exhibit: Something strange is going on here... setup.exe says "Running: No Package /etc/postinstal/". What is up with the "No Package"? My packages deal with my special problem with the password file (published on this list), the jar command, script etc. The setup.log.full contains the /usr/bin/bash -x dump of the /etc/postinstall/ files. 4/ When investigating, the problem in 3, I to found the 'cygpath' problem in ** my ** private packages (which as stated do ** NOT ** involve XFree86) This leads me to believe that there is some kind of interaction between the new setup.exe and cygpath that is causing the problem. I am attaching both sets of setup.log, setup.log.full, and the cygcheck output for both machines. Also I noticed within the file setup_machine2_doesnt_work.log.full: Transcript written on amstex.log. fmtutil: /usr/share/texmf/web2c/lambda.oft installed. fmtutil: /usr/share/texmf/web2c/omega.oft installed. fmtutil: /usr/share/texmf/web2c/amstex.fmt installed. fmtutil: /usr/share/texmf/web2c/latex.fmt installed. fmtutil: /usr/share/texmf/web2c/pdflatex.fmt installed. fmtutil: /usr/share/texmf/web2c/pdftex.fmt installed. fmtutil: /usr/share/texmf/web2c/tex.fmt installed. fmtutil: /usr/share/texmf/web2c/elatex.efmt installed. fmtutil: /usr/share/texmf/web2c/etex.efmt installed. fmtutil: /usr/share/texmf/web2c/pdfelatex.efmt installed. fmtutil: /usr/share/texmf/web2c/pdfetex.efmt installed. fmtutil: /usr/share/texmf/web2c/mpost.mem installed. fmtutil: /usr/share/texmf/web2c/mf.base installed. fmtutil: /usr/share/texmf/web2c/mfw.base installed. install_link failed for /usr/bin/latex. File already exists. Checking for psfonts.map in config.ps... no. Adding ... done 2003/09/27 00:32:49 running: H:\cygwin\bin\sh.exe -c /etc/postinstall/postinstall-lilypond.sh find: paths must precede expression Usage: find [path...] [expression] rm: too few arguments Try `rm --help' for more information. 2003/09/27 00:32:50 running: H:\cygwin\bin\sh.exe -c /etc/postinstall/proftpd.sh 2003/09/27 00:32:50 running: H:\cygwin\bin\sh.exe -c /etc/postinstall/robots.sh 2003/09/27 00:32:51 running: H:\cygwin\bin\sh.exe -c /etc/postinstall/rpm.sh 2003/09/27 00:32:52 running: H:\cygwin\bin\sh.exe -c /etc/postinstall/splint.sh 2003/09/27 00:32:52 running: H:\cygwin\bin\sh.exe -c /etc/postinstall/squid-postinstall.sh will not overwrite existing /etc/squid.conf will not overwrite existing /etc/mime.conf 2003/09/27 00:32:52 running: H:\cygwin\bin\sh.exe -c
RE: Question regarding problem during uninstall using setup.exe
Rob, Sorry it has been a looong week ... with quite a number of looong weeks ahead, and I misinterpreted your response. Anyway, I appreciate your responses. I am going to try a preremove script. I have just checked http://cygwin.com/setup.html to see if there is any online info about how these work, but I couldn't see any. Anyway with the preremove script, I am going to try an unmount first of any specific mounted dir's prior to the removal of the package. I am aware (as I subscribe to cygwin-apps) that there is allot of work being done on setup.exe and cygwin dll (1.5.1) and not being familiar with the program would take allot of work to get up to speed. However, I would be more than willing to share my results of the preremove script, if the unmounting works. Alan -Original Message- From: Robert Collins [mailto:[EMAIL PROTECTED] Sent: August 1, 2003 17:00 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: Question regarding problem during uninstall using setup.exe On Fri, 2003-08-01 at 21:45, Alan Miles wrote: > Rob, > > Thanks for the message. > > However, my "packages" did NOT create these directories - I just wish to > mount them, therefore setup should not be deleting them. For example, I understand that. Which part of my email suggested I did not understand the problem? It's known. The cause it predictable. We could do better - hey, you're welcome to join in the development and help improve this area! Cheers, Rob -- GPG key available at: http://members.aardvark.net.au/lifeless/keys.txt. --- -- 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: Question regarding problem during uninstall using setup.exe
Rob, Thanks for the message. However, my "packages" did NOT create these directories - I just wish to mount them, therefore setup should not be deleting them. For example, I mount C:\Documents and Settings\Alan Miles as /mnt/User. Setup should not (and does not) delete the files in this sub-directory. I noticed Christopher Faylor has replied as well, but I haven't had a chance to review his message. I will do that later, when I have more time. Thanks, Alan -Original Message- From: Robert Collins [mailto:[EMAIL PROTECTED] Sent: August 1, 2003 04:44 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Question regarding problem during uninstall using setup.exe On Fri, 2003-08-01 at 10:21, Alan Miles wrote: > > I don't believe it should be doing the > > rmdir H:\CygnusSolutions-Cygwin Files\CygwinMachine_Package_Dirs\dest > rmdir H:\CygnusSolutions-Cygwin Files\CygwinMachine_Package_Dirs\build > > commands, and I am not sure if this is a setup.exe issue, hence the reason I > am sending this to this mailing list. Setup tries to remove any directories created by packages it installs - which includes /. Improvements could be made in this area, yes. Cheers, Rob -- GPG key available at: http://members.aardvark.net.au/lifeless/keys.txt. --- -- 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/
Question regarding problem during uninstall using setup.exe
All, I tried to send this message to [EMAIL PROTECTED], since as I understand from the web-site setup.exe issues go there, but my message got bounced. Hence I am sending it here. Keep up the excellent work on cygwin. Can't wait for 1.5.* to come out. Using the latest setup and installation of cygwin I have a problem when I use setup.exe to un-install cygwin, so I can get a ** completely ** fresh install. I periodically like to uninstall cygwin and re-install to remove any cruft etc. Also this helps with maintenance of my computer, as I can always re-install later. That way I don't have to use so many backup CD's. To get around my ** own ** customizations, I have built my own install packages that integrate into the setup.exe. To do this integration, I use the "generic" build script template, setup.hints + upset to construct my setup.ini. This works great. However, when I de-install setup.exe seems to remove several directories that are ** NOT ** in the cygwin directory structure but are elsewhere, and I mount them under cygwin. Output of my mount: H:\CygnusSolutions-Cygwin Files\CygwinMachine_Package_Dirs\build on /CygwinMachine_Package_Files/Build type system (binmode) H:\CygnusSolutions-Cygwin Files\CygwinMachine_Package_Dirs\dest on /CygwinMachine_Package_Files/Release type system (binmode) H:\CygnusSolutions-Cygwin Files\CygwinMachine_Package_Dirs\src on /CygwinMachine_Package_Files/src type system (binmode) C:\Documents and Settings\Alan Miles on /mnt/User type user (binmode) H:\cygwin\usr\X11R6\lib\X11\fonts on /usr/X11R6/lib/X11/fonts type system (binmode) H:\cygwin\bin on /usr/bin type system (binmode) H:\cygwin\lib on /usr/lib type system (binmode) H:\cygwin on / type system (binmode) c: on /mnt/Drives/c type system (binmode,noumount) d: on /mnt/Drives/d type system (binmode,noumount) e: on /mnt/Drives/e type system (binmode,noumount) h: on /mnt/Drives/h type system (binmode,noumount) i: on /mnt/Drives/i type system (binmode,noumount) j: on /mnt/Drives/j type system (binmode,noumount) k: on /mnt/Drives/k type system (binmode,noumount) l: on /mnt/Drives/l type system (binmode,noumount) Setup.exe seems to remove H:\CygnusSolutions-Cygwin Files\CygwinMachine_Package_Dirs\build and H:\CygnusSolutions-Cygwin Files\CygwinMachine_Package_Dirs\dest (which I use but were empty at the time). Interestingly, it does ** NOT ** remove H:\CygnusSolutions-Cygwin Files\CygwinMachine_Package_Dirs\src which is NOT empty. Subsequent re-installation causes problems with the mount command, until I unmount, manually re-create these directories, and remount. For example, a fragment of info from my setup.log.full file (related to the installation): ... rmdir H:\cygwin/usr/doc/_CygwinMachine_Base-1.0/Setup-Help rmdir H:\cygwin/usr/doc/_CygwinMachine_Base-1.0/PackageBuilder/infra/bin/cygwin/Cy gwin/Setup/CVS rmdir H:\cygwin/usr/doc/_CygwinMachine_Base-1.0/PackageBuilder/infra/bin/cygwin/Cy gwin/Setup rmdir H:\cygwin/usr/doc/_CygwinMachine_Base-1.0/PackageBuilder/infra/bin/cygwin/Cy gwin/CVS rmdir H:\cygwin/usr/doc/_CygwinMachine_Base-1.0/PackageBuilder/infra/bin/cygwin/Cy gwin rmdir H:\cygwin/usr/doc/_CygwinMachine_Base-1.0/PackageBuilder/infra/bin/cygwin/CV S rmdir H:\cygwin/usr/doc/_CygwinMachine_Base-1.0/PackageBuilder/infra/bin/cygwin rmdir H:\cygwin/usr/doc/_CygwinMachine_Base-1.0/PackageBuilder/infra/bin/CVS rmdir H:\cygwin/usr/doc/_CygwinMachine_Base-1.0/PackageBuilder/infra/bin rmdir H:\cygwin/usr/doc/_CygwinMachine_Base-1.0/PackageBuilder/infra/CVS rmdir H:\cygwin/usr/doc/_CygwinMachine_Base-1.0/PackageBuilder/infra rmdir H:\cygwin/usr/doc/_CygwinMachine_Base-1.0/PackageBuilder rmdir H:\cygwin/usr/doc/_CygwinMachine_Base-1.0/CygwinMachine-Help rmdir H:\cygwin/usr/doc/_CygwinMachine_Base-1.0/Auxillary_Scripts rmdir H:\cygwin/usr/doc/_CygwinMachine_Base-1.0 rmdir H:\cygwin/mnt/User rmdir H:\cygwin/mnt/Drives/Z rmdir H:\cygwin/mnt/Drives/Y rmdir H:\cygwin/mnt/Drives/X rmdir H:\cygwin/mnt/Drives/W rmdir H:\cygwin/mnt/Drives/V rmdir H:\cygwin/mnt/Drives/U rmdir H:\cygwin/mnt/Drives/T rmdir H:\cygwin/mnt/Drives/S rmdir H:\cygwin/mnt/Drives/R rmdir H:\cygwin/mnt/Drives/Q rmdir H:\cygwin/mnt/Drives/P rmdir H:\cygwin/mnt/Drives/O rmdir H:\cygwin/mnt/Drives/N rmdir H:\cygwin/mnt/Drives/M rmdir H:\cygwin/mnt/Drives/L rmdir H:\cygwin/mnt/Drives/K rmdir H:\cygwin/mnt/Drives/J rmdir H:\cygwin/mnt/Drives/I rmdir H:\cygwin/mnt/Drives/H rmdir H:\cygwin/mnt/Drives/G rmdir H:\cygwin/mnt/Drives/F rmdir H:\cygwin/mnt/Drives/E rmdir H:\cygwin/mnt/Drives/D rmdir H:\cygwin/mnt/Drives/C rmdir H:\cygwin/mnt/Drives/B rmdir H:\cygwin/mnt/Drives/A rmdir H:\cygwin/mnt/Drives rmdir H:\cygwin/etc/skel/.ncftp rmdir H:\cygwin/etc/CygwinMachines.Diffs rmdir H:\CygnusSolutions-Cygwin Files\CygwinMachine_Package_Dirs\dest rmdir H:\CygnusSolutions-Cygwin Files\CygwinMachine_Package_Dirs\build 2003/07/31 11:24:35 Uninstalling _CygwinMachine_Custom_Utilities unlink H:\cygwin/bin//FieldCounter.exe unlink H:\cygwin/b
Patch for Bug in /etc/profile script ....
All,
I have a file called /etc/skel/a/b/c/d.txt, /etc/skel/e/f.txt
Under Linux (and I certainly believe the same is true for UNIX), anything,
directory(s), file(s) etc put in /etc/skel
gets put into the user's home directory when the sys admin creates the
account and its home directory.
However, that is not happening here.
What is happening here in these two examples is that it is trying to copy
the file:
cp /etc/skel/a/b/c/d.txt /home/user1/a/b/c/d.txt
cp /etc/skel/e/f.txt /home/user1/e/f.txt
Now this ** would ** work if the directories /home/user1/a/b/c/, and
/home/user1/e had already existed. However, they don't since the system
is creating the home directory. Hence the copy fails.
I am submitting this patch which corrects the problem. the key is the -D
flag on the install command - it causes the system to create any missing
leading directories, as well as doing the install.
$ diff -u /etc/profile.old profile
--- /etc/profile.old2003-06-14 10:03:21.0 -0500
+++ profile 2003-06-23 04:01:00.0 -0500
@@ -32,7 +32,7 @@
for f in `/bin/find . -type f`; do
fDest=`echo $f | sed -e 's/^\.//g'`
if [ ! -e "$HOME$fDest" -a ! -L "$HOME$fDest" ]; then
- cp "$f" "$HOME/$fDest"
+ /usr/bin/install -D -p -v "${f}" "${HOME}/${fDest}"
fi
done
fi
_
Alan Miles
ICQ#: 171006836
More ways to contact me: http://wwp.icq.com/171006836
_
--
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/
Question regarding setup, upset and post install scripts
All, I am running cygwin at work and at home. As I need to "customize" cygwin for each environment (i.e., one for work, one for home) I found a way to build "custom" packages, that I would like to integrate into my setup. Such customizations include: - For ** my ** environments - remove the space in the "passwd" files for a user name (I have posted messages on this list in the past regarding a more primitive version) - Adding Win32 CPAN support to perl (I have posted messages on this list in the past regarding patches) - I ** NEEDED ** a "-u" flag to jar (the cygwin versions says it is unsupported), so build a "wrapper" script to a "Windows" version (uses cygpath to do cygwin/Windows file name conversions) etc. To integrate these into my setup, I found information on this list regarding "upset", setup.hints etc. I have somewhat successfully got the setup.ini file working. However, my postinstall script is malfunctioning and I am trying to figure out how to debug it. When I run it ** AFTER ** cygwin has installed (not using my integration) the script works fine. How can I capture the output to a log file (via the setup) mechanism? I found these messages, but they haven't helped me too much. Any ideas? http://sources.redhat.com/ml/cygwin/2002-10/msg00955.html http://sources.redhat.com/ml/cygwin/2003-04/msg00379.html _ Alan Miles ICQ#: 171006836 More ways to contact me: http://wwp.icq.com/171006836 _ -- 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: WinXP username with spaces --> wmaker ko
Igor, Will do. Thanks for your input. Alan -Original Message- From: Igor Pechtchanski [mailto:[EMAIL PROTECTED] Sent: April 5, 2003 14:03 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: WinXP username with spaces --> wmaker ko On Sat, 5 Apr 2003, Alan Miles wrote: > Igor, > > I appreciate your input - > > >> you can actually *have* two users, e.g., "Alan Miles" and > >> "Alan_Miles", > > That possibility had not occurred to me - thanks for pointing that flaw out. > > Since, this for me, is a problem at home, and not at work -I would have to > investigate this in my own time. The perl items > I need for both home and work, so I can investigate that item there. > > I could (when I have some time) look at determining what scripts need > fixing - once such "broken" script would be /etc/profile: > > > cp -a /etc/skel/. $HOME > > should probably read: > > > cp -a /etc/skel/. "$HOME" > > Igor, if I could get a list of such patches together, could you provide me > with a "sanity" check (like you already have done). That way > any flawed reasoning can be dealt with. > [snip] > Cheers, > Alan Alan, I'm sure if you post the patches (or a link to a website containing them) to this list, you'll get plenty of feedback. I'll certainly take a look at them, although someone may beat me to it. FYI, it's best if the patches are in unidiff (diff -up) format, as per <http://cygwin.com/contrib.html> (even though your patches won't be to the Cygwin source tree). That way they are easier to review. Igor P.S. If you provide a patch, make sure to specify exactly which package and which version the patch is for... -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Knowledge is an unending adventure at the edge of uncertainty. -- Leto II -- 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: WinXP username with spaces --> wmaker ko
Igor, I appreciate your input - >> you can actually *have* two users, e.g., "Alan Miles" and >> "Alan_Miles", That possibility had not occurred to me - thanks for pointing that flaw out. Since, this for me, is a problem at home, and not at work -I would have to investigate this in my own time. The perl items I need for both home and work, so I can investigate that item there. I could (when I have some time) look at determining what scripts need fixing - once such "broken" script would be /etc/profile: > cp -a /etc/skel/. $HOME should probably read: > cp -a /etc/skel/. "$HOME" Igor, if I could get a list of such patches together, could you provide me with a "sanity" check (like you already have done). That way any flawed reasoning can be dealt with. Meanwhile, Kaio, if you don't have two users, maybe (at least for the moment), my manual solution would fix your problem. Cheers, Alan -- 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: WinXP username with spaces --> wmaker ko
Igor,
Granted - There are "issues" with the solution - that is why I said
"partial" solution ( I need to resolve ALL issues)
The challenge really has to do with /usr/bin/mkpasswd (which gets called by
/etc/postinstall/passwd-grp.sh during the install process)
>From what I can tell, it is the item that generates the password file, which
affects HOME and the home directory setup.
Often, users don't have access to change their id's, so there Windows logon
name may have spaces in them. We cannot chnage that.
Maybe I wasn't too clear in my thoughts - until I have a scripted solution
(the code fragment I presented), I manually "fix" the problem by:
1/ Install CYGWIN (say to c:\cygwin) - I install the icon to my desktop and
start menu
2/ Using Windows Wordpad, open the /etc/passwd file (e.g.,
c:\cygwin\etc\passwd)
3/ Change field 1 (the user name) - change any spaces to _ characters (i.e.,
change "Alan Miles" to "Alan_Miles")
4/ Change field 6 (the home directory setting) - change any spaces to _
characters (i.e., change "/home/Alan Miles" to "/home/Alan_Miles")
5/ Save /etc/passwd file (e.g., c:\cygwin\etc\passwd)
6/ Click on the cygwin desktop icon to "logon" to cygwin for the first time.
/etc/profile creates the home directory the first time:
(fragment from /etc/profile:
# If the home directory doesn't exist, create it.
if [ ! -d "$HOME" ]; then
mkdir -p "$HOME"
# copy skeleton files
cp -a /etc/skel/. $HOME
fi
)
Now the cygwin creates the home directory properly (i.e.,
"/home/Alan_Miles"), HOME is set to "/home/Alan_Miles", and USER is set to
"Alan_Miles"
I have not had any trouble with this "manual" setup.
This is the item I would like to either fix by scripting, e.g., the partial
code fragment already presented, or better still patch /usr/bin/mkpasswd to
convert any names it sees with spaces in them to _ characters. Then problem
"completely" solved.
I appreciate your input.
BTW, Igor got your other message regarding Perl - you said:
>> This wasn't meant to chide you;
You weren't chiding me - my first message I thought went to Gerrit only and
should have gone to the list (which is why I then resent it). All you did
was point out that I inadvertently duplicated messages - no problem.
Alan
-Original Message-
From: Igor Pechtchanski [mailto:[EMAIL PROTECTED]
Sent: April 5, 2003 10:53
To: [EMAIL PROTECTED]
Cc: kaio; [EMAIL PROTECTED]
Subject: RE: WinXP username with spaces --> wmaker ko
Alan,
The "fix" below has a few problems (one of which is unconditionally
removing /etc/passwd). IMO, it's better to fix the scripts that have
improper quoting, or, barring that, unset HOME in your Windows environment
(or modify /etc/profile) and make sure your username doesn't contain a
space. Going out of your way to accomodate scripts without proper quoting
will only lead to the proliferation of such scripts.
Igor
On Sat, 5 Apr 2003, Alan Miles wrote:
> All,
>
> I have the same problem (on my machine at home) - However I do have a
> (partial) solution (I am still working on the final solution):
>
> This has to be done after CYGWIN installation, but BEFORE and user logon.
> Edit the /etc/passwd file and replace the space in the first field, and
edit
> the field /home/ to /home/
> and save.
>
> I am working on a scripting solution to install as part of my
installation -
> maybe this could be incorporated as part of the "main" CYGWIN release.
>
> Below is a script fragment on how I am proposing to "automate" this fix.
>
> ThePasswordFile="/etc/passwd"
> ModUserName="$(/usr/bin/echo "${USER}" | /usr/bin/sed -e 's/ /_/g')"
>
> ...
>
> ModHomeUserName="$(/usr/bin/basename "${HOME}" | /usr/bin/sed -e 's/
/_/g')"
> ModHomeUserDirName="$(/usr/bin/dirname "${HOME}")/"
> ModHome="${ModHomeUserDirName}${ModHomeUserName}"
>
> /usr/bin/rm -f "${ThePasswordFile}"
>
> if [ ! -e "${ThePasswordFile}" -a ! -L "${ThePasswordFile}" ]
> then
>/usr/bin/mkpasswd -l -c | /usr/bin/gawk -F':' -v oldUser="${USER}" -v
newUser="${ModUserName}" -v newUserHomeDir="${ModHome}" ' BEGIN {OFS=":" ; }
$1 ~ oldUser {$1=newUser ; $6=newUserHomeDir; } {print $0 ; } ' >
"${ThePasswordFile}"
> fi
>
> Hope this helps.
>
> Alan
> -Original Message-
> From: kaio [mailto:[EMAIL PROTECTED]
> Sent: April 4, 2003 10:48
> To: [EMAIL PROTECTED]
> Subject: WinXP username with spaces --> wmaker ko
>
>
> i have my administrator user named with a space on WInXP.
> cy
RE: PERL 5.8.0-2 and Haase_Gerrit/1.3/perl/Tk800.023-1.patch - taking this to Tk800.024
Igor, I am using MS Outlook 2000 - Gerrit's email was: [EMAIL PROTECTED] when I checked the "properties" of this email I got: [EMAIL PROTECTED] Thus I am guessing I inadvertently sent "duplicate" messages to the group - my apologies for that. Alan -Original Message- From: Igor Pechtchanski [mailto:[EMAIL PROTECTED] Sent: April 5, 2003 10:41 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: PERL 5.8.0-2 and Haase_Gerrit/1.3/perl/Tk800.023-1.patch - taking this to Tk800.024 On Sat, 5 Apr 2003, Alan Miles wrote: > Sorry - my original reply went to Gerrit only - having read on the list that > it should be going to the group, I am sending this to the group ... > [snip] Alan, Did you by any chance notice which return address Gerrit used? ;-) FYI, your original reply is here: <http://cygwin.com/ml/cygwin/2003-04/msg00502.html> 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! Knowledge is an unending adventure at the edge of uncertainty. -- Leto II -- 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: WinXP username with spaces --> wmaker ko
All,
I have the same problem (on my machine at home) - However I do have a
(partial) solution (I am still working on the final solution):
This has to be done after CYGWIN installation, but BEFORE and user logon.
Edit the /etc/passwd file and replace the space in the first field, and edit
the field /home/ to /home/
and save.
I am working on a scripting solution to install as part of my installation -
maybe this could be incorporated as part of the "main" CYGWIN release.
Below is a script fragment on how I am proposing to "automate" this fix.
ThePasswordFile="/etc/passwd"
ModUserName="$(/usr/bin/echo "${USER}" | /usr/bin/sed -e 's/ /_/g')"
...
ModHomeUserName="$(/usr/bin/basename "${HOME}" | /usr/bin/sed -e 's/ /_/g')"
ModHomeUserDirName="$(/usr/bin/dirname "${HOME}")/"
ModHome="${ModHomeUserDirName}${ModHomeUserName}"
/usr/bin/rm -f "${ThePasswordFile}"
if [ ! -e "${ThePasswordFile}" -a ! -L "${ThePasswordFile}" ]
then
/usr/bin/mkpasswd -l -c | /usr/bin/gawk -F':' -v oldUser="${USER}" -v
newUser="${ModUserName}" -v newUserHomeDir="${ModHome}" ' BEGIN {OFS=":" ; }
$1 ~ oldUser {$1=newUser ; $6=newUserHomeDir; } {print $0 ; } ' >
"${ThePasswordFile}"
fi
Hope this helps.
Alan
-Original Message-
From: kaio [mailto:[EMAIL PROTECTED]
Sent: April 4, 2003 10:48
To: [EMAIL PROTECTED]
Subject: WinXP username with spaces --> wmaker ko
i have my administrator user named with a space on WInXP.
cygwin installation is ok, but windowmaker don't install: seems that the
space generates a new parameter in installation commands!
in fact, wmaker installation creates a new dir in /home/ with the first half
of username!
--
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: PERL 5.8.0-2 and Haase_Gerrit/1.3/perl/Tk800.023-1.patch - taking this to Tk800.024
Sorry - my original reply went to Gerrit only - having read on the list that
it should be going to the group, I am sending this to the group ...
Gerrit,
Thanks for the email.
I have been using CYGWIN for about 3/4 years now, both at home and at work,
and I needed to get this item to work using cygwin perl. Now it does.
>> It was reported that Tk800.024 builds without patching it or with
>> minimal tweaks like the one you need to apply to get it compiled
>> after updating 023 w/ patch to 024.
The libraries compile (except for the warning below), but one of the test
programs failed to link due to the undefined reference to
`_win32_get_osfhandle' issue in Tk800.024-1/Event/Event.xs. I found the
answer on how to fix that in
http://sources.redhat.com/ml/cygwin/2002-09/msg00752.html.
To build I execute the command "perl Makefile.PL && make && make test &&
make install". Hence my reason for "patching" the source.
My purpose in sending the email was to ensure that nobody else had to
"re-invent the wheel". Maybe you could try this patch out, and then release
it for the cygwin community.
Since emailing the group, I have fixed the below problem:
/usr/include/limits.h:143:1: warning: this is the location of the previous
definition
gcc -c -I.. -I../pTk/mTk/xlib -I. -Ibitmaps -I../pTk/mTk/xlib -DPERL_USE_SA
FE_PUTENV -fno-strict-aliasing -DUSEIMPORTLIB -O2 -DVERSION=\"800.024\" -D
XS_VERSION=\"800.024\"
"-I/usr/lib/perl5/5.8.0/cygwin-multi-64int/CORE" -D__WIN32__ -D_WIN32 -DWIN
32 -Wall -Wno-implicit-int -Wno-comment -Wno-unused -D__USE_FIXED_PROTOTYPES
__ imgGIF.c
In file included from tkPort.h:28,
from tk.h:71,
from imgGIF.c:35:
tkWinPort.h:54:1: warning: "OPEN_MAX" redefined
In file included from
/usr/lib/gcc-lib/i686-pc-cygwin/3.2/include/limits.h:132,
from
/usr/lib/gcc-lib/i686-pc-cygwin/3.2/include/syslimits.h:7,
from
/usr/lib/gcc-lib/i686-pc-cygwin/3.2/include/limits.h:11,
from tkWinPort.h:31,
from tkPort.h:28,
from tk.h:71,
from imgGIF.c:35:
Hence my current (complete) patch is (which is largely based on your
original patch):
diff -r -u Tk800.024/Event/Event.xs Tk800.024-1/Event/Event.xs
--- Tk800.024/Event/Event.xs2002-01-07 03:35:44.0 -0600
+++ Tk800.024-1/Event/Event.xs 2003-04-04 13:49:42.0 -0600
@@ -4,6 +4,17 @@
modify it under the same terms as Perl itself.
*/
+/*
+ * Fix required to fix: undefined reference to `_win32_get_osfhandle' issue
as directed in:
+ *
+ * http://sources.redhat.com/ml/cygwin/2002-09/msg00752.html
+ *
+ */
+#ifdef __CYGWIN__
+# define win32_get_osfhandle _get_osfhandle
+# define win32_open_osfhandle _open_osfhandle
+#endif
+
#include
#include
#include
diff -r -u Tk800.024/Makefile.PL Tk800.024-1/Makefile.PL
--- Tk800.024/Makefile.PL 2002-03-05 08:00:43.0 -0600
+++ Tk800.024-1/Makefile.PL 2003-04-04 13:49:42.0 -0600
@@ -154,7 +154,7 @@
}
sub MY::postamble {
-'
+ my $str = '
html : subdirs manifypods
@cd pod && $(MAKE) html $(PASTHRU)
@@ -184,6 +184,8 @@
$(MAKE) manifest
';
+ $str =~ s/DEFINE=.*// if($^O eq 'cygwin');
+ $str;
}
diff -r -u Tk800.024/README.cygwin Tk800.024-1/README.cygwin
--- Tk800.024/README.cygwin 2000-09-08 04:27:27.0 -0500
+++ Tk800.024-1/README.cygwin 2003-04-04 13:49:42.0 -0600
@@ -90,7 +90,7 @@
(sometimes $^O eq 'MSWin32' is used instead of $Tk::platform
eq 'MSWin32' assuming they are equivalent and vice versa)
+ #define distinctions
-_WIN32defined by gcc, if X11 need to undef
+_WIN32win_arch MSWin32
__WIN32__ win_arch MSWin32, also defined in pTk/Lang.h
WIN32 from #include
when precedes #include "perl.h" then need
@@ -107,7 +107,7 @@
README.cygwin MANIFEST
* documentation
-Makefile.PL Tk/MMutil.pm pTk/Makefile.PL
+Makefile.PL Tk/MMutil.pm pTk/Makefile.PL myConfig
* make stuff
pTk/mTk/win/tkWinX.c
@@ -149,6 +149,6 @@
+ Fix gcc warnings, mostly in pTk win32 flavor?
+ Test with cygwin-xfree X Server?
-Thu Aug 31 12:54:09 BST 2000
+Sun Jun 10 21:34:30 PST 2001
Eric Fifer
[EMAIL PROTECTED]
[EMAIL PROTECTED]
diff -r -u Tk800.024/Tk/MMutil.pm Tk800.024-1/Tk/MMutil.pm
--- Tk800.024/Tk/MMutil.pm 2002-03-05 08:27:40.0 -0600
+++ Tk800.024-1/Tk/MMutil.pm2003-04-04 13:49:42.0 -0600
@@ -238,13 +238,10 @@
push(@def,qw(-D__CYGWIN__));
if ($win_arch eq 'MSWin32')
{
- push(@def,qw(-D__WIN32__)) unless $self->{'DEFINE'} =~
/-D__WIN32__/;
+ push(@def,qw(-D__WIN32__ -D_WIN32))
+ unless $self->{'DEFINE'} =~ /-D__WIN32__/;
push(@def,qw(-DWIN32)) if $self->{'NAME'} eq 'Tk::pTk';
}
- elsif ($win_arch eq 'x')
- {
- push(@def,qw(-U_WI
RE: PERL 5.8.0-2 and Haase_Gerrit/1.3/perl/Tk800.023-1.patch - taking this to Tk800.024
Gerrit,
Thanks for the email.
I have been using CYGWIN for about 3/4 years now, both at home and at work,
and I needed to get this item to work using cygwin perl. Now it does.
>> It was reported that Tk800.024 builds without patching it or with
>> minimal tweaks like the one you need to apply to get it compiled
>> after updating 023 w/ patch to 024.
The libraries compile (except for the warning below), but one of the test
programs failed to link due to the undefined reference to
`_win32_get_osfhandle' issue in Tk800.024-1/Event/Event.xs. I found the
answer on how to fix that in
http://sources.redhat.com/ml/cygwin/2002-09/msg00752.html.
To build I execute the command "perl Makefile.PL && make && make test &&
make install". Hence my reason for "patching" the source.
My purpose in sending the email was to ensure that nobody else had to
"re-invent the wheel". Maybe you could try this patch out, and then release
it for the cygwin community.
Since emailing the group, I have fixed the below problem:
/usr/include/limits.h:143:1: warning: this is the location of the previous
definition
gcc -c -I.. -I../pTk/mTk/xlib -I. -Ibitmaps -I../pTk/mTk/xlib -DPERL_USE_SA
FE_PUTENV -fno-strict-aliasing -DUSEIMPORTLIB -O2 -DVERSION=\"800.024\" -D
XS_VERSION=\"800.024\"
"-I/usr/lib/perl5/5.8.0/cygwin-multi-64int/CORE" -D__WIN32__ -D_WIN32 -DWIN
32 -Wall -Wno-implicit-int -Wno-comment -Wno-unused -D__USE_FIXED_PROTOTYPES
__ imgGIF.c
In file included from tkPort.h:28,
from tk.h:71,
from imgGIF.c:35:
tkWinPort.h:54:1: warning: "OPEN_MAX" redefined
In file included from
/usr/lib/gcc-lib/i686-pc-cygwin/3.2/include/limits.h:132,
from
/usr/lib/gcc-lib/i686-pc-cygwin/3.2/include/syslimits.h:7,
from
/usr/lib/gcc-lib/i686-pc-cygwin/3.2/include/limits.h:11,
from tkWinPort.h:31,
from tkPort.h:28,
from tk.h:71,
from imgGIF.c:35:
Hence my current (complete) patch is (which is largely based on your
original patch):
diff -r -u Tk800.024/Event/Event.xs Tk800.024-1/Event/Event.xs
--- Tk800.024/Event/Event.xs2002-01-07 03:35:44.0 -0600
+++ Tk800.024-1/Event/Event.xs 2003-04-04 13:49:42.0 -0600
@@ -4,6 +4,17 @@
modify it under the same terms as Perl itself.
*/
+/*
+ * Fix required to fix: undefined reference to `_win32_get_osfhandle' issue
as directed in:
+ *
+ * http://sources.redhat.com/ml/cygwin/2002-09/msg00752.html
+ *
+ */
+#ifdef __CYGWIN__
+# define win32_get_osfhandle _get_osfhandle
+# define win32_open_osfhandle _open_osfhandle
+#endif
+
#include
#include
#include
diff -r -u Tk800.024/Makefile.PL Tk800.024-1/Makefile.PL
--- Tk800.024/Makefile.PL 2002-03-05 08:00:43.0 -0600
+++ Tk800.024-1/Makefile.PL 2003-04-04 13:49:42.0 -0600
@@ -154,7 +154,7 @@
}
sub MY::postamble {
-'
+ my $str = '
html : subdirs manifypods
@cd pod && $(MAKE) html $(PASTHRU)
@@ -184,6 +184,8 @@
$(MAKE) manifest
';
+ $str =~ s/DEFINE=.*// if($^O eq 'cygwin');
+ $str;
}
diff -r -u Tk800.024/README.cygwin Tk800.024-1/README.cygwin
--- Tk800.024/README.cygwin 2000-09-08 04:27:27.0 -0500
+++ Tk800.024-1/README.cygwin 2003-04-04 13:49:42.0 -0600
@@ -90,7 +90,7 @@
(sometimes $^O eq 'MSWin32' is used instead of $Tk::platform
eq 'MSWin32' assuming they are equivalent and vice versa)
+ #define distinctions
-_WIN32defined by gcc, if X11 need to undef
+_WIN32win_arch MSWin32
__WIN32__ win_arch MSWin32, also defined in pTk/Lang.h
WIN32 from #include
when precedes #include "perl.h" then need
@@ -107,7 +107,7 @@
README.cygwin MANIFEST
* documentation
-Makefile.PL Tk/MMutil.pm pTk/Makefile.PL
+Makefile.PL Tk/MMutil.pm pTk/Makefile.PL myConfig
* make stuff
pTk/mTk/win/tkWinX.c
@@ -149,6 +149,6 @@
+ Fix gcc warnings, mostly in pTk win32 flavor?
+ Test with cygwin-xfree X Server?
-Thu Aug 31 12:54:09 BST 2000
+Sun Jun 10 21:34:30 PST 2001
Eric Fifer
[EMAIL PROTECTED]
[EMAIL PROTECTED]
diff -r -u Tk800.024/Tk/MMutil.pm Tk800.024-1/Tk/MMutil.pm
--- Tk800.024/Tk/MMutil.pm 2002-03-05 08:27:40.0 -0600
+++ Tk800.024-1/Tk/MMutil.pm2003-04-04 13:49:42.0 -0600
@@ -238,13 +238,10 @@
push(@def,qw(-D__CYGWIN__));
if ($win_arch eq 'MSWin32')
{
- push(@def,qw(-D__WIN32__)) unless $self->{'DEFINE'} =~
/-D__WIN32__/;
+ push(@def,qw(-D__WIN32__ -D_WIN32))
+ unless $self->{'DEFINE'} =~ /-D__WIN32__/;
push(@def,qw(-DWIN32)) if $self->{'NAME'} eq 'Tk::pTk';
}
- elsif ($win_arch eq 'x')
- {
- push(@def,qw(-U_WIN32));
- }
}
foreach (@inc)
{
@@ -519,16 +516,12 @@
push(@opt,'LD' => 'gcc -shared');
if ($win_arch eq 'MSWin32')
PERL 5.8.0-2 and Haase_Gerrit/1.3/perl/Tk800.023-1.patch - taking this to Tk800.024
All, I am running the latest cygwin dll, setup etc, with Perl 5.8.0-2 (the latest). BTW, I am running cygwin on a Windows 2000 Professional SP2 machine. The PERL package Tk800.023 is now Tk800.024 but Haase Gerrit's patch to get this package to work under Cygwin only works to Tk800.023. Since I wanted to use Tk800.024, I had to figure out how to do this. ftp://ftp.uni-erlangen.de/pub/pc/gnuwin32/cygwin/porters/Haase_Gerrit/1.3/pe rl/Tk800.023-1.patch http://www.cpan.org/authors/id/NI-S/Tk800.023.tar.gz http://www.cpan.org/authors/id/NI-S/Tk800.patch.023.024.gz To recreate for Tk800.024 I did the following: 1/ Got the above files 2/ Un-tarred the Tk800.023.tar.gz 3/ Applied Haase Gerrit's patch 4/ Applied Tk800.patch.023.024.gz 5/ Renamed the Tk800.023 "root" directory to: Tk800.024 During the make test I got: D_RUN_PATH="/lib/w32api:/usr/lib" gcc -shared -s -L/usr/local/lib Event.o pTkCallback.o tclEvent.o tclNotify.o tclPlatEvent.o tclPlatNotfy.o tclPlat Time.o tclTimer.o tkWin32Dll.o -o ../blib/arch/auto/Tk/Event/Event.dll ../pTk/libpTk.a /usr/lib/perl5/5.8.0/cygwin-multi-64int/CORE/libperl.dll.a -L/ lib/w32api -lcomdlg32 -lgdi32 -lm Event.o(.text+0x245):Event.c: undefined reference to `_win32_get_osfhandle' collect2: ld returned 1 exit status make[1]: *** [../blib/arch/auto/Tk/Event/Event.dll] Error 1 make[1]: Leaving directory `/home/ammiles/Shared_Binaries/Source/Cygwin_Perl_Modules/TK/tmp/Tk800.024/E vent' make: *** [subdirs] Error 2 6/ To fix this: (a) I had to chmod a+w Event/Event.xs (couldn't edit the file) (b) Add the following in: /* * Fix required to fix: undefined reference to `_win32_get_osfhandle' issue as directed in: * * http://sources.redhat.com/ml/cygwin/2002-09/msg00752.html * */ #ifdef __CYGWIN__ # define win32_get_osfhandle _get_osfhandle # define win32_open_osfhandle _open_osfhandle #endif 6/ Re-ran make test. It compiles, however t/fileevent seems to be "stuck", i.e., it is blocked - that is I think the pipe read is waiting for pipe write and visa-versa. I go to the window this creates and select "quit" and all other tests seem to work fine. I am attaching my complete perl Makefile.PL, make, make test logs. Any ideas? Alan Miles some output from my log file: In file included from tkPort.h:28, from Xlib_f.c:1: tkWinPort.h:54:1: warning: "OPEN_MAX" redefined In file included from /usr/lib/gcc-lib/i686-pc-cygwin/3.2/include/limits.h:132, from /usr/lib/gcc-lib/i686-pc-cygwin/3.2/include/syslimits.h:7, from /usr/lib/gcc-lib/i686-pc-cygwin/3.2/include/limits.h:11, from tkWinPort.h:31, from tkPort.h:28, from Xlib_f.c:1: /usr/include/limits.h:143:1: warning: this is the location of the previous definition In file included from Xlib_f.c:10: Xlib.t:28: warning: initialization from incompatible pointer type Xlib.t:32: warning: initialization from incompatible pointer type Xlib.t:36: warning: initialization from incompatible pointer type Xlib.t:40: warning: initialization from incompatible pointer type Xlib.t:56: warning: initialization from incompatible pointer type Xlib.t:66: warning: initialization from incompatible pointer type Xlib.t:76: warning: initialization from incompatible pointer type Xlib.t:80: warning: initialization from incompatible pointer type Xlib.t:96: warning: initialization from incompatible pointer type Xlib.t:144: warning: initialization from incompatible pointer type Xlib.t:148: warning: initialization from incompatible pointer type Xlib.t:158: warning: initialization from incompatible pointer type Xlib.t:162: warning: initialization from incompatible pointer type Xlib.t:172: warning: initialization from incompatible pointer type Xlib.t:176: warning: initialization from incompatible pointer type Xlib.t:180: warning: initialization from incompatible pointer type Xlib.t:184: warning: initialization from incompatible pointer type Xlib.t:200: warning: initialization from incompatible pointer type Xlib.t:204: warning: initialization from incompatible pointer type Xlib.t:208: warning: initialization from incompatible pointer type Xlib.t:212: warning: initialization from incompatible pointer type Xlib.t:224: warning: initialization from incompatible pointer type Xlib.t:228: warning: initialization from incompatible pointer type Xlib.t:232: warning: initialization from incompatible pointer type Xlib.t:248: warning: initialization from incompatible pointer type Xlib.t:252: warning: initialization from incompatible pointer type Xlib.t:278: warning: initialization from incompatible pointer type Xlib.t:378: warning: initialization from incompatible pointer type Xlib.t:382: warning: initialization from incompatible pointer type Xlib.t:386: warning: initialization from incompatible pointer type Xlib.t:390: warning: initialization from incompatible pointer type Xlib.t
