Re: Problem building cross-debugger

["Gerrit van Niekerk" <gerritvn@gpvno.co.za>]

On 13 Feb 2008 at 9:49, Michael Shatz wrote:
> Finally found the problem.
> 
> It's all about cygwin "textmode" mount huck.
> When the build drive (or may be source, or both, in my case they were the
> same) is mounted in the text mode the following command misbehaves:
> /bin/sh ./libtool --tag=CC --mode=link i686-pc-cygwin-gcc -W -Wall
> -Wstrict-prototypes -Wmissing-prototypes -Werror -g -O2   -o libbfd.la
> -rpath /usr/local/emb386/i686-pc-cygwin/i386-elf/lib -release `cat
> libtool-soversion`  archive.lo archures.lo bfd.lo bfdio.lo bfdwin.lo
> cache.lo coffgen.lo corefile.lo format.lo init.lo libbfd.lo opncls.lo
> reloc.lo section.lo syms.lo targets.lo hash.lo linker.lo srec.lo binary.lo
> tekhex.lo ihex.lo stabs.lo stab-syms.lo merge.lo dwarf2.lo simple.lo `cat
> ofiles`  
> 
> Either 'libtool' or, more likely, 'sh' somehow ignores the tail of the
> 'ofiles' file which happens to contain the  cpu-i386.o
> 
> When running from binary-mounted drive everything compiles as expected.

Must admit: I don't know much about Cygwin - basically run the Cygwin 
Bash shell and enter the rquired commands which do not include mounting 
anything. What do I have to change to do a binary mount?
-- 
Gerrit van Niekerk
GP van Niekerk Ondernemings BK
Roosstraat 211, Meyerspark, 0184, South Africa
Tel: +27(12)8036501 Fax SA: 0866 413 555
Cell: +27(73)6891370
Fax Int'l: +1(206)2034139
Email: gerritvn@gpvno.co.za
Web: http://www.gpvno.co.za