This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos 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: IDT79RC334


Update......
I have mounted the /tmp binary as for the FAQ page and I am still getting
the following error when I compile gcc. Binutils built fine and installed
ok.... I am under cygwin verson as of 4 days ago, and source files right off
of the web site for ecos. Any ideas? I am stumped. I am going to try to
build for another processor and see what happens.
Thanks
Jim

<SNIP>
gcc -DIN_GCC -DHAVE_CONFIG_H -DIN_GCC -DCROSS_COMPILE -g -O2 -W -Wall -Wwrit
e-st
rings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-
long
-long -DHAVE_CONFIG_H -DGENERATOR_FILE  -W -Wall -Wwrite-strings -Wstrict-pr
otot
ypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -I. -I.. -I
/src
/gcc-3.2.1/gcc/fixinc -I/src/gcc-3.2.1/gcc/fixinc/.. -I/src/gcc-3.2.1/gcc/fi
xinc
/../config -I/src/gcc-3.2.1/gcc/fixinc/../../include  -o fixincl.exe
fixincl.o f
ixtests.o fixfixes.o server.o procopen.o gnu-regex.o fixlib.o
../../libiberty/li
biberty.a
gnu-regex.o(.text+0x6556): In function `regerror':
/src/gcc-3.2.1/gcc/fixinc/gnu-regex.c:5723: undefined reference to
`___mempcpy'
collect2: ld returned 1 exit status
make[2]: *** [full-stamp] Error 1
make[2]: Leaving directory `/tmp/build/gcc/gcc/fixinc'
make[1]: *** [fixinc.sh] Error 2
make[1]: Leaving directory `/tmp/build/gcc/gcc'
make: *** [all-gcc] Error 2
make: Leaving directory `/tmp/build/gcc'




-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com
[mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of James
Robinson
Sent: Monday, June 09, 2003 6:49 PM
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] IDT79RC334


Hello List,
I am trying to build the toolkit for the IDT 334 processor. I am using
mipsisa32-elf. Is this the right one? The tool chain fails under the gcc
build with unresolved external. I am now rebuilding everything and following
the instructions to the letter off the web site. I build under
/work/build/gcc but I am now trying the /tmp/build/gcc. I don't see why the
directory would make a difference........
Anyhooo.......
Any input would be great.
James Robinson
PS..
I have the IDT 334 Eval board to work with.

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.483 / Virus Database: 279 - Release Date: 5/19/2003


--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.483 / Virus Database: 279 - Release Date: 5/19/2003

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.488 / Virus Database: 287 - Release Date: 6/5/2003


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss


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