public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: alee <alee@IfA.Hawaii.Edu>
To: Kai Ruottu <karuottu@mbnet.fi>
Cc: gcc-help@gcc.gnu.org
Subject: Re: compiling gcc 4.1.1 for AVR
Date: Wed, 27 Sep 2006 09:37:00 -0000	[thread overview]
Message-ID: <451A463F.4070801@ifa.hawaii.edu> (raw)
In-Reply-To: <451A1C7E.20506@mbnet.fi>

Kai Ruottu wrote:

> alee wrote:
>
>> I'm trying to compile gcc 4.1.1 for the AVR platorm.
>
>
> You seem to have achieved your goal already!
>
>> I compiled binutils 2.17 for the AVR platorm already and when I try 
>> to compile gcc,
>
>
> Can you in any way imagine that the subdirectory 'gcc' in the GCC 
> sources could be that
> 'GCC' ?  So when it is "compiled", the compiler(s) called as "GCC" 
> is/are ready!
>
>> I get the following error:
>>
>> ....
>> checking for avr-gcc... 
>> /linux_source/gcc-4.1.1/host-i686-pc-linux-gnu/gcc/xgcc 
>> -B/linux_source/gcc-4.1.1/host-i686-pc-linux-gnu/gcc/ 
>> -B/opt/avr/avr/bin/ -B/opt/avr/avr/lib/ -isystem /opt/avr/avr/include 
>> -isystem /opt/avr/avr/sys-include
>> checking for C compiler default output file name... configure: error: 
>> C compiler cannot create executables
>> See `config.log' for more details.
>> make[1]: *** [configure-target-libssp] Error 1
>
>
> This error tells that the already built "GCC" for AVR cannot create 
> executables with
> the help of the AVR targeted 'as' and 'ld', the AVR targeted C library 
> etc.
>
> Why the GCC build tries to build the 'libssp.a' for AVR as default and 
> whether it is required for
> AVR at all, are the questions you should ask here.  Anyway there 
> should be the GCC configure
> option :
>
> |--disable-libssp|
>    Specify that the run-time libraries for stack smashing protection
>    should not be built.
>
> to disable it's build, so if you think it being not needed, just 
> disable it's build!  A reconfigure
> and a rebuild could show how you could get a clean working build but 
> just as well you could
> try to remove the 'libssp' subdir from the 
> '/linux_source/gcc-4.1.1/host-i686-pc-linux-gnu/avr'
> and then try 'make' again... If this doesn't help, then try removing 
> the 'libssp' "target" from
> the generated main GCC  'Makefile'.
>
>> Where do I get gmp.h?  Do I need it? What else can be wrong?
>
>
> My thought is that you don't need 'libssp' for AVR at all...
>
>
>

Ok...I added the "--disable-libssp" and "make" went further but it stops 
at another error:
.....
Entering directory `/linux_source/gcc-4.1.1/host-i686-pc-linux-gnu/gcc'
gcc -c   -g -O2 -DIN_GCC -DCROSS_COMPILE  -W -Wall -Wwrite-strings 
-Wstrict-prototypes -Wmissing-prototypes -Wmissing-format-attribute    
-DHAVE_CONFIG_H -DGENERATOR_FILE -I. -Ibuild -I../.././gcc 
-I../.././gcc/build -I../.././gcc/../include 
-I../.././gcc/../libcpp/include     -o build/fix-header.o 
../.././gcc/fix-header.c
/opt/avr/bin/avr-as: unrecognized option `-Qy'
make[2]: *** [build/fix-header.o] Error 1
make[2]: Leaving directory 
`/linux_source/gcc-4.1.1/host-i686-pc-linux-gnu/gcc'
make[1]: *** [all-gcc] Error 2
make[1]: Leaving directory `/linux_source/gcc-4.1.1'
make: *** [all] Error 2

What is "make" building here?  Do I have a buggy avr-as?  avr-as doesn't 
have the '-Qy' option...should it?  Or is "make" using avr-as 
incorrectly here?

Thanks.

  reply	other threads:[~2006-09-27  9:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-27  4:03 alee
2006-09-27  6:31 ` Kai Ruottu
2006-09-27  9:37   ` alee [this message]
2006-09-27  9:57     ` Kai Ruottu
2006-09-27 19:47     ` Amit Choudhary

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=451A463F.4070801@ifa.hawaii.edu \
    --to=alee@ifa.hawaii.edu \
    --cc=gcc-help@gcc.gnu.org \
    --cc=karuottu@mbnet.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).