Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 13 May 2003 15:18:53 -0400 From: DEEPA SIVASANKARANE Subject: Re: Cygwin Net - Compilation To: cygwin AT cygwin DOT com MIME-Version: 1.0 Message-Id: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Yes, it was a mistake. Now , I went to the DOS prompt, cd C:\cygwin\bin Do I do a mount "c:\cygwin" "/" or just mount "/" ? I did the latter as u suggested, alongwith mount "/usr/lib" mount "/usr/bin" it did'nt work.. Sorry for the truble :-),pls. help. thanx, regards, Deepa ---- Original message ---- >Date: Tue, 13 May 2003 14:52:36 -0400 (EDT) >From: Igor Pechtchanski >Subject: Re: Cygwin Net - Compilation >To: DEEPA SIVASANKARANE >Cc: cygwin AT cygwin DOT com > >Deepa, > >Now, what in the world possessed you to do *that*? >Run cmd.exe, cd to your cygwin bin directory (probably c:\cygwin\bin), and >you'll be able to run mount from there. You will need at least three >mounts: "/", "/usr/bin", and "/usr/lib". > >Next time, before "umount"ing, run "mount -m >/bin/restore_mounts.bat". >Then you'll be able to undo your commands by simply "cd c:\cygwin\bin ^ >restore_mounts" > Igor > >On Tue, 13 May 2003, DEEPA SIVASANKARANE wrote: > >> Hi Igor, >> >> I did a umount -A, and I ran bash again. Now I'm not >> able to execute anything, including mount. >> What do I do ? >> >> thanx, >> Deepa >> >> ---- Original message ---- >> >Date: Tue, 13 May 2003 14:00:41 -0400 (EDT) >> >From: Igor Pechtchanski >> >Subject: Re: Cygwin Net - Compilation >> >To: DEEPA SIVASANKARANE >> >Cc: cygwin AT cygwin DOT com >> > >> >Deepa, >> > >> >See . You may also be able to >> >run the old toolset by setting your cygdrive prefix to "//" (the >> >obvious way, "mount -u -c //", won't work, but you can circumvent it by >> >using "mount -u -c '/\'") -- *NOTE that this will make you unable to >> >access any network share from that user account!* >> > Igor >> >P.S. Try passing the -specs=FILE option to umsgcc -- that should make >> >it read the specs from FILE, unless they *really* diverged from the gcc >> >codebase. >> > >> >On Tue, 13 May 2003, DEEPA SIVASANKARANE wrote: >> > >> >> Thanx, Igor. Shall work on getting the new toolset, with >> >> configure options changed. >> >> Unfortunately, umsgcc does'nt read from a "specs" file >> >> like gcc, but uses "built-in specs". >> >> >> >> BTW, the new syntax for drives is just /c or /cygdrive/c ? >> >> >> >> Thanx again, >> >> best regards, >> >> Deepa >> >> >> >> >> >> ---- Original message ---- >> >> >Date: Mon, 12 May 2003 16:30:27 -0400 (EDT) >> >> >From: Igor Pechtchanski >> >> >Subject: Re: Cygwin Net - Compilation >> >> >To: DEEPA SIVASANKARANE >> >> >Cc: cygwin AT cygwin DOT com >> >> > >> >> >On Mon, 12 May 2003, DEEPA SIVASANKARANE wrote: >> >> > >> >> >> Hi folks, >> >> >> >> >> >> I'm using a certain arch. specific gcc (umsgcc) for >> >> >> compilation, whose specs are as below. It looks like >> >> >> "umsgcc" was compiled in a Redhat Cygwin environment ? >> >> >> >> >> >> This is the one available to me and when I try to >> >> >> use it on Cygwin Net release, there were some "file >> >> >> not found" errors, tho the files were there and I had >> >> >> used "-I" option to include the directory. >> >> >> Could anybody pls. help or suggest something ? >> >> >> >> >> >> Thanx in advance, >> >> >> best regards, >> >> >> Deepa >> >> >> >> >> >> ----------------------------------------------------- --- >> >> >> Using builtin specs. >> >> >> Configured with: //d/sanjiv/proj/tools/redhat/configure --host=i686-pc- cygwin --target=cra8500-elf --prefix=//f/redhat/cradle --exec- prefix=//f/redhat/cradle/H-i686-pc-cygwin >> >> >> UMSGCC version 3.2.042 (with gcc version 2.97-cradle- 011011) >> >> > >> >> >Deepa, >> >> > >> >> >The configure options above use the old syntax for different drives. >> >> >The newer Cygwin DLLs (starting from 1.3.1, I think) interpret the >> >> >above as, for example, the share "redhat" on server "f" (which you >> >> >most likely don't have, thus the errors). It probably takes quite a >> >> >bit of time, too. >> >> > >> >> >I'm not sure what you mean by "this is the only one available" -- >> >> >Cygwin has a "gcc" package... Unless you mean "available for that >> >> >target architecture". >> >> > >> >> >One way to fix this is to recompile the toolchain by providing the >> >> >correct options to configure. Another is to provide your own specs >> >> >file (which is not mentioned above, BTW, use - dumpspecs for that). >> >> >See the gcc info page for the format of the specs file. >> >> > Igor > >-- > http://cs.nyu.edu/~pechtcha/ > |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu >ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com > |,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 Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/