From: "Felipe Gil Castiñeira" <xil@uvigo.es>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] AmigaOneG3SE_config: sys/types.h: No such file or directory
Date: Tue, 24 Jan 2006 11:40:04 +0100 [thread overview]
Message-ID: <43D60404.1030102@uvigo.es> (raw)
In-Reply-To: <OF503B3181.ACCA0D7C-ON48257100.0023B231@uk.marconicomms.com>
Hi,
I have recently build the bios emulator included in AmigaOneG3. As you say,
there is not "sys/types.h", but that is only the first error (there are lots
more). If you search the mailing list, there is a thread
(http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/20068) with the
answer
from Wolfgang:
"I'm afraid you have to dig through this mess - unfortunately the
AmigaOneG3SE port has never been really maintained."
"Problems are caused by the unmaintained source
tree for this board."
I managed to compile the code for a MPC5200 board, but my VGA initialization
test is in standby until I receive a board with the "B" revision of the
MPC5200.
Best regards,
Felipe.
KokHow Teh wrote:
>Hi;
> I try to build AmigaOneG3SE_config target to see if the bios_emulator
>builds fine but I bump into "sys/types.h not found" error. True enough,
>there is no sys directory in u-boot.
>
><snip>
>make[1]: Entering directory `/home/teh/cvs/u-boot/board/MAI/AmigaOneG3SE'
>/opt/eldk-ppc-linux-x86/usr/bin/ppc_74xx-gcc -M -g -Os -fPIC -ffixed-r14 -meabi -fno-strict-aliasing -D__KERNEL__ -DTEXT_BASE=0xfff00000
>-I/home/teh/cvs/u-boot/include -fno-builtin -ffreestanding -nostdinc -isystem /opt/eldk-ppc-linux-x86/usr/bin/../lib/gcc-lib/ppc-linux/3.3.3/include
>-pipe -DCONFIG_PPC -D__powerpc__ -DCONFIG_74xx_7xx -ffixed-r2 -ffixed-r29 -mstring -DTEXT_BASE=0xfff00000 -Wa,-mregnames -DEASTEREGG
>-I../bios_emulator/scitech/include -I../bios_emulator/scitech/src/x86emu -Dprintk=printf -Wall -Wstrict-prototypes board_asm_init.S memio.S
>AmigaOneG3SE.c articiaS.c flash.c serial.c smbus.c articiaS_pci.c via686.c i8259.c ../bios_emulator/x86interface.c ../bios_emulator/bios.c
>../bios_emulator/glue.c interrupts.c ps2kbd.c video.c usb_uhci.c enet.c ../menu/cmd_menu.c cmd_boota.c nvram.c > .depend
>AmigaOneG3SE.c:32:7: missing terminating " character
>AmigaOneG3SE.c:74:1: missing terminating " character
>In file included from ../bios_emulator/scitech/include/x86emu.h:50,
> from ../bios_emulator/x86interface.c:1:
>../bios_emulator/scitech/include/x86emu/types.h:42:23: sys/types.h: No such file or directory
>In file included from ../bios_emulator/scitech/include/x86emu.h:50,
> from ../bios_emulator/bios.c:6:
>../bios_emulator/scitech/include/x86emu/types.h:42:23: sys/types.h: No such file or directory
>../bios_emulator/glue.c:51:24: pasting "mypci_read_cfg_byte" and "(" does not give a valid preprocessing token
>../bios_emulator/glue.c:51:24: pasting "pci_read_config_byte" and "(" does not give a valid preprocessing token
>../bios_emulator/glue.c:52:25: pasting "mypci_read_cfg_word" and "(" does not give a valid preprocessing token
>../bios_emulator/glue.c:52:25: pasting "pci_read_config_word" and "(" does not give a valid preprocessing token
>../bios_emulator/glue.c:54:25: pasting "mypci_write_cfg_byte" and "(" does not give a valid preprocessing token
>../bios_emulator/glue.c:54:25: pasting "pci_write_config_byte" and "(" does not give a valid preprocessing token
>../bios_emulator/glue.c:55:26: pasting "mypci_write_cfg_word" and "(" does not give a valid preprocessing token
>../bios_emulator/glue.c:55:26: pasting "pci_write_config_word" and "(" does not give a valid preprocessing token
>make[1]: *** [.depend] Error 1
>make[1]: Leaving directory `/home/teh/cvs/u-boot/board/MAI/AmigaOneG3SE'
>make: *** [board/MAI/AmigaOneG3SE/libAmigaOneG3SE.a] Error 2
>[teh at ShrekII u-boot 9]$ find . -name sys -print
>[teh at ShrekII u-boot 10]$
>
> Environment problem? Any insight is appreciated.
>
>Regards,
>TEH
>
>
>
>
prev parent reply other threads:[~2006-01-24 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 6:34 [U-Boot-Users] AmigaOneG3SE_config: sys/types.h: No such file or directory KokHow Teh
2006-01-24 10:40 ` Felipe Gil Castiñeira [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=43D60404.1030102@uvigo.es \
--to=xil@uvigo.es \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.