Re: Cygutils patch: fix cygstart under recent snapshots

[Charles Wilson]

Michael Schaap wrote:

Can you apply the patch and release a new Cygutils version, at your 
convenience?


Done.  I'll announce 1.3.1-1 after the mirrors have had a chance to get 
it. (FYI: your next 'cvs update' you'll need to explicitly get the newly 
added m4/ and build-aux/ subdirectories -- or use 'cvs update -d')


--
Chuck

--
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: print from xfig

[Steven Woody]

On 12/5/06, Andrew Louie <[EMAIL PROTECTED]> wrote:

Steven Woody  gmail.com> writes:

>
> i can run xfig successuflly, but i can not print our network printer.
> it reported:
>
> lpr: printer error: can't open 'd:\printersharename'
>
> what do i do? thank you.
>


Can you normally print with lpr?

did you try: lpr -P//networkshare/printername



i tried:  lpr -P//CNZUHPR01 myfile, but got
lpr: printer error: can't open '' for writing: The printer name is invalid.

i am not pretty sure if the printer name is ok.  i got the name by
right click the network printer icon in the control panel then select
the 'properties'.  i know it's a HP LaserJet-2300DN and accessable to
me via our company's domain.

--
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: find -execdir command executed in wrong directory

[David Rothenberger]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 12/5/2006 8:20 PM, Eric Blake wrote:
> David Rothenberger  acm.org> writes:
> 
>>
>> "find -execdir" seems to be executing the command in the wrong
>> directory. If the file is in /tmp/a/b/c, the command is executed with
>> the current directory /tmp/a/b instead of /tmp/a/b/c. oldfind does the
>> right thing.
> 
> Thanks for the report. I'm forwarding it upstream, and hopefully a patch will 
> be available soon.  The bug only affects the "-execdir {} +" version (you can 
> still use the less efficient "-execdir {} \;").
> 

I've encountered another similar problem. This one seems to be triggered
by a directory that comes after some files in a directory.

% cygcheck -cd findutils
Cygwin Package Information
Package  Version
findutils4.3.2-3

% mkdir -p /tmp/a/b/c
% touch /tmp/a/b/a{1,2}
% find /tmp/a -type f -print -execdir pwd {} +
/tmp/a/b/a1
/tmp/a/b/a2
pwd: ignoring non-option arguments
/tmp/a/b/c

The last output should have been /tmp/a/b, not /tmp/a/b/c.

% oldfind /tmp/a -type f -print -execdir pwd {} +
/tmp/a/b/a1
/tmp/a/b/a2
pwd: ignoring non-option arguments
/tmp/a/b

If /tmp/a/b/c is removed, it works correctly.

% rmdir /tmp/a/b/c
% find /tmp/a -type f -print -execdir pwd {} +
/tmp/a/b/a1
/tmp/a/b/a2
pwd: ignoring non-option arguments
/tmp/a/b

It also works correctly if the files come after the directory.

% mkdir /tmp/a/b/a0
% find /tmp/a -type f -print -execdir pwd {} +
/tmp/a/b/a1
/tmp/a/b/a2
pwd: ignoring non-option arguments
/tmp/a/b


- --
David Rothenbergerspammer? -> [EMAIL PROTECTED]
GPG/PGP: 0x92D68FD8, DB7C 5146 1AB0 483A 9D27 DFBA FBB9 E328 92D6 8FD8

Love cannot be much younger than the lust for murder.
-- Sigmund Freud
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEVAwUBRX9kDr3xOW8bc2dhAQiVtgf/cxP7ntgE3C+/zRARKwRO0kOxyIldRRsr
7/hdyt74yps87+NtTjm3xHAwxf7oWvJyDhJxhxsR6tj57oKYRlLqIwoyNg8PZu5g
TwprPLDIDyd0WTfkHl1r1AJnxVAvQesAOO3JEjcbDLvFDWU1JNYj1SEJw6RI3NCG
UwnD/yCLCP4IRIOT/Ok3ituSygb5JPtoMcvWV4C1WJK6OPYv7gt7etwpBohIH4zm
/w+83kLdWn5n9T+kEYW8dsrN9NH3OblAj2byg9jjuwIJ79SO6f9V3kor8OsU9Le1
LwQsqoLuLcroS/27kgE9hUCa8Q8XdFm5wATIotc6lYurTd0mYG0x5A==
=iyjG
-END PGP SIGNATURE-


--
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: another cygport patch

[Yaakov S (Cygwin Ports)]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Eric Blake wrote:
> Cygport currently makes it impossible to pass arguments to ./configure
> that contain a space.  I need this for building autogen.
> 
> 2006-12-12  Eric Blake  <[EMAIL PROTECTED]>
> 
>   * cygport (cygconf): Preserve shell metacharacters in args.

Thanks.  Checked into CVS.


Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFf2D+piWmPGlmQSMRCAZQAKDunELVdDIskgHzUPi3bWTAUtJqUwCggrxB
zSGy1hxo0pp0ynYDNx8Oos8=
=IvIQ
-END PGP SIGNATURE-

--
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: library paths

[Brian Dessent]

Richard Foulk wrote:

> We use perl a lot and are looking into building a standard routine for
> the beginning of each script that will add to the path where necessary.
> And perhaps even remove from the path if two or more instances of the
> key libraries are found.

I don't understand how this would work at all, assuming you mean using
Cygwin's perl.  If the PATH is not set to include /bin then you won't
even be able to run perl at all, let alone execute anything at the
beginning of the script.  The only way to do this would be if you're
talking about CMD.EXE batch file scripting, or some other non-Cygwin
scripting language like VBscript.

Brian

--
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/

library paths

[Richard Foulk]

Running cygwin on a number of diverse machines, accessability of
cygwin1.dll and others can be a problem.

