Kaan Akşit schrieb:
$ avr-gcc -mmcu=atmega8 -v -c demo.c
Using built-in specs.
COLLECT_GCC=avr-gcc
Target: avr
Configured with: ../configure --target=avr --mandir=/usr/share/man
You still configure in the source tree which is not supported.
Johann
On Tue, Jul 31, 2012 at 05:09:44PM +0300, Kaan Akşit wrote:
> I have exported the path, if I compile avr-gcc without export; it ends up
> compiling without the previous warning and this time the below error
> appears:
>
> Configuring in avr/libgcc
> configure: creating cache ./config.cache
> check
I am using below code to configure avr-gcc, I don't understand what is
wrong with it:
../configure --target=avr --mandir=/usr/share/man --datadir=/usr/share
--prefix=/usr/share/avr --enable-languages="c,c++" --disable-nls
--disable-libssp --with-dwarf2 --with-system-zlib
--enable-version-specific-
On Wed, Aug 01, 2012 at 12:35:47PM +0300, Kaan Akşit wrote:
> I am using below code to configure avr-gcc, I don't understand what is
> wrong with it:
>
> ../configure --target=avr --mandir=/usr/share/man --datadir=/usr/share
> --prefix=/usr/share/avr --enable-languages="c,c++" --disable-nls
> --di
I am really confused because if I do not set any prefix during
configuration; both avr-gcc and avr-binutils will use /usr/local which
means default is not the supported way.
So to give an example if I use prefix /usr/local for avr-binutils, should I
be using something outside of /usr/local ? For e
On Wed, Aug 01, 2012 at 03:19:58PM +0300, Kaan Akşit wrote:
> I am really confused because if I do not set any prefix during
> configuration; both avr-gcc and avr-binutils will use /usr/local which
> means default is not the supported way.
>
> So to give an example if I use prefix /usr/local for a