Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <19990917025219.29822.rocketmail@web123.yahoomail.com> Date: Thu, 16 Sep 1999 19:52:19 -0700 (PDT) From: Earnie Boyd Reply-To: earnie_boyd AT yahoo DOT com Subject: Re: Building mingw32-x-h8300 tools To: "Michael K. Elwood" , cygwin cygwin , crossgcc AT sourceware DOT cygnus DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- "Michael K. Elwood" wrote: > Well, since nobody wanted to solve my problem for me, I had to go solve it > myself. But the problem (and solution) may be interesting to people trying > to build mingw32-hosted cross tools, or to mingw32 people in general. -8<- > lib/gcc-lib/h8300-hms/2.95/ directory) contains some cpp arguments like > > -D__SIZE_TYPE__=unsigned\ int > > cpp hates that space in the value, so you really need double quotes around > the "unsigned\ int" part. So I fixed the specs file by surrounding these > values with double quotes. Everything seemed great...only it didn't fix the > problem. Back to GDB. I wonder if you'd used -D__SIZE_TYPE__=unsigned^ int if it would have worked. It has to do with M$ character quoting and the \ character only character quotes the " character and the \ character. To quote anything else you need to use the ^ character. > > When gcc goes to spawn cpp, it calls pexecute() in libiberty, which in turn > calls the Win32 _spawnv or _spawnvp function. Just before it does this, the > mingw32 pexecute() calls fix_argv(), which scans every string in the argv > array and escapes any double quotes with a preceding \. Instead of helping, > though, this just confused cpp. So i took out the call to fix_argv(). > Presto! Everything worked. :) > Hey, it feels good to have done a splendid job. > I now have a working mingw32-hosted h8300-targeted GNU cross compiler > (version 2.95). Many thanks to Mumit Khan and others who have helped along > the way. I can provide a patch for the changed files if anybody is > interested. > > Now a question: Is fix_argv() still necessary? It seems to be causing more > harm than good. > I don't know the answer. === Earnie Boyd Newbies, please visit (If you respond to the list, then please don't cc me) __________________________________________________ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com