We use perl a lot and are looking into building a standard routine for
the beginning of each script that will add to the path where necessary.
And perhaps even remove from the path if two or more instances of the
key libraries are found.

Has anyone done something like this?  Any suggestions?


Thanks

Richard


--
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: bash.exe: warning: could not find /tmp, please create!

[Igor Peshansky]

On Tue, 12 Dec 2006, João Gonçalves wrote:

> I am trying to start cygwin and I get this error message.
> I understand, from what I read, that this error is because I am using
> a different user. And that's true, I am using a different user, but I
> also lost the old user, because I installed windows again!
> Is to mount cygwin in my current user withou going to the old one? Or
> do I have to install cygwin again?

Please read and follow

> Problem reports:   http://cygwin.com/problems.html

Without that information, a WAG is that your initial Cygwin install was
for "Just me", and the new user is missing the standard mounts.  You can
either use the "mount" command to set up standard mounts, or just re-run
setup and tell it to install for "All users".  You don't need to reinstall
anything (though the above run of setup will upgrade your installation as
well unless you go into the "Keep" mode).
HTH,
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_Igor Peshansky, Ph.D. (name changed!)
 |,4-  ) )-,_. ,\ (  `'-'   old name: Igor Pechtchanski
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Freedom is just another word for "nothing left to lose"...  -- Janis Joplin
--
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: Postinstall Problem with 01bash.bat

[Igor Peshansky]

On Tue, 12 Dec 2006, Dave Korn wrote:

> On 12 December 2006 03:24, Eric Blake wrote:
>
>   Hey Eric,
>
> > Phooey - now that you have gotten rid of the problem, I can't do any
> > more debugging via your system.  I'm still trying to reproduce the
> > failure, by manually sourcing /etc/profile.d/00bash.sh, but so far it
> > seems I am just catching list users, like you, reporting failure that
> > is solved by a simple cp, but where the postinstall script did not
> > work.
>
>   Next time you roll the package, why not get 00bash.sh to run all the
> "ls -l" and "getfacl" stuff that you've been asking people to do after
> the event and stash the results away in a textfile in /etc/setup
> somewhere for after-the-event perusal when it goes wrong for somebody?

Just print it to stdout -- that way it'll be stored in setup.log.full.
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_Igor Peshansky, Ph.D. (name changed!)
 |,4-  ) )-,_. ,\ (  `'-'   old name: Igor Pechtchanski
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Freedom is just another word for "nothing left to lose"...  -- Janis Joplin

--
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/

MAKE does not recognize symbolic links after applying patch

[Jim Breaux]

Hello,

I am using MAKE 3.80 (for various reasons I cannot upgrade to 3.81 yet).  I
recently encountered the bug described here:
http://www.cygwin.com/ml/cygwin/2004-09/msg01659.html

I applied the recommended patch to the source code and rebuilt MAKE.  It
seems to be working fine EXCEPT that it no longer recognizes symbolic links
(e.g., if I call 'make ' it acts as if the file does
not exist when in fact it does exist).  The unpatched version of MAKE has no
problem recognizing symbolic links.  Has anyone seen this kind of behavior
before?

Thanks,

Jim



--
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: bash.exe: warning: could not find /tmp, please create!

[Larry Hall (Cygwin)]

João Gonçalves wrote:

I am trying to start cygwin and I get this error message.
I understand, from what I read, that this error is because I am using
a different user. And that's true, I am using a different user, but I
also lost the old user, because I installed windows again!
Is to mount cygwin in my current user withou going to the old one? Or
do I have to install cygwin again?



You can mount '/tmp' to anywhere you like.  You don't need to reinstall.

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 893-9889 - FAX
Holliston, MA 01746

--
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: Postinstall Problem with 01bash.bat

[Dave Korn]

On 12 December 2006 03:24, Eric Blake wrote:

  Hey Eric,

> Phooey - now that you have gotten rid of the problem, I can't do any more
> debugging via your system.  I'm still trying to reproduce the failure, by
> manually sourcing /etc/profile.d/00bash.sh, but so far it seems I am just
> catching list users, like you, reporting failure that is solved by a
> simple cp, but where the postinstall script did not work.

  Next time you roll the package, why not get 00bash.sh to run all the "ls -l"
and "getfacl" stuff that you've been asking people to do after the event and
stash the results away in a textfile in /etc/setup somewhere for
after-the-event perusal when it goes wrong for somebody?


cheers,
  DaveK
-- 
Can't think of a witty .sigline today


--
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: cygstart getting The specified file was not found

[ERIC HO]

Thanks to all who helped out on this!

--
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/

Automatic "setup.ini" generation/cleanup?

[cuicui]

Hello,

I'd like to speed up the setup.ini parsing during setup and i'm looking 
for a script to generate or clean a "setup.ini" regarding to a local 
packages directory.


Is there any way simple to achieve that ?

All the best,

Nicolas



--
Ce message a ete verifie par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a ete trouve.


--
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: bash.exe: warning: could not find /tmp, please create!

[João Gonçalves]

I am trying to start cygwin and I get this error message.
I understand, from what I read, that this error is because I am using
a different user. And that's true, I am using a different user, but I
also lost the old user, because I installed windows again!
Is to mount cygwin in my current user withou going to the old one? Or
do I have to install cygwin again?

--
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: cygstart getting The specified file was not found

[Michael Schaap]

Corinna Vinschen wrote:

When using cygwin_internal(CW_SYNC_WINENV), Cygwin doesn't only copy the
environment, it also changes into the actual cwd and keeps Cygwin cwd
and native cwd in sync.  This is also propagated to child processes. 
Naturally, this process and its children are blocking the cwd from now

on, until all these processes exited.
  
Luckily, this won't be an issue for cygstart.  It doesn't hang around, 
but exits as soon as it asked the shell to open a file, URL or program.
(Whatever program the shell starts, might be blocking the cwd, of 
course, but that is no different than when you start the program in any 
other way.)


In any case, with the fixed cygstart,
   $ cygstart .
   $ rmdir $PWD
works fine.  (The Explorer window actually closes itself when you do the 
rmdir.)


- Michael

--
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/

Cygwin developer needs Vista

[Christopher Faylor]

Does anyone have a copy of Windows Vista that they would be willing to
donate for the Cygwin cause?  I'm feeling sort of guilty that Corinna is
stuck with all of the Vista issues but, since I don't have a copy of
Vista to use, I can't really help her.

Both 64 and 32 bit versions would be appreciated.

And, hopefuly it goes without saying that I'm looking for legal copies
which are allowed to be transferred to me.

Feel free to send email to cgf at cgf dot cx if you can help out.

cgf
--
Christopher Faylor  spammer? -> [EMAIL PROTECTED]
Cygwin Co-Project Leader[EMAIL PROTECTED]
Network Appliance, Inc.

--
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: cygstart getting The specified file was not found

[Michael Schaap]

Igor Peshansky wrote:

I just looked at the ChangeLog between those two snapshots.  The following
looks like the culprit change:

2006-11-29  Corinna Vinschen  <(snip)>

* path.cc [snip]
(cwdstuff::init): Initialize cygheap->cwd with current working
directory.  Change to windows_system_directory afterwards.

With that change, any use of non-Cygwin calls, e.g., GetCurrentDirectory,
or ShellExecute (which calls GetCurrentDirectory under the covers, it
seems) will produce the problem you're seeing (Windows system directory as
the current directory).

