From: Yurij Grechishhev <yurij.grechishhev@gmail.com>
To: ecos discuss <ecos-discuss@sourceware.org>
Subject: Re: [ECOS] error while compiling insight 6.8
Date: Fri, 29 Jun 2012 06:50:00 -0000 [thread overview]
Message-ID: <CAAyhtXTqbkdqc-dQ_WbJY4W7voSicBmNNWEec_tgKH7UfHGXgw@mail.gmail.com> (raw)
In-Reply-To: <1340916037.61714.YahooMailNeo@web193205.mail.sg3.yahoo.com>
You can try to configure this way:
./configure --disable-werror
2012/6/29 abhishek srivastava <just_abhi22@yahoo.co.in>
>
> hi
> i have getting error while compiling insight 6.8a/6.8-1a for gdb.
> after ./configure when i do make,i get following error.
>
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.././bfd -I. -DTRAD_CORE -I. -I.././bfd -I.././bfd/../include -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Werror -g -O2 -c -DDEBUGDIR=\"/usr/local/lib/debug\" .././bfd/dwarf2.c -o dwarf2.o
> /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.././bfd -I. -DTRAD_CORE -I. -I.././bfd -I.././bfd/../include -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Werror -g -O2 -c -o simple.lo simple.c
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.././bfd -I. -DTRAD_CORE -I. -I.././bfd -I.././bfd/../include -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Werror -g -O2 -c simple.c -o simple.o
> rm -f elf32-target.h
> sed -e s/NN/32/g < .././bfd/elfxx-target.h > elf32-target.new
> mv -f elf32-target.new elf32-target.h
> /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.././bfd -I. -DTRAD_CORE -I. -I.././bfd -I.././bfd/../include -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Werror -g -O2 -c -o elf32-i386.lo elf32-i386.c
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.././bfd -I. -DTRAD_CORE -I. -I.././bfd -I.././bfd/../include -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Werror -g -O2 -c elf32-i386.c -o elf32-i386.o
> elf32-i386.c: In function 'elf_i386_relocate_section':
> elf32-i386.c:2635:16: error: variable 'warned' set but not used [-Werror=unused-but-set-variable]
> cc1: all warnings being treated as errors
> make[4]: *** [elf32-i386.lo] Error 1
> make[4]: Leaving directory `/home/abhi/ecos/gnutools/i386-elf/insight/insight-6.8/bfd'
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory `/home/abhi/ecos/gnutools/i386-elf/insight/insight-6.8/bfd'
> make[2]: *** [all] Error 2
> make[2]: Leaving directory `/home/abhi/ecos/gnutools/i386-elf/insight/insight-6.8/bfd'
> make[1]: *** [all-bfd] Error 2
> make[1]: Leaving directory `/home/abhi/ecos/gnutools/i386-elf/insight/insight-6.8'
> make: *** [all] Error 2
> abhi@abhi-HP:~/ecos/gnutools/i386-elf/insight/insight-6.8$
>
>
> please help
>
>
>
> Abhishek
>
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
--
With best regards!
____________________________
Yurij Grechishhev
Bauman State Technical University,
Department of Computer Systems and Networks
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2012-06-29 6:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 20:41 abhishek srivastava
2012-06-29 6:50 ` Yurij Grechishhev [this message]
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=CAAyhtXTqbkdqc-dQ_WbJY4W7voSicBmNNWEec_tgKH7UfHGXgw@mail.gmail.com \
--to=yurij.grechishhev@gmail.com \
--cc=ecos-discuss@sourceware.org \
/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).