This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: cross gcc - working gcc, but cannot compile C++


Dave,

I'd used some search engines for the -Qy error but never really found
the solution. Your reply prompted me to do that yet again, and I found 

http://www.cygwin.com/ml/cygwin/1997-06/msg00457.html

which basically says

  configure creates a softlink in gcc object directory to the new
version of the cross assembler. Problem is that the native compiler
get confused and use the cross assembler instead of the native one.

So I looked inside the build/gcc/gcc directory and found a file
called "as" with the contents

#!/bin/sh
exec /usr/ppc/bin/arm-wince-pe-as "$@"

Renaming that file made the build progress beyond my initial problem.

I think this is a bug in gcc/g++. Right ?

	Danny

On Mon, 2006-07-24 at 21:05 +0200, Danny Backx wrote:
> I've run ./xgcc -dumpspecs but I don't know what to look at. That one
> doesn't contain the string "Qy". However, when I do the same with my
> native gcc (the one I got from Mandriva), it does contain that :
> 
> *asm:
> %{v:-V} %{Qy:} %{!Qn:-Qy} %{n} %{T} %{Ym,*} %{Yd,*} %{Wa,*:%*}
> 
> You might have noted that the failing command (see my previous mail)
> runs /tmp/gcc-4/bin/gcc (it basically ran "gcc" before, the /tmp path is
> an attempt to see whether getting rid of my Mandriva compiler helped).
> So it runs a normal gcc, but that ends up calling arm-wince-pe-as, which
> is not something I would expect to happen.
> 
> Do I have another cross-binutils in my path ? No, I've taken great care
> to remove all of it at the beginning of my build script. For your
> reference, I'm including part of my build script as attachment, they
> should give you an idea of (1) the order in which I am building things,
> look at build.sh, (2) the exact parameters, look at settings.sh and
> build-gcc.sh .
> 
> Thanks,
> 
> 	Danny
> 
> On Mon, 2006-07-24 at 19:33 +0100, Dave Korn wrote:
> > On 24 July 2006 18:31, Danny Backx wrote:
> > 
> > 
> > > I can build a cross-gcc as long as I tell it to support only C. When
> > > trying to get C++ compiled as well, I always end up getting the error
> > > message below.
> > > 
> > > I've tried patching gas because I had the feeling that gcc is producing
> > > an option that gas doesn't support any more, but somehow I couldn't get
> > > that to work.
> > > 
> > > Is this a gcc bug ?
> > 
> >   Looks like a problem with specs file generation, conceivably some kind of
> > old SysV option.  Might be informative to run "./xgcc -dumpspecs" in the build
> > directory.
> > 
> > > /usr/ppc/bin/arm-wince-pe-as: unrecognized option `-Qy'    
> > > gmake: *** [g++spec.o] Error 1
> > 
> >   Whatever it is, it's been seen before....  lots!
> > 
> > http://www.google.co.uk/search?q=unrecognized+option+Qy&btnG=Search&hl=en&clie
> > nt=firefox-a&rls=org.mozilla%3Aen-GB%3Aofficial
> > 
> >   Is it conceivable that you have another version of cross-binutils in your
> > path, ahead of the arm-wince-pe binutils, and aimed at a different target?
> > What exact configure options did you use when you configured gcc and binutils?
> > 
> > 
> >     cheers,
> >       DaveK
-- 
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info

Attachment: signature.asc
Description: This is a digitally signed message part


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]