So it looks like you ought to call cygwin_internal(CW_SYNC_WINENV) after
all, as it syncs more than the environment variables...
  

Indeed, this turns out to be the culprit.

Thanks - also to Corinna - for helping to find this,

- Michael

--
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/

Python crashes with threading and Tkinter

[Dan Lenski]

Hi all,
I've been having a problem with Python under Cygwin.  Basically,
Python crashes if I try to start any threads in a program using the
Tkinter GUI package.

This issue has been encountered before, by Steve Ward in February
2006: http://www.cygwin.com/ml/cygwin/2006-02/msg00700.html

The test program that he posted crashes for me as well, under Cygwin
1.5.22-1.  The same program runs flawlessly under Linux.  The only
workaround I have found is this followup by Jim Brooks:
http://www.cygwin.com/ml/cygwin/2006-02/msg00799.html
He recommended downgrading to Cygwin 1.5.18, as apparently the problem
was introduced by threading changes in Cygwin 1.5.19.

Does anyone know of another way to resolve this problem, so that
Python Tkinter programs can use multithreading?  Thanks!

Dan Lenski

--
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: cygstart getting The specified file was not found

[Michael Schaap]

Hi Eric,

ERIC HO wrote:

The command and out are as follows:
/cygdrive/c/user $cmd /c cd
c:\user
The latest snapshot (2006-12-11) has the same problem.
I went back to 1.5.22-1 release and the problem is fixed.

Not sure which change causes this.
Thanks.
  


The bug was found and fixed, and a new Cygutils version which includes 
this fix will hopefully be released soon.
(If you can't wait, feel free to either build a new version yourself 
with the patch, or download an executable from 
.)


Note that this version will work fine in the latest snapshot 
(2006-12-11), but not in the version you were using when you originally 
reported the problem (2006-11-30), though.


Thanks for reporting this,

- Michael

--
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/

Cygutils patch: fix cygstart under recent snapshots

[Michael Schaap]

Hi Chuck,

Attached is a Cygutils patch that fixes cygstart under recent Cygwin 
snapshots.  (It didn't set the current directory correctly under them.)  
In addition, I've added a --verbose flag, which shows the Win32 
ShellExecute call that is made.


Can you apply the patch and release a new Cygutils version, at your 
convenience?


The appropriate Changelog entries are:
   * src/cygstart/cygstart.c (winstart): use 
cygwin_internal(CW_SYNC_WINENV) instead of own code to sync environment
   * src/cygstart/cygstart.c (main): add --verbose option to show 
actual ShellExecute call made


Thanks in advance,

- Michael
Index: src/cygstart/cygstart.c
===
RCS file: /cvs/cygwin-apps/cygutils/src/cygstart/cygstart.c,v
retrieving revision 1.5
diff -u -r1.5 cygstart.c
--- src/cygstart/cygstart.c 10 Feb 2006 05:50:39 -  1.5
+++ src/cygstart/cygstart.c 12 Dec 2006 16:24:51 -
@@ -25,6 +25,8 @@
 #endif
 #include "common.h"
 
+#include 
+
 /* The official name of this program (e.g., no `g' prefix).  */
 #define PROGRAM_NAME "cygstart"
 #define AUTHORS "Michael Schaap"
@@ -40,7 +42,7 @@
 #define MSDN_URL "http://msdn.microsoft.com/library/en-us/shellcc/platform/"; \
  "Shell/reference/functions/shellexecute.asp"
 
-static const char versionID[] = "1.3";
+static const char versionID[] = "1.4";
 /* for future CVS */
 static const char revID[] =
"$Id: cygstart.c,v 1.5 2006/02/10 05:50:39 cwilson Exp $";
@@ -53,9 +55,9 @@
 static char *program_name;
 
 static int cygStart(const char *aPath, const char *action, const char *args,
-const char *workDir, int show);
+const char *workDir, int show, int verbose);
 static int winStart(const char *aPath, const char *action, const char *args,
-const char *workDir, int show);
+const char *workDir, int show, int verbose);
 static char *startError(int err);
 static const char *getVersion(void);
 static void printTopDescription(FILE *f, char *name);
