public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
* [ECOS] Redboot for i386 won't compile
@ 2001-08-16 16:55 Trenton D. Adams
  2001-08-16 17:55 ` Jonathan Larmour
  0 siblings, 1 reply; 4+ messages in thread
From: Trenton D. Adams @ 2001-08-16 16:55 UTC (permalink / raw)
  To: 'eCos Disuss'

I get the following error when trying to build Redboot for an i386 PC
target.  I would have expected the config tool to not pass to many files
to gcc!

GCC 2.95.2
GUI Config Tool 2.04
Windows 98

make -r -C hal/i386/arch/current build
make[1]: Entering directory
`/f/WorkStuff/PCeCos/eCosBuilds/Redboot_build/hal/i386/arch/current'
i386-elf-gcc -c
-I/cygdrive/F/WorkStuff/PCeCos/eCosBuilds/Redboot_install/include
-I/cygdrive/F/WorkStuff/eCosRepository/ECOS/packages/hal/i386/arch/curre
nt
-I/cygdrive/F/WorkStuff/eCosRepository/ECOS/packages/hal/i386/arch/curre
nt/src
-I/cygdrive/F/WorkStuff/eCosRepository/ECOS/packages/hal/i386/arch/curre
nt/tests -I.
-I/cygdrive/F/WorkStuff/eCosRepository/ECOS/packages/hal/i386/arch/curre
nt/src/ -Wall -Wpointer-arith -Wstrict-prototypes -Winline -Wundef
-Woverloaded-virtual -g -O2 -ffunction-sections -fdata-sections
-fno-rtti -fno-exceptions -fvtable-gc -finit-priority
-Wp,-MD,src/hal_misc.tmp -o src/hal_i386_arch_hal_misc.o
/cygdrive/F/WorkStuff/eCosRepository/ECOS/packages/hal/i386/arch/current
/src/hal_misc.c
make[1]: Leaving directory
`/f/WorkStuff/PCeCos/eCosBuilds/Redboot_build/hal/i386/arch/current'
cpp: too many input files
make: Leaving directory `/f/WorkStuff/PCeCos/eCosBuilds/Redboot_build'
make[1]: *** [src/hal_misc.o.d] Error 1
make: *** [build] Error 2

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [ECOS] Redboot for i386 won't compile
  2001-08-16 16:55 [ECOS] Redboot for i386 won't compile Trenton D. Adams
@ 2001-08-16 17:55 ` Jonathan Larmour
  2001-08-16 19:11   ` Trenton D. Adams
  0 siblings, 1 reply; 4+ messages in thread
From: Jonathan Larmour @ 2001-08-16 17:55 UTC (permalink / raw)
  To: Trenton D. Adams; +Cc: 'eCos Disuss'

"Trenton D. Adams" wrote:
> 
> I get the following error when trying to build Redboot for an i386 PC
> target.  I would have expected the config tool to not pass to many files
> to gcc!

No, it's an odd symptom of a different problem. You moved your tools from
the location in which they were originally configured to be installed. They
don't like this :-). If you can't keep them in their original location, you
can set GCC_EXEC_PREFIX, e.g.

export GCC_EXEC_PREFIX=/foo/bar/H-i686-pc-cygwin/lib/gcc-lib/2.95.2

Note that this will screw up any other gcc's you have, including native
ones, while this is set as it will make them *all* look there for their
files.

GCC 3 doesn't need this any more so it'll be gone in future.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

^ permalink raw reply	[flat|nested] 4+ messages in thread

* RE: [ECOS] Redboot for i386 won't compile
  2001-08-16 17:55 ` Jonathan Larmour
@ 2001-08-16 19:11   ` Trenton D. Adams
  2001-08-16 19:40     ` Jonathan Larmour
  0 siblings, 1 reply; 4+ messages in thread
From: Trenton D. Adams @ 2001-08-16 19:11 UTC (permalink / raw)
  To: 'Jonathan Larmour'; +Cc: 'eCos Disuss'

Oh, cool.  Thanks! :)

Could I put "export GCC_EXEC_PREFIX=/foo/bar/mygcclocation;sh-elf" in my
"Global command prefix" of the GUI Config tool?  That way I wouldn't
have to worry about it screwing it up for my other gcc compiler!

-----Original Message-----
From: jlarmour@cambridge.redhat.com
[ mailto:jlarmour@cambridge.redhat.com ] On Behalf Of Jonathan Larmour
Sent: August 16, 2001 6:55 PM
To: Trenton D. Adams
Cc: 'eCos Disuss'
Subject: Re: [ECOS] Redboot for i386 won't compile


"Trenton D. Adams" wrote:
> 
> I get the following error when trying to build Redboot for an i386 PC 
> target.  I would have expected the config tool to not pass to many 
> files to gcc!

No, it's an odd symptom of a different problem. You moved your tools
from the location in which they were originally configured to be
installed. They don't like this :-). If you can't keep them in their
original location, you can set GCC_EXEC_PREFIX, e.g.

export GCC_EXEC_PREFIX=/foo/bar/H-i686-pc-cygwin/lib/gcc-lib/2.95.2

Note that this will screw up any other gcc's you have, including native
ones, while this is set as it will make them *all* look there for their
files.

GCC 3 doesn't need this any more so it'll be gone in future.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223)
271062 Maybe this world is another planet's Hell -Aldous Huxley ||
Opinions==mine

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [ECOS] Redboot for i386 won't compile
  2001-08-16 19:11   ` Trenton D. Adams
@ 2001-08-16 19:40     ` Jonathan Larmour
  0 siblings, 0 replies; 4+ messages in thread
From: Jonathan Larmour @ 2001-08-16 19:40 UTC (permalink / raw)
  To: Trenton D. Adams; +Cc: 'eCos Disuss'

"Trenton D. Adams" wrote:
> 
> Oh, cool.  Thanks! :)
> 
> Could I put "export GCC_EXEC_PREFIX=/foo/bar/mygcclocation;sh-elf" in my
> "Global command prefix" of the GUI Config tool?  That way I wouldn't
> have to worry about it screwing it up for my other gcc compiler!

No, but you could do:

cd /where.sh-elf-gcc.is
mv sh-elf-gcc sh-elf-gcc-tda
cat >sh-elf-gcc
#!/bin/sh
export GCC_EXEC_PREFIX=/whatever
`basename $0`/sh-elf-gcc-tda $*
^D
chmod +x sh-elf-gcc


-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2001-08-16 19:40 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-08-16 16:55 [ECOS] Redboot for i386 won't compile Trenton D. Adams
2001-08-16 17:55 ` Jonathan Larmour
2001-08-16 19:11   ` Trenton D. Adams
2001-08-16 19:40     ` Jonathan Larmour

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).