* Linux 2.4.25 from ELDK 3.1 won't compile
@ 2005-05-02 13:25 Peter Asemann
2005-05-02 14:40 ` Wolfgang Denk
0 siblings, 1 reply; 3+ messages in thread
From: Peter Asemann @ 2005-05-02 13:25 UTC (permalink / raw)
To: linuxppc-embedded
I still didn't manage to compile a kernel. Though I unselected as much
features as I could, the compiler still isn't happy. Any ideas?
Peter Asemann
make[1]: Entering directory
`/opt/asemann/eldk/ppc_8xx/usr/src/linux-2.4.25/arch/ppc/kernel'
(...)
ppc_8xx-gcc -D__KERNEL__
-I/opt/asemann/eldk/ppc_8xx/usr/src/linux-2.4.25/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer
-I/opt/asemann/eldk/ppc_8xx/usr/src/linux-2.4.25/arch/ppc -fsigned-char
-msoft-float -pipe -ffixed-r2 -Wno-uninitialized -mmultiple -mstring
-nostdinc -I /opt/asemann/eldk/usr/lib/gcc-lib/ppc-linux/3.3.3/include
-DKBUILD_BASENAME=m8xx_setup -c -o m8xx_setup.o m8xx_setup.c
m8xx_setup.c:64: error: `bd_t' undeclared here (not in a function)
m8xx_setup.c: In function `m8xx_calibrate_decr':
m8xx_setup.c:192: error: `bd_t' undeclared (first use in this function)
m8xx_setup.c:192: error: (Each undeclared identifier is reported only once
m8xx_setup.c:192: error: for each function it appears in.)
m8xx_setup.c:192: error: `binfo' undeclared (first use in this function)
m8xx_setup.c:192: error: parse error before ')' token
m8xx_setup.c:196: error: `IMAP_ADDR' undeclared (first use in this function)
m8xx_setup.c: In function `m8xx_set_rtc_time':
m8xx_setup.c:269: error: `IMAP_ADDR' undeclared (first use in this function)
m8xx_setup.c: In function `m8xx_get_rtc_time':
m8xx_setup.c:279: error: `IMAP_ADDR' undeclared (first use in this function)
m8xx_setup.c: In function `m8xx_restart':
m8xx_setup.c:288: error: `IMAP_ADDR' undeclared (first use in this function)
m8xx_setup.c: In function `m8xx_show_percpuinfo':
m8xx_setup.c:317: error: `bd_t' undeclared (first use in this function)
m8xx_setup.c:317: error: `bp' undeclared (first use in this function)
m8xx_setup.c:319: error: parse error before ')' token
m8xx_setup.c: In function `m8xx_find_end_of_memory':
m8xx_setup.c:377: error: `bd_t' undeclared (first use in this function)
m8xx_setup.c:377: error: `binfo' undeclared (first use in this function)
m8xx_setup.c:380: error: parse error before ')' token
m8xx_setup.c:378: warning: unused variable `__res'
m8xx_setup.c: In function `m8xx_map_io':
m8xx_setup.c:394: error: `IMAP_ADDR' undeclared (first use in this function)
m8xx_setup.c:394: error: `IMAP_SIZE' undeclared (first use in this function)
m8xx_setup.c: In function `platform_init':
m8xx_setup.c:441: error: `bd_t' undeclared (first use in this function)
make[1]: *** [m8xx_setup.o] Error 1
make[1]: Leaving directory
`/opt/asemann/eldk/ppc_8xx/usr/src/linux-2.4.25/arch/ppc/kernel'
make: *** [_dir_arch/ppc/kernel] Error 2
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Linux 2.4.25 from ELDK 3.1 won't compile
2005-05-02 13:25 Linux 2.4.25 from ELDK 3.1 won't compile Peter Asemann
@ 2005-05-02 14:40 ` Wolfgang Denk
0 siblings, 0 replies; 3+ messages in thread
From: Wolfgang Denk @ 2005-05-02 14:40 UTC (permalink / raw)
To: Peter Asemann; +Cc: linuxppc-embedded
In message <42762A58.7090104@web.de> you wrote:
> I still didn't manage to compile a kernel. Though I unselected as much
> features as I could, the compiler still isn't happy. Any ideas?
Which board are you using? Are you sure that the board support is
complete and working? Is there a default configuration for your
board? Does this one work?
Did you RTFM (the DULG, to be precise) ?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Status quo. Latin for "the mess we're in."
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Linux 2.4.25 from ELDK 3.1 won't compile
@ 2005-05-02 14:18 Frank
0 siblings, 0 replies; 3+ messages in thread
From: Frank @ 2005-05-02 14:18 UTC (permalink / raw)
To: Peter Asemann, linuxppc-embedded
--- Peter Asemann <peter.asemann@web.de> wrote:
> I still didn't manage to compile a kernel. Though I unselected
> as much
> features as I could, the compiler still isn't happy. Any
> ideas?
>
> Peter Asemann
>
>
> make[1]: Entering directory
>
`/opt/asemann/eldk/ppc_8xx/usr/src/linux-2.4.25/arch/ppc/kernel'
>
> (...)
>
> ppc_8xx-gcc -D__KERNEL__
> -I/opt/asemann/eldk/ppc_8xx/usr/src/linux-2.4.25/include -Wall
>
> -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing
> -fno-common
> -fomit-frame-pointer
> -I/opt/asemann/eldk/ppc_8xx/usr/src/linux-2.4.25/arch/ppc
> -fsigned-char
> -msoft-float -pipe -ffixed-r2 -Wno-uninitialized -mmultiple
> -mstring
> -nostdinc -I
> /opt/asemann/eldk/usr/lib/gcc-lib/ppc-linux/3.3.3/include
> -DKBUILD_BASENAME=m8xx_setup -c -o m8xx_setup.o m8xx_setup.c
> m8xx_setup.c:64: error: `bd_t' undeclared here (not in a
> function)
> m8xx_setup.c: In function `m8xx_calibrate_decr':
> m8xx_setup.c:192: error: `bd_t' undeclared (first use in this
> function)
> m8xx_setup.c:192: error: (Each undeclared identifier is
> reported only once
> m8xx_setup.c:192: error: for each function it appears in.)
> m8xx_setup.c:192: error: `binfo' undeclared (first use in this
> function)
> m8xx_setup.c:192: error: parse error before ')' token
> m8xx_setup.c:196: error: `IMAP_ADDR' undeclared (first use in
You have to define IMAP_ADDR in your platform header file. Take
a look at arch/ppc/platforms/tqm8xx.h
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-05-02 14:40 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-05-02 13:25 Linux 2.4.25 from ELDK 3.1 won't compile Peter Asemann
2005-05-02 14:40 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2005-05-02 14:18 Frank
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox