From: "Cliff Tsai" <clifftsai@minecard.com.tw>
To: "Keith Seitz" <keiths@cygnus.com>
Cc: <gdb@sources.redhat.com>
Subject: Re: insight+dejagnu-20010417 build error on arm-elf(libgdb.a:remote-rdi.o)!
Date: Fri, 20 Apr 2001 22:02:00 -0000 [thread overview]
Message-ID: <009401c0ca20$19a853c0$b200a8c0@minecard.com.tw> (raw)
In-Reply-To: <Pine.SOL.3.91.1010420100215.2271E-100000@ryobi.cygnus.com>
----- Original Message -----
From: "Keith Seitz" <keiths@cygnus.com>
To: "Cliff Tsai" <clifftsai@minecard.com.tw>
Cc: <gdb@sources.redhat.com>
Sent: Saturday, April 21, 2001 1:08 AM
Subject: Re: insight+dejagnu-20010417 build error on
arm-elf(libgdb.a:remote-rdi.o)!
> On Fri, 20 Apr 2001, Cliff Tsai wrote:
>
> > The "head config.status" is
> >
/src/gdb/insight_dejagnu-20010417/configure --host=i586-pc-cygwin --target=a
> > rm-elf
> > --prefix=/tools --exec-prefix=/tools/arm-elf -v --norecursion.
> >
> > My configure command is:
> > /src/gdb/insight_dejagnu-20010417/configure --target=arm-elf \
> > --prefix=/tools --exec-prefix=/tools/arm-elf -v 2>&1 | tee configure.out
> >
> > By the way,I just use 0420 snapshot,the same error occur!
>
> I just retrieved this snapshot and built it on both windows and linux
> without any problems...
>
> Is libangsd.a being built? Does the directory OBJDIR/gdb/rdi-share exist
> and contain anything? What do the last few lines of your final link look
> like? Mine look like:
>
> rm -f libangsd.a
> ar cru libangsd.a ardi.o angel_bytesex.o crc.o devsw.o drivers.o
etherdrv.o hostchan.o hsys.o logging.o msgbuild.o params.o rx.o serdrv.o
serpardr.o tx.o unixcomm.o
> ranlib libangsd.a
> make[2]: Leaving directory `/home/keiths/arm-elf/gdb/rdi-share'
> rm -f gdb.exe
> gcc -g -O2 -Wl,--subsystem,console -o gdb.exe \
> main.o libgdb.a cli-decode.o cli-script.o cli-cmds.o cli-setshow.o
cli-utils.o gdbtk.o gdbtk-cmds.o gdbtk-hooks.o gdbtk-varobj.o
gdbtk-wrapper.o gdbres.o rdi-share/libangsd.a ../sim/arm/libsim.a
../bfd/libbfd.a ../readline/libreadline.a ../opcodes/libopc
> odes.a ./../intl/libintl.a ../libiberty/libiberty.a `if test -r
../libtermcap/libtermcap.a; then echo ../libtermcap/libtermcap.a; else
echo -ltermcap; fi`
../libgui/src/libgui.a -L/home/keiths/arm-elf/itcl/itcl/win -litcl30 -L/home
/keiths/arm-elf/itcl/
>
itk/win -litk30 -L/home/keiths/arm-elf/tix/win/tcl8.0 -ltix4180 -L/home/keit
hs/arm-elf/tk/win -ltk80 -L/home/keiths/arm-elf/tcl/win -ltcl80 -lm -lm
../libiberty/libiberty.a -luser32 -lshell32 -lgdi32 -lcomdlg32 -ladvapi32\
>
> What does "uname -a" say?
>
> Keith
>
Keith:thank you very much
(1) Yes!libangsd.a exists.And There are some .o in my build library
(xxx/gdb/rdi-share)
(2) But I can't find any information about libangsd.a in my "make.out"
(3) uname -a say=>CYGWIN_98-4.10 CLIFF 1.1.8(0.34/3/2) 2001-01-03 10:58 i586
unknown.
Do I need a newer version of cygwin? But I encounter another problem
after install newer version of
cygwin when build insight!
By the way!I wanna know can I build the insight for arm-elf that set
big_endian as default?
I've seen few lines in \gdb\config\arm\tm-arm.h about endian.
How can I do to set arm-elf take big_endian as default?
Or Where can I set in order for insight(build for little-endian as default)
to accept big_endian elf-image.
/*tm-arm.h*/
/* Target byte order on ARM defaults to selectable, and defaults to
little endian. */
#define TARGET_BYTE_ORDER_SELECTABLE_P 1
#define TARGET_BYTE_ORDER_DEFAULT LITTLE_ENDIAN
/* IEEE format floating point. */
#define IEEE_FLOAT (1)
#define TARGET_DOUBLE_FORMAT (target_byte_order == BIG_ENDIAN \
? &floatformat_ieee_double_big \
: &floatformat_ieee_double_littlebyte_bigword)
.....
Thank you.
next prev parent reply other threads:[~2001-04-20 22:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <002301c0c985$b0bd4040$b200a8c0@minecard.com.tw>
2001-04-20 10:08 ` Keith Seitz
2001-04-20 22:02 ` Cliff Tsai [this message]
2001-04-24 11:58 ` Keith Seitz
[not found] <015501c0c890$920f5ca0$b200a8c0@minecard.com.tw>
2001-04-19 8:43 ` Keith Seitz
2001-04-19 10:52 ` Keith Seitz
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='009401c0ca20$19a853c0$b200a8c0@minecard.com.tw' \
--to=clifftsai@minecard.com.tw \
--cc=gdb@sources.redhat.com \
--cc=keiths@cygnus.com \
/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