something, please correct me.
Best Regards,
KJ
寄件者： Arthur Wong [EMAIL PROTECTED]
收件者： uClinux development list uclinux-dev@uclinux.org
寄件日期： 2008/12/5(星期五) 上午10:50:09
主 旨： Re: [uClinux-dev] Compiler library libgcc.a for uClinux
It's a interesting discussion
Lin KJ wrote:
- The compiler version newer than gcc-4.x can NOT be used for XIP uClinux
because of the
R_ARM_GOTOFF32 relocation type. It will produce the R_ARM_GOTOFF32
relocation which will be resolved by adding a negative offset from the
GOT. However,
in the
@uclinux.org
寄件日期： 2008/12/4(星期四) 下午8:00:18
主 旨： Re: [uClinux-dev] Compiler library libgcc.a for uClinux
Hi KJ,
Lin KJ wrote:
Thanks for your detailed information.
But i am still puzzled.
You mentioned that the uClinux binaries do not necessarily have to be
XIP and can be run on non-XIP
： 2008/12/5(星期五) 下午1:24:03
主 旨： Re: [uClinux-dev] Compiler library libgcc.a for uClinux
After make clean and make, however, it is failed on the elf2flt stage.
I got the following repeated error messages.
ERROR: reloc type R_ARM_PC24 unsupported in this context
ERROR: reloc type R_ARM_PLT32
Gavin Lambert wrote:
dist/vendors/config/armnommu/config.arch file?
Usually in your board-specific config.arch file (not the generic armnommu one
-- the one that you selected in the toplevel Makefile) there are three lines
like this:
# DISABLE_XIP := 1 # XIP works fine
#
Hi Jamie,
Jamie Lokier wrote:
Gavin Lambert wrote:
dist/vendors/config/armnommu/config.arch file?
Usually in your board-specific config.arch file (not the generic armnommu one
-- the one that you selected in the toplevel Makefile) there are three lines
like this:
# DISABLE_XIP := 1
-dev@uclinux.org
寄件日期： 2008/12/4(星期四) 上午7:47:03
主 旨： Re: [uClinux-dev] Compiler library libgcc.a for uClinux
Hi KJ,
Lin KJ wrote:
I wonder whether the arm-linux- toolchains recommend by the uClinux website
can be used for ARM uClinux world.
They can, I use them to create running systems.
(I
: [uClinux-dev] Compiler library libgcc.a for uClinux
Hi KJ,
Lin KJ wrote:
Thanks for your detailed information.
But i am still puzzled.
You mentioned that the uClinux binaries do not necessarily have to be XIP
and can be run on non-XIP mode.
How do i switch to run non-XIP uClinux
Hi All,
I wonder whether the arm-linux- toolchains recommend by the uClinux website
can be used for ARM uClinux world.
The compiler library libgcc.a will be an issue.
Since XIP code is must for uClinux, the libgcc.a must be produced by the XIP
compiling flags.
For ARM, it will be -fpic
Hi KJ,
Lin KJ wrote:
I wonder whether the arm-linux- toolchains recommend by the uClinux website
can be used for ARM uClinux world.
They can, I use them to create running systems.
(I always test the GDB/ARMultaor uClinux target with those arm-linux
toolchains).
The compiler library
[EMAIL PROTECTED]
收件者： uClinux development list uclinux-dev@uclinux.org
寄件日期： 2008/12/4(星期四) 上午7:47:03
主 旨： Re: [uClinux-dev] Compiler library libgcc.a for uClinux
Hi KJ,
Lin KJ wrote:
I wonder whether the arm-linux- toolchains recommend by the uClinux website
can be used for ARM uClinux world
Quoth Lin KJ:
You mentioned that the uClinux binaries do not necessarily have to be
XIP and can be run on non-XIP mode.
How do i switch to run non-XIP uClinux?
Bypass the -fpic -msingle-pic-base CFLAGS and use some
specific elf2flt options?
If uClinux could be non-XIP, why the -fpic
12 matches
Mail list logo
