Re: problem with cygwin version 1.3.4 cross compilation using gcc
- Original Message - From: Rahul [EMAIL PROTECTED] ... machine where I am compiling it. Am I missing something ? Do I need to do something different while compiling ? Do I need to set PATH variable on another machine ? I have tried looking at cygwin FAQ, User Manual and then turned to this group. Install Cygwin on the second PC. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: problem with cygwin version 1.3.4 cross compilation using gcc
Hi, Install Cygwin on the second PC. Thanks for responding. I was of the opinion that once I have binary/exe I just need cygwin1.dll. This is what impression I get at most of the cygwin website. It sound very odd that for distributing a software that we make using cygwin, we need to have complete cygwin set up on client's machine. Can we have some workaround to this ? Rahul. -Original Message- From: Robert Collins [mailto:[EMAIL PROTECTED]] Sent: Saturday, December 01, 2001 3:19 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: problem with cygwin version 1.3.4 cross compilation using gcc - Original Message - From: Rahul [EMAIL PROTECTED] ... machine where I am compiling it. Am I missing something ? Do I need to do something different while compiling ? Do I need to set PATH variable on another machine ? I have tried looking at cygwin FAQ, User Manual and then turned to this group. Install Cygwin on the second PC. Rob _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: problem with cygwin version 1.3.4 cross compilation using gcc
Rahul, The problem is with the lines: (void) sprintf(tempdirname,/var/testinstall); (void) printf(now creating %s directory\n, tempdirname); if((mkdir(tempdirname,0777)) != 0) throw -1; (void) sprintf(tempdirname,/var/testinstall/testcygwin); (void) printf(now creating %s directory\n, tempdirname); if((mkdir(tempdirname,0777)) != 0) throw -1; Correct? Even if the mkdir function goes through the cygwin1.dll (it may be a simple wrapper for the win32 equivalent, for all I know), the cygwin1.dll has no idea where you have put the root of the cygwin tree. The default is probably C:\cygwin, but I could have it in D:\local\cygwin if I prefer. I would suspect that the registry contains the information as to where the / of a POSIX path is mapped, but however it is stored, your target PC doesn't have it, and won't, unless you install cygwin. Either: 1) Install cygwin on the target PC, so that / has a defined location. 2) Use all Windows pathnames. 3) Hack and kludge registry, etc., to pretend that cygwin is installed. If you choose 3), don't tell your users to ask for installation support here! Eric -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: problem with cygwin version 1.3.4 cross compilation using gcc
=== - Original Message - From: Rahul [EMAIL PROTECTED] To: Robert Collins [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Sunday, December 02, 2001 10:47 AM Subject: RE: problem with cygwin version 1.3.4 cross compilation using gcc Hi, Install Cygwin on the second PC. Thanks for responding. I was of the opinion that once I have binary/exe I just need cygwin1.dll. This is what impression I get at most of the cygwin website. It sound very odd that for distributing a software that we make using cygwin, we need to have complete cygwin set up on client's machine. Can we have some workaround to this ? Eric's more detailed answer address's this. You don't need all the utilities and so forth that are available, but you *DO* need the path and mount table setup correctly. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: problem with cygwin version 1.3.4 cross compilation using gcc
On Sun, Dec 02, 2001 at 12:45:25PM +1100, Robert Collins wrote: === - Original Message - From: Rahul [EMAIL PROTECTED] To: Robert Collins [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Sunday, December 02, 2001 10:47 AM Subject: RE: problem with cygwin version 1.3.4 cross compilation using gcc Hi, Install Cygwin on the second PC. Thanks for responding. I was of the opinion that once I have binary/exe I just need cygwin1.dll. This is what impression I get at most of the cygwin website. It sound very odd that for distributing a software that we make using cygwin, we need to have complete cygwin set up on client's machine. Can we have some workaround to this ? Eric's more detailed answer address's this. You don't need all the utilities and so forth that are available, but you *DO* need the path and mount table setup correctly. You could just use the appropriate UNIX function, aka mount(), to mount the cygwin root in a program. You don't have to install a cygwin distribution to manipulate the mount table. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