@@ -64,7 +66,6 @@
 static void help(poptContext optCon, FILE *f, char *name);
 static void version(poptContext optCon, FILE *f, char *name);
 static void license(poptContext optCon, FILE *f, char *name);
-static void setup_win_environ(void);
 
 int main(int argc, const char **argv)
 {
@@ -80,6 +81,7 @@
 char *args = NULL;
 char *workDir = NULL;
 int show = SW_SHOWNORMAL;
+int verbose = 0;
 
 /* Action options */
 struct poptOption actionOptionsTable[] = {
@@ -143,6 +145,13 @@
 { NULL, '\0', 0, NULL, 0, NULL, NULL }
 };
 
+/* Troubleshooting options */
+struct poptOption troubleOptionsTable[] = {
+{ "verbose",  'v',  POPT_ARG_NONE, NULL, 'E', \
+  "Show the actual ShellExecute call made", NULL},
+{ NULL, '\0', 0, NULL, 0, NULL, NULL }
+};
+
 /* Help options */
 struct poptOption helpOptionsTable[] = {
 { "help",  '?',  POPT_ARG_NONE, NULL, '?', \
@@ -165,6 +174,8 @@
   "Directory options", NULL },
 { NULL, '\0', POPT_ARG_INCLUDE_TABLE, showOptionsTable, 0, \
   "Show options", NULL },
+{ NULL, '\0', POPT_ARG_INCLUDE_TABLE, troubleOptionsTable, 0, \
+  "Troubleshooting options", NULL },
 { NULL, '\0', POPT_ARG_INCLUDE_TABLE, helpOptionsTable, 0, \
   "Help options", NULL },
 { NULL, '\0', 0, NULL, 0, NULL, NULL }
@@ -218,7 +229,7 @@
 free(workDir);
 return(0);
 case 'r':
-cygStart(MSDN_URL, NULL, NULL, NULL, SW_NORMAL);
+cygStart(MSDN_URL, NULL, NULL, NULL, SW_NORMAL, verbose);
 poptFreeContext(optCon);
 free(program_name);
 if (action)
@@ -313,6 +324,11 @@
 case 'O':
 show = SW_SHOWNORMAL;
 break;
+
+/* Troubleshooting options */
+case 'E':
+verbose = 1;
+break;
 }
 }
 if (rc < -1 ) {
@@ -360,7 +376,7 @@
 }
 
 /* Start it! */
-ret = cygStart(file, action, args, workDir, show);
+ret = cygStart(file, action, args, workDir, show, verbose);
 
 poptFreeContext(optCon);
 free(program_name);
