I succeeded to run frankenlibc test programs on TWR-LS1021A board.
I worked on https://github.com/garasubo/frankenlibc/tree/stable-arm .
I use U-Boot and load these test programs and jump to the loaded address.

But I tried to compile the latest master by `./build.sh qemu-arm`, it
failed as follow:
/home/garasubo/workspace/frankenlibc/rump/lib/libc.a(softfloat.o): In
function `__aeabi_i2f':
/home/garasubo/workspace/frankenlibc/src/lib/libc/softfloat/bits64/softfloat.c:1130:
multiple definition of `__aeabi_i2f'
/usr/lib/gcc/arm-none-eabi/4.9.2/libgcc.a(_arm_addsubsf3.o):(.text+0x1d0):
first defined here
/home/garasubo/workspace/frankenlibc/rump/lib/libc.a(softfloat.o): In
function `__aeabi_ui2f':
/home/garasubo/workspace/frankenlibc/src/lib/libc/softfloat/bits64/softfloat.c:1139:
multiple definition of `__aeabi_ui2f'
/usr/lib/gcc/arm-none-eabi/4.9.2/libgcc.a(_arm_addsubsf3.o):(.text+0x1c8):
first defined here
/home/garasubo/workspace/frankenlibc/rump/lib/libc.a(softfloat.o): In
function `__aeabi_i2d':
/home/garasubo/workspace/frankenlibc/src/lib/libc/softfloat/bits64/softfloat.c:1160:
multiple definition of `__aeabi_i2d'
/usr/lib/gcc/arm-none-eabi/4.9.2/libgcc.a(_arm_addsubdf3.o):(.text+0x340):
first defined here
/home/garasubo/workspace/frankenlibc/rump/lib/libc.a(softfloat.o): In
function `__aeabi_ui2d':
/home/garasubo/workspace/frankenlibc/src/lib/libc/softfloat/bits64/softfloat.c:1174:
multiple definition of `__aeabi_ui2d'
/usr/lib/gcc/arm-none-eabi/4.9.2/libgcc.a(_arm_addsubdf3.o):(.text+0x31c):
first defined here
/home/garasubo/workspace/frankenlibc/rump/lib/libc.a(softfloat.o): In
function `__aeabi_f2d':
/home/garasubo/workspace/frankenlibc/src/lib/libc/softfloat/bits64/softfloat.c:1548:
multiple definition of `__aeabi_f2d'
/usr/lib/gcc/arm-none-eabi/4.9.2/libgcc.a(_arm_addsubdf3.o):(.text+0x368):
first defined here
/home/garasubo/workspace/frankenlibc/rump/lib/libc.a(softfloat.o): In
function `extractFloat32Sign':
/home/garasubo/workspace/frankenlibc/src/lib/libc/softfloat/bits64/softfloat.c:247:
multiple definition of `__aeabi_fadd'
/usr/lib/gcc/arm-none-eabi/4.9.2/libgcc.a(_arm_addsubsf3.o):(.text+0xc):
first defined here
/home/garasubo/workspace/frankenlibc/rump/lib/libc.a(softfloat.o): In
function `extractFloat32Sign':
/home/garasubo/workspace/frankenlibc/src/lib/libc/softfloat/bits64/softfloat.c:247:
multiple definition of `__aeabi_fsub'
/usr/lib/gcc/arm-none-eabi/4.9.2/libgcc.a(_arm_addsubsf3.o):(.text+0x8):
first defined here
/home/garasubo/workspace/frankenlibc/rump/lib/libc.a(softfloat.o): In
function `__aeabi_fmul':
/home/garasubo/workspace/frankenlibc/src/lib/libc/softfloat/bits64/softfloat.c:1901:
multiple definition of `__aeabi_fmul'
/usr/lib/gcc/arm-none-eabi/4.9.2/libgcc.a(_arm_muldivsf3.o):(.text+0x0):
first defined here
/home/garasubo/workspace/frankenlibc/rump/lib/libc.a(softfloat.o): In
function `__aeabi_fdiv':
/home/garasubo/workspace/frankenlibc/src/lib/libc/softfloat/bits64/softfloat.c:1962:
multiple definition of `__aeabi_fdiv'
/usr/lib/gcc/arm-none-eabi/4.9.2/libgcc.a(_arm_muldivsf3.o):(.text+0x198):
first defined here
/home/garasubo/workspace/frankenlibc/rump/lib/libc.a(softfloat.o): In
function `extractFloat64Sign':
/home/garasubo/workspace/frankenlibc/src/lib/libc/softfloat/bits64/softfloat.c:416:
multiple definition of `__aeabi_dadd'
/usr/lib/gcc/arm-none-eabi/4.9.2/libgcc.a(_arm_addsubdf3.o):(.text+0xc):
first defined here
/home/garasubo/workspace/frankenlibc/rump/lib/libc.a(softfloat.o): In
function `extractFloat64Sign':
/home/garasubo/workspace/frankenlibc/src/lib/libc/softfloat/bits64/softfloat.c:416:
multiple definition of `__aeabi_dsub'
/usr/lib/gcc/arm-none-eabi/4.9.2/libgcc.a(_arm_addsubdf3.o):(.text+0x8):
first defined here
/home/garasubo/workspace/frankenlibc/rump/lib/libc.a(softfloat.o): In
function `__aeabi_dmul':
/home/garasubo/workspace/frankenlibc/src/lib/libc/softfloat/bits64/softfloat.c:2867:
multiple definition of `__aeabi_dmul'
/usr/lib/gcc/arm-none-eabi/4.9.2/libgcc.a(_arm_muldivdf3.o):(.text+0x0):
first defined here
/home/garasubo/workspace/frankenlibc/rump/lib/libc.a(softfloat.o): In
function `__aeabi_ddiv':
/home/garasubo/workspace/frankenlibc/src/lib/libc/softfloat/bits64/softfloat.c:2926:
multiple definition of `__aeabi_ddiv'
/usr/lib/gcc/arm-none-eabi/4.9.2/libgcc.a(_arm_muldivdf3.o):(.text+0x290):
first defined here
collect2: error: ld returned 1 exit status

