[U-Boot] U-boot2013:07-Recompile with -fPIC error for mips64 board
Hi All,
I am cross-compiling u-boot2013-07 for mips64 board.These steps i have followed: 1)I have exported envionment variables CC,LD,AS,CCAS,AR and LD_LIBRARY_PATH. 2)export CROSS_COMPILE=mips64-unknown-elf- 3)make tools 4)make board_config 5)make all Linking error:relocation R_X86_64_32 against `board_init_f' can not be used when making a shared object; recompile with -fPIC /arch/mips/cpu.mips64./../../../lib/start.o: could not read symbols: Bad value.Please provide me pointer to resolve this.
Regards, Krishna
Dear krishna dwivedi,
In message CAKAK--mG07ZxHFzhw=qtVONpfrQS61Q=Ai_mYrLLYg+XmFj=Dw@mail.gmail.com you wrote:
--===============1781805000== Content-Type: multipart/alternative; boundary=047d7bd6c6425eb96b04e02592ae
--047d7bd6c6425eb96b04e02592ae Content-Type: text/plain; charset=ISO-8859-1
Hi All,
I am cross-compiling u-boot2013-07 for mips64 board.These steps i have followed: 1)I have exported envionment variables CC,LD,AS,CCAS,AR and LD_LIBRARY_PATH. 2)export CROSS_COMPILE=mips64-unknown-elf- 3)make tools 4)make board_config 5)make all
This is NOT the noral order of steps. There is no need to build "tools" manually, and in no way this should be done before the config target.
I think I asked this before: which _exact_ machine configuration are you using, i. e. what is your board name?
Best regards,
Wolfgang Denk
Hi Wolfgang,
I am using xlp832 mips64 netlogic board.I referred these steps from u-boot README file. Configuration: TARGET arch CPU BoardName brcm8xx mips mips64 brcm8xx - - Options brcm8xx:SYS_BIG_ENDIAN
Regards, Krishna
On Thu, Jun 27, 2013 at 11:19 PM, Wolfgang Denk wd@denx.de wrote:
Dear krishna dwivedi,
In message <CAKAK--mG07ZxHFzhw=qtVONpfrQS61Q=Ai_mYrLLYg+XmFj= Dw@mail.gmail.com> you wrote:
--===============1781805000== Content-Type: multipart/alternative;
boundary=047d7bd6c6425eb96b04e02592ae
--047d7bd6c6425eb96b04e02592ae Content-Type: text/plain; charset=ISO-8859-1
Hi All,
I am cross-compiling u-boot2013-07 for mips64 board.These steps i have followed: 1)I have exported envionment variables CC,LD,AS,CCAS,AR and
LD_LIBRARY_PATH.
2)export CROSS_COMPILE=mips64-unknown-elf- 3)make tools 4)make board_config 5)make all
This is NOT the noral order of steps. There is no need to build "tools" manually, and in no way this should be done before the config target.
I think I asked this before: which _exact_ machine configuration are you using, i. e. what is your board name?
Best regards,
Wolfgang Denk
-- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de The optimum committee has no members. - Norman Augustine
Gentle Reminder!!
Hi Wolfgang,
Can you please reply on this.
Regards, Krishna
On Fri, Jun 28, 2013 at 10:20 AM, krishna dwivedi < krishna.dwivedi01@gmail.com> wrote:
Hi Wolfgang,
I am using xlp832 mips64 netlogic board.I referred these steps from u-boot README file. Configuration: TARGET arch CPU BoardName brcm8xx mips mips64 brcm8xx
-Options brcm8xx:SYS_BIG_ENDIAN
Regards, Krishna
On Thu, Jun 27, 2013 at 11:19 PM, Wolfgang Denk wd@denx.de wrote:
Dear krishna dwivedi,
In message <CAKAK--mG07ZxHFzhw=qtVONpfrQS61Q=Ai_mYrLLYg+XmFj= Dw@mail.gmail.com> you wrote:
--===============1781805000== Content-Type: multipart/alternative;
boundary=047d7bd6c6425eb96b04e02592ae
--047d7bd6c6425eb96b04e02592ae Content-Type: text/plain; charset=ISO-8859-1
Hi All,
I am cross-compiling u-boot2013-07 for mips64 board.These steps i have followed: 1)I have exported envionment variables CC,LD,AS,CCAS,AR and
LD_LIBRARY_PATH.
2)export CROSS_COMPILE=mips64-unknown-elf- 3)make tools 4)make board_config 5)make all
This is NOT the noral order of steps. There is no need to build "tools" manually, and in no way this should be done before the config target.
I think I asked this before: which _exact_ machine configuration are you using, i. e. what is your board name?
Best regards,
Wolfgang Denk
-- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de The optimum committee has no members. - Norman Augustine
Dear krishna dwivedi,
please don't top post / full quote!!
In message CAKAK--mJC=5_J1awu4=m1evpjPKmmiB0YVnmvqjnca5WZNvR-g@mail.gmail.com you wrote:
Can you please reply on this.
I can reply, but I cannot help you.
I am using xlp832 mips64 netlogic board.I referred these steps from u-boot README file. Configuration: TARGET arch CPU BoardName brcm8xx mips mips64 brcm8xx
-Options brcm8xx:SYS_BIG_ENDIAN
This board is not part of the mainline distribution, so we have never seen the actual code for it. we cannot help you with unknown out-of-tree code. Also, you don't follow the recommended way to build the code, as I've pointed out before.
With out-of-tree code you're basically on your own.
Best regards,
Wolfgang Denk
Hi Wolfgang,
Can you please let me know on which mips board you have compiled this u-boot now.
Regards, Krishna
On Mon, Jul 1, 2013 at 3:28 PM, Wolfgang Denk wd@denx.de wrote:
Dear krishna dwivedi,
please don't top post / full quote!!
In message <CAKAK--mJC=5_J1awu4= m1evpjPKmmiB0YVnmvqjnca5WZNvR-g@mail.gmail.com> you wrote:
Can you please reply on this.
I can reply, but I cannot help you.
I am using xlp832 mips64 netlogic board.I referred these steps from u-boot README file. Configuration: TARGET arch CPU BoardName brcm8xx mips mips64 brcm8xx
-Options brcm8xx:SYS_BIG_ENDIAN
This board is not part of the mainline distribution, so we have never seen the actual code for it. we cannot help you with unknown out-of-tree code. Also, you don't follow the recommended way to build the code, as I've pointed out before.
With out-of-tree code you're basically on your own.
Best regards,
Wolfgang Denk
-- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de That said, there may be good reasons for what you did beyond obsequi- ous sycophantic parody. Perhaps you might be so kind as to elucidate. -- Tom Christiansen in 5ldjbm$jtk$1@csnews.cs.colorado.edu
Krishna,
On 7/1/2013 4:15 PM, krishna dwivedi wrote:
Hi Wolfgang,
Can you please let me know on which mips board you have compiled this u-boot now.
Please understand that the u-boot community supports only those platforms whose support has been mainlined. If you are making changes to the u-boot for your custom board, then the community may not be of much help. For your case, you must contact your hardware provider (Cavium or whatever it is).
You can see all the MIPS boards supported by the community by looking at boards.cfg file.
And please follow the community rules strictly (such as avoiding top posting etc.) if you want a genuine response. Otherwise, your messages would be considered simply as noise and no one would bother to respond.
Regards Amit Virdi
Hi Amit,
Sure.But i am trying to compile U-boot for default board qemu-mips without any changes that is supported in boards.cfg.
Regards, Krishna
On Mon, Jul 1, 2013 at 4:24 PM, Amit Virdi amit.virdi@st.com wrote:
Krishna,
On 7/1/2013 4:15 PM, krishna dwivedi wrote:
Hi Wolfgang,
Can you please let me know on which mips board you have compiled this u-boot now.
Please understand that the u-boot community supports only those platforms whose support has been mainlined. If you are making changes to the u-boot for your custom board, then the community may not be of much help. For your case, you must contact your hardware provider (Cavium or whatever it is).
You can see all the MIPS boards supported by the community by looking at boards.cfg file.
And please follow the community rules strictly (such as avoiding top posting etc.) if you want a genuine response. Otherwise, your messages would be considered simply as noise and no one would bother to respond.
Regards Amit Virdi
participants (3)
-
Amit Virdi -
krishna dwivedi -
Wolfgang Denk