@@ -378,7 +394,7 @@
 
 /* Start a program, or open a file or URL, using Cygwin POSIX paths */
 static int cygStart(const char *aPath, const char *action, const char *args,
-const char *workDir, int show)
+const char *workDir, int show, int verbose)
 {
 char winPath[MAX_PATH+1];
 char winDir[MAX_PATH+1];
@@ -393,20 +409,25 @@
 /* Convert working directory, if any, from POSIX to Windows */
 if (workDir) {
 cygwin_conv_to_win32_path(workDir, winDir);
-return winStart(winPath, action, args, winDir, show);
+return winStart(winPath, action, args, winDir, show, verbose);
 } else {
-re

Re: cygstart getting The specified file was not found

[Michael Schaap]

Michael Schaap wrote:


normalize_posix_path: /cygdrive/c/WINDOWS/system32/hello.txt = 
normalize_posix_path (hello.txt)

(FWIW, the above strace output is now actually incorrect, prepending 
/cygdrive/c/WINDOWS/system32/, instead of the POSIX current directory, 
to the filename.)



Never mind that.  This is already fixed in the 2006-12-11 snapshot.

- Michael

--
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: Postinstall Problem with 01bash.bat

[Kenneth Evans, Jr.]

I could probably restore my Cygwin directory from a backup and try again.

-Ken

-Original Message-
From: Eric Blake [mailto:[EMAIL PROTECTED] 
Sent: Monday, December 11, 2006 9:24 PM
To: Kenneth Evans, Jr.
Cc: cygwin@cygwin.com
Subject: Re: Postinstall Problem with 01bash.bat

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Kenneth Evans, Jr. on 12/11/2006 8:52 AM:
> Hi,
> 
>> What do the following say?
> 
>> $ ls -l /bin/sh.exe /bin/bash.exe
>> $ bash --version
>> $ sh --version
> 
> C:\Documents and Settings\evans>ls -l /bin/sh.exe /bin/bash.exe
> -rwxrwxrwx 1 evans Users 484352 Dec  6 08:17 /bin/bash.exe
> -rwxrwxrwx 1 evans None  451072 Feb 26  2006 /bin/sh.exe

A permissions problem,...

> 
> C:\Documents and Settings\evans>cp /bin/bash.exe /bin/sh.exe
> cp: cannot create regular file `/bin/sh.exe': Device or resource busy

compounded by the fact that sh was in use at the time.

>
> A dialog says: The procedure entry point rl_getenv_hook could not be
located
> in the link library cygreadline6.dll.  Afterward, I couldn't exit the
> command shell (Eventually I got the not-responding dialog.)

The dialog box is normal when you have the old 3.0 bash as /bin/sh, but
upgraded readline successfully.

> 
> I killed three bash.exe processes and one sh.exe.  Then it ran.  Then I
ran
> setup.exe, and it finished.  Cool.  If I could have found that information
> earlier, it would have saved a lot of time.  There are too many Google
hits
> on this problem.  I guess we still don't know what was wrong, either.

Phooey - now that you have gotten rid of the problem, I can't do any more
debugging via your system.  I'm still trying to reproduce the failure, by
manually sourcing /etc/profile.d/00bash.sh, but so far it seems I am just
catching list users, like you, reporting failure that is solved by a
simple cp, but where the postinstall script did not work.

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFfiDq84KuGfSFAYARArS+AJ9pE6y6XNe8qDw6AFsu1kSppxv4+gCgylnT
ZR2+XhQCg76t0ADgyXIF4AU=
=/HwU
-END PGP SIGNATURE-


--
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: cygstart getting The specified file was not found

[Michael Schaap]

Corinna Vinschen wrote:

On Dec 12 14:23, Michael Schaap wrote:
  

Corinna Vinschen wrote:


Does cygstart use CreateProcess and/or GetCurrentDirectory instead of
fork/exec/getcwd?

If so, cygstart will have to call cygwin_internal(CW_SYNC_WINENV) before
using the native Windows functions.
  
No, it uses ShellExecute (see "cygstart --reference").  It does indeed 
need to sync the environment, but it does this using its own code. 
(Predates cygwin_internal(CW_SYNC_WINENV); I still need to change 
cygstart some day to use it.)



ShellExecute is the same problem.  With 1.7.0 you must use
cygwin_internal(CW_SYNC_WINENV), when calling native Windows functions
which have even vaguely to do with the current directory.

  

Indeed.
I had code to do that which precedes (and even inspired, I think) 
cygwin_internal(CW_SYNC_WINENV), but that did not set the current 
directory, the need for which, I guess, is a new thing.


However, this is unrelated to this problem, things go wrong long before 
that.  It appears that cygwin_conv_to_win32_path incorrectly determines 
the current working directory.


It is called as follows:

cygwin_conv_to_win32_path(aPath, winPath);

where aPath == "hello.txt".

The current directory is "/cygdrive/c/user" =~ "c:\user", but 
cygwin_conv_to_win32_path thinks that:


normalize_posix_path: /cygdrive/c/WINDOWS/system32/hello.txt = 
normalize_posix_path (hello.txt)



Hang on.  cygwin_conv_to_win32_path does not translate the path into
an absolute path, cygwin_conv_to_full_win32_path does that.

  
You're right.  I was fooled by the strace output which seemed to suggest 
that it did.
Indeed, the problem is not filename conversion, but the Windows current 
directory.


(FWIW, the above strace output is now actually incorrect, prepending 
/cygdrive/c/WINDOWS/system32/, instead of the POSIX current directory, 
to the filename.)



I'm running the following simple testcase(tm):

  #include 
  #include 

  int
  main (int argc, char **argv)
  {
char buf[260];

cygwin_conv_to_win32_path (argv[1], buf);
puts (buf);
cygwin_conv_to_full_win32_path (argv[1], buf);
puts (buf);
GetCurrentDirectory (260, buf);
puts (buf);
cygwin_internal (CW_SYNC_WINENV);
GetCurrentDirectory (260, buf);
puts (buf);
return 0;
  }

$ pwd
/home/corinna/tests
$ ./cyg_conv_to_w32 hello.txt
hello.txt
C:\home\corinna\tests\hello.txt
C:\WINDOWS\system32
C:\home\corinna\tests

This shows you what happens.  This is not a bug, but deliberately
chosen.  Use cygwin_internal(CW_SYNC_WINENV), please.

  

Yes, ma'am.  :-)

I've been holding off for a while, since the old code did the job as 
well, and still worked for older Cygwin versions that didn't have 
cygwin_internal (CW_SYNC_WINENV), but I guess the time has come... 
especially since the old code doesn't work anymore.  ;-)


- Michael

--
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: building a cross compiler for linux

[Dave Korn]

On 12 December 2006 09:55, Domen Vrankar wrote:

> I'm using this tutorila: http://x.cygwin.com/docs/cg/prog-build-cross.html
> for building a cygwin cross compiler for linux.
> 
> I built binutils sucessfully but when trying to build gcc I get:
> 
> configure: error: cannot run C compiled programs.
> If you meant to cross compile, use `--host'.
> See `config.log' for more details.
> 
> This happens even though I use --host=i686-pc-linux.

  But you don't mean to cross-compile: you mean to natively compile something
that just happens to be a cross-compiler itself.

  So you should be using --target instead of --host.


cheers,
  DaveK
-- 
Can't think of a witty .sigline today


--
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: cygstart getting The specified file was not found

[Corinna Vinschen]

On Dec 12 08:58, Igor Peshansky wrote:
> On Tue, 12 Dec 2006, Michael Schaap wrote:
> > I went down the list of snapshots, and it looks like this was introduced
> > some time in between 2006-11-27 and 2006-11-30.
> 
> I just looked at the ChangeLog between those two snapshots.  The following
> looks like the culprit change:
> 
> 2006-11-29  Corinna Vinschen  <...>
> 
> * path.cc [snip]
> (cwdstuff::init): Initialize cygheap->cwd with current working
> directory.  Change to windows_system_directory afterwards.
> 
> With that change, any use of non-Cygwin calls, e.g., GetCurrentDirectory,
> or ShellExecute (which calls GetCurrentDirectory under the covers, it
> seems) will produce the problem you're seeing (Windows system directory as
> the current directory).
> 
> So it looks like you ought to call cygwin_internal(CW_SYNC_WINENV) after
> all, as it syncs more than the environment variables...

Right.  The idea is that Cygwin applications are POSIX applications
which use POSIX calls.  If you require Windows calls in your Cygwin
application, you should always call cygwin_internal(CW_SYNC_WINENV)
before doing the Windows calls (if they are working directory related,
yada yada yada).

The idea behind this change (always having system32 as cwd) is this:
POSIX allows to remove a directory, even if this directory is the
current working directory of the process itself, or of any other
process.  This doesn't work on Windows, because every win32 process has
an open handle to its cwd.  Since Cygwin processes are not actually
anymore in the directory which is their cwd, they don't have an open
handle on this dir.  So the dir is removable now, provided there isn't a
native win32 process hanging around in this directory.  This change was
a preparation for the patch which also allows to remove local files
which have an open handle (they are actually now moved to the recycle
bin and marked for "delete on close".

When using cygwin_internal(CW_SYNC_WINENV), Cygwin doesn't only copy the
environment, it also changes into the actual cwd and keeps Cygwin cwd
and native cwd in sync.  This is also propagated to child processes. 
Naturally, this process and its children are blocking the cwd from now
on, until all these processes exited.

A cygwin process not calling native Windows calls never need to call
cygwin_internal(CW_SYNC_WINENV).  fork/exec gets it right automatically,
even if the child process is a native win32 process.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
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: cygstart getting The specified file was not found

[Corinna Vinschen]

On Dec 12 14:23, Michael Schaap wrote:
> Corinna Vinschen wrote:
> >Does cygstart use CreateProcess and/or GetCurrentDirectory instead of
> >fork/exec/getcwd?
> >
> >If so, cygstart will have to call cygwin_internal(CW_SYNC_WINENV) before
> >using the native Windows functions.
> 
> No, it uses ShellExecute (see "cygstart --reference").  It does indeed 
> need to sync the environment, but it does this using its own code. 
> (Predates cygwin_internal(CW_SYNC_WINENV); I still need to change 
> cygstart some day to use it.)

ShellExecute is the same problem.  With 1.7.0 you must use
cygwin_internal(CW_SYNC_WINENV), when calling native Windows functions
which have even vaguely to do with the current directory.

> However, this is unrelated to this problem, things go wrong long before 
> that.  It appears that cygwin_conv_to_win32_path incorrectly determines 
> the current working directory.
> 
> It is called as follows:
> 
> cygwin_conv_to_win32_path(aPath, winPath);
> 
> where aPath == "hello.txt".
> 
> The current directory is "/cygdrive/c/user" =~ "c:\user", but 
> cygwin_conv_to_win32_path thinks that:
> 
> normalize_posix_path: /cygdrive/c/WINDOWS/system32/hello.txt = 
> normalize_posix_path (hello.txt)

Hang on.  cygwin_conv_to_win32_path does not translate the path into
an absolute path, cygwin_conv_to_full_win32_path does that.

I'm running the following simple testcase(tm):

  #include 
  #include 

  int
  main (int argc, char **argv)
  {
char buf[260];

cygwin_conv_to_win32_path (argv[1], buf);
puts (buf);
cygwin_conv_to_full_win32_path (argv[1], buf);
puts (buf);
GetCurrentDirectory (260, buf);
puts (buf);
cygwin_internal (CW_SYNC_WINENV);
GetCurrentDirectory (260, buf);
puts (buf);
return 0;
  }

$ pwd
/home/corinna/tests
$ ./cyg_conv_to_w32 hello.txt
hello.txt
C:\home\corinna\tests\hello.txt
C:\WINDOWS\system32
C:\home\corinna\tests

This shows you what happens.  This is not a bug, but deliberately
chosen.  Use cygwin_internal(CW_SYNC_WINENV), please.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
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: cygstart getting The specified file was not found

[Igor Peshansky]

On Tue, 12 Dec 2006, Igor Peshansky wrote:

> On Tue, 12 Dec 2006, Michael Schaap wrote:
>
> > Michael Schaap wrote:
> > > Corinna Vinschen wrote:
> > > >
> > > > Does cygstart use CreateProcess and/or GetCurrentDirectory instead of
> > > > fork/exec/getcwd?
> > > >
> > > > If so, cygstart will have to call cygwin_internal(CW_SYNC_WINENV)
> > > > before using the native Windows functions.
> > >
> > > No, it uses ShellExecute (see "cygstart --reference").  It does indeed
> > > need to sync the environment, but it does this using its own code.
> > > (Predates cygwin_internal(CW_SYNC_WINENV); I still need to change
> > > cygstart some day to use it.)
> > >
> > > However, this is unrelated to this problem, things go wrong long
> > > before that.  It appears that cygwin_conv_to_win32_path incorrectly
> > > determines the current working directory.
> > >
> > > It is called as follows:
> > >
> > > cygwin_conv_to_win32_path(aPath, winPath);
> > >
> > > where aPath == "hello.txt".
> > >
> > > The current directory is "/cygdrive/c/user" =~ "c:\user", but
> > > cygwin_conv_to_win32_path thinks that:
> > >
> > > normalize_posix_path: /cygdrive/c/WINDOWS/system32/hello.txt =
> > > normalize_posix_path (hello.txt)
> > >
> > > (See Eric's messages for more debugging info.)
> >
> > I just installed the 2006-12-11 snapshot, and I can reproduce this. Like
> > Eric, I'm on XP SP2.
> >
> > I went down the list of snapshots, and it looks like this was introduced
> > some time in between 2006-11-27 and 2006-11-30.
>
> I just looked at the ChangeLog between those two snapshots.  The following
> looks like the culprit change:
>
> 2006-11-29  Corinna Vinschen  

WHOOPS!  Corinna, major apologies for leaving the email address unmunged.
I'm usually more careful than that.

> * path.cc [snip]
> (cwdstuff::init): Initialize cygheap->cwd with current working
> directory.  Change to windows_system_directory afterwards.
>
> With that change, any use of non-Cygwin calls, e.g., GetCurrentDirectory,
> or ShellExecute (which calls GetCurrentDirectory under the covers, it
> seems) will produce the problem you're seeing (Windows system directory as
> the current directory).
>
> So it looks like you ought to call cygwin_internal(CW_SYNC_WINENV) after
> all, as it syncs more than the environment variables...
>   Igor

-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_Igor Peshansky, Ph.D. (name changed!)
 |,4-  ) )-,_. ,\ (  `'-'   old name: Igor Pechtchanski
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Freedom is just another word for "nothing left to lose"...  -- Janis Joplin

--
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: cygstart getting The specified file was not found

[Igor Peshansky]

On Tue, 12 Dec 2006, Michael Schaap wrote:

> Michael Schaap wrote:
> > Corinna Vinschen wrote:
> > >
> > > Does cygstart use CreateProcess and/or GetCurrentDirectory instead of
> > > fork/exec/getcwd?
> > >
> > > If so, cygstart will have to call cygwin_internal(CW_SYNC_WINENV)
> > > before using the native Windows functions.
> >
> > No, it uses ShellExecute (see "cygstart --reference").  It does indeed
> > need to sync the environment, but it does this using its own code.
> > (Predates cygwin_internal(CW_SYNC_WINENV); I still need to change
> > cygstart some day to use it.)
> >
> > However, this is unrelated to this problem, things go wrong long
> > before that.  It appears that cygwin_conv_to_win32_path incorrectly
> > determines the current working directory.
> >
> > It is called as follows:
> >
> > cygwin_conv_to_win32_path(aPath, winPath);
> >
> > where aPath == "hello.txt".
> >
> > The current directory is "/cygdrive/c/user" =~ "c:\user", but
> > cygwin_conv_to_win32_path thinks that:
> >
> > normalize_posix_path: /cygdrive/c/WINDOWS/system32/hello.txt =
> > normalize_posix_path (hello.txt)
> >
> > (See Eric's messages for more debugging info.)
>
> I just installed the 2006-12-11 snapshot, and I can reproduce this. Like
> Eric, I'm on XP SP2.
>
> I went down the list of snapshots, and it looks like this was introduced
> some time in between 2006-11-27 and 2006-11-30.

I just looked at the ChangeLog between those two snapshots.  The following
looks like the culprit change:

2006-11-29  Corinna Vinschen  <[EMAIL PROTECTED]>

* path.cc [snip]
(cwdstuff::init): Initialize cygheap->cwd with current working
directory.  Change to windows_system_directory afterwards.

With that change, any use of non-Cygwin calls, e.g., GetCurrentDirectory,
or ShellExecute (which calls GetCurrentDirectory under the covers, it
seems) will produce the problem you're seeing (Windows system directory as
the current directory).

So it looks like you ought to call cygwin_internal(CW_SYNC_WINENV) after
all, as it syncs more than the environment variables...
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_Igor Peshansky, Ph.D. (name changed!)
 |,4-  ) )-,_. ,\ (  `'-'   old name: Igor Pechtchanski
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Freedom is just another word for "nothing left to lose"...  -- Janis Joplin

--
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: another cygport patch

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Eric Blake on 12/12/2006 6:37 AM:
> Cygport currently makes it impossible to pass arguments to ./configure
> that contain a space.  I need this for building autogen.
> 
> 2006-12-12  Eric Blake  <[EMAIL PROTECTED]>
> 
>   * cygport (cygconf): Preserve shell metacharacters in args.

Better version (verbose had the same bug):

- --- /bin/cygport.orig   2006-12-12 06:35:36.86500 -0700
+++ /bin/cygport2006-12-12 06:40:19.661875000 -0700
@@ -141,7 +141,7 @@
 # displays command to stdout before execution
 verbose() {
echo "[EMAIL PROTECTED]"
- -   [EMAIL PROTECTED]
+   "[EMAIL PROTECTED]"
 }

 # for internal use only
@@ -753,7 +753,7 @@
export ac_cv_func_mmap_fixed_mapped=yes;

verbose ${confdir}/configure --srcdir="${confdir}" ${confargs} \
- -   [EMAIL PROTECTED] ${CYGCONF_ARGS} || error "configure failed"
+   "[EMAIL PROTECTED]" ${CYGCONF_ARGS} || error "configure failed"
 }

 # standard GNU make call


- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFfrIq84KuGfSFAYARAvaAAJ0c/FwGpUaguiNj3/OfPljseFpnuQCfZ/FW
Q9EIjr8wBl1jfEM5H9T3DA0=
=c0NY
-END PGP SIGNATURE-

--
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: cygstart getting The specified file was not found

[Michael Schaap]

Michael Schaap wrote:

Corinna Vinschen wrote:


Does cygstart use CreateProcess and/or GetCurrentDirectory instead of
fork/exec/getcwd?

If so, cygstart will have to call cygwin_internal(CW_SYNC_WINENV) before
using the native Windows functions.



No, it uses ShellExecute (see "cygstart --reference").  It does indeed 
need to sync the environment, but it does this using its own code. 
(Predates cygwin_internal(CW_SYNC_WINENV); I still need to change 
cygstart some day to use it.)


However, this is unrelated to this problem, things go wrong long before 
that.  It appears that cygwin_conv_to_win32_path incorrectly determines 
the current working directory.


It is called as follows:

cygwin_conv_to_win32_path(aPath, winPath);

where aPath == "hello.txt".

The current directory is "/cygdrive/c/user" =~ "c:\user", but 
cygwin_conv_to_win32_path thinks that:


normalize_posix_path: /cygdrive/c/WINDOWS/system32/hello.txt = 
normalize_posix_path (hello.txt)


(See Eric's messages for more debugging info.)



I just installed the 2006-12-11 snapshot, and I can reproduce this. 
Like Eric, I'm on XP SP2.


I went down the list of snapshots, and it looks like this was introduced 
some time in between 2006-11-27 and 2006-11-30.


 - Michael

--
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/

another cygport patch

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Cygport currently makes it impossible to pass arguments to ./configure
that contain a space.  I need this for building autogen.

2006-12-12  Eric Blake  <[EMAIL PROTECTED]>

* cygport (cygconf): Preserve shell metacharacters in args.

- --- /bin/cygport.orig   2006-12-12 06:35:36.86500 -0700
+++ /bin/cygport2006-12-12 06:35:43.86500 -0700
@@ -753,7 +753,7 @@
export ac_cv_func_mmap_fixed_mapped=yes;

verbose ${confdir}/configure --srcdir="${confdir}" ${confargs} \
- -   [EMAIL PROTECTED] ${CYGCONF_ARGS} || error "configure failed"
+   "[EMAIL PROTECTED]" ${CYGCONF_ARGS} || error "configure failed"
 }

 # standard GNU make call


- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFfrCu84KuGfSFAYARAhrtAKCSqeg5IbtMpcfiHgNNCX/aEXmHDgCfVkUq
XLrJi/8ZvsBeG5xYx+TTRV0=
=nwwp
-END PGP SIGNATURE-

--
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: cygstart getting The specified file was not found

[Michael Schaap]

Corinna Vinschen wrote:


Does cygstart use CreateProcess and/or GetCurrentDirectory instead of
fork/exec/getcwd?

If so, cygstart will have to call cygwin_internal(CW_SYNC_WINENV) before
using the native Windows functions.



No, it uses ShellExecute (see "cygstart --reference").  It does indeed 
need to sync the environment, but it does this using its own code. 
(Predates cygwin_internal(CW_SYNC_WINENV); I still need to change 
cygstart some day to use it.)


However, this is unrelated to this problem, things go wrong long before 
that.  It appears that cygwin_conv_to_win32_path incorrectly determines 
the current working directory.


It is called as follows:

cygwin_conv_to_win32_path(aPath, winPath);

where aPath == "hello.txt".

The current directory is "/cygdrive/c/user" =~ "c:\user", but 
cygwin_conv_to_win32_path thinks that:


normalize_posix_path: /cygdrive/c/WINDOWS/system32/hello.txt = 
normalize_posix_path (hello.txt)


(See Eric's messages for more debugging info.)

 - Michael

--
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: building a cross compiler for linux

[Vin Shelton]

Hi Domen,

Domen Vrankar wrote:

I'm using this tutorila: http://x.cygwin.com/docs/cg/prog-build-cross.html
for building a cygwin cross compiler for linux.

I built binutils sucessfully but when trying to build gcc I get:

configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

This happens even though I use --host=i686-pc-linux.

Has annyone an idea why this is happening?

I'm using Debian etch, server with two 32 bit pentium processors



I would strongly recommend the use of crosstool for this.  See
http://www.kegel.com/crosstool/ for details.

Here is some advice from
http://www.kegel.com/crosstool/crosstool-0.42/doc/crosstool-howto.html:

Crosstool, and probably gcc and glibc's configure scripts, assume that 
directory names do not contain any spaces. This is often violated on 
Windows. Please take care to not use directory names with spaces in them 
when running crosstool. It might work, but if it doesn't, you've been 
warned. (Same goes for Mac OS X.)


crosstool creates some really deeply nested directories while building, so 
filenames are quite long. This has two consequences:


First, on some versions of Windows, filenames (including directory) can't be 
longer than 240 chars. To avoid exceeding this limit, don't run crosstool in 
a directory with a long name.


Second, the maximum length of commandlines is extremely short. Since 
crosstool uses commandlines that include multiple filenames, they can exceed 
the limit very quickly. You can avoid this problem by using the "mount" 
command's options. e.g. mount /bin and /usr/bin with -X or "-o cygexec" (see 
the cygwin faq, and/or mount the crosstool directory with "-o managed" (see 
the cygwin doc for "mount").



It's easy to run afoul of either of these two.

HTH,
  Vin Shelton


--
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:20061211snapshot isue( was: rxvt NOT RESPONDING when exiting)

[Rodrigo Medina]

Hi,
The 20061023 snapshot, also presents the problem, but with less frequency.
bye,
RM


--
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:20061211snapshot isue( was: rxvt NOT RESPONDING when exiting)

[Rodrigo Medina]

Hi,
The cygwin1.dll-20061211 malfunctions like the cygwin1.dll-20061205.
bye
RM


--
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:20061211snapshot isue( was: rxvt NOT RESPONDING when exiting)

[Rodrigo Medina]

Sorry,
The snapshot with the problem was the 20061205, not the 20061211, that I
have not
checked.

bye,
RM


--
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/

20061211snapshot isue( was: rxvt NOT RESPONDING when exiting)

[Rodrigo Medina]

Hi,
The problems with rxvt do not appear with the 20061023 snapshot.
XWin also remains active, but desappears from the cygwin list of
processes.

Bye
RM


--
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/

building a cross compiler for linux

[Domen Vrankar]

I'm using this tutorila: http://x.cygwin.com/docs/cg/prog-build-cross.html
for building a cygwin cross compiler for linux.

I built binutils sucessfully but when trying to build gcc I get:

configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

This happens even though I use --host=i686-pc-linux.

Has annyone an idea why this is happening?

I'm using Debian etch, server with two 32 bit pentium processors

r. Domen

--
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: cygstart getting The specified file was not found

[Corinna Vinschen]

On Dec 12 02:58, Michael Schaap wrote:
> ERIC HO wrote:
> >/cygdrive/c/user $cmd /c pwd
> >/cygdrive/c/user
> 
> Hmm, I should have asked for
> $ cmd /c cd
> :-[
> 
> >
> >My cygcheck ouput are attached. Thanks
> >
> 
> Looks like you're running a pretty old Cygwin snapshot:
> Cygwin DLL version info:
> Build date: Thu Nov 30 10:51:28 EST 2006
> Snapshot date: 20061130-10:49:23
> 
> Can you either go back to the latest release (1.5.22), or install the 
> newest snapshot?

Does cygstart use CreateProcess and/or GetCurrentDirectory instead of
fork/exec/getcwd?

If so, cygstart will have to call cygwin_internal(CW_SYNC_WINENV) before
using the native Windows functions.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
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/