*** Failed target:  newfs
*** Failed command:
/home/garasubo/workspace/frankenlibc/rump/bin/arm-rumprun-netbsdelf-eabi-gcc
-o newfs dkcksum.o newfs.o mkfs.o ffs_bswap.o ffs_appleufs.o partutil.o
pathadj.o quota2_subr.o -lutil -lprop
*** Error code 1

Stop.
nbmake: stopped in /home/garasubo/workspace/frankenlibc/src/sbin/newfs

How can I fix this?

Thanks,

Takumi

2015-05-12 20:48 GMT+09:00 Takumi Shimada <[email protected]>:

> I use TWR-LS1021A board.
>
> http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=TWR-LS1021A&uc=true&lang_cd=en
> I'm developing this board as baremetal platform. So I will implement the
> hardware specific boot code.
>
> I'm also planning to use Raspberry Pi 2.
>
>
> 2015-05-12 17:29 GMT+09:00 Justin Cormack <[email protected]>:
>
>> On 12 May 2015 at 08:24, Takumi Shimada <[email protected]> wrote:
>> > Hi,
>> >
>> > I want to develop rumpkernel application on baremetal arm platform.
>> > I tried to compile rumpkernel as following steps:
>> >
>> > I also tried to compile frankenlibc.
>> > But it also failed:
>> >
>> > $ ./build.sh qemu-arm
>> > I think arm-rumprun-netbsdelf-eabi-cc needs "-nostdlib" option.
>> >
>> > Could you tell me how to fix them?
>> >
>>
>> Sorry, frankenlibc is fixed now if you update.
>>
>> Note that there is not one arm baremetal platform, every system is
>> different in terms of startup, devices it supports and so on. NetBSD
>> will have drivers for many of these devices, if it supports the
>> device, but there will still be some work to do. The qemu driver for
>> frankenlibc is very minimal as the emulated system has very few
>> functions; I am planning to do a more functional implementation in a
>> while when the hardware I want becomes available. Which hardware are
>> you interested in?
>>
>> Justin
>>
>
>

Reply via email to