Editing make process?
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
https://github.com/swarren/u-boot — I have this, need to get the binary so I can finally run something other than Raspbian on the Pi.
The instructions are:
"cd" to directory.. derp.
"make rpi_2_defconfig"
"make all"
However, this is how things turn out ---
[*userredacted*@*machineredacted* u-boot-tegra_dev] $ make rpi_2_defconfig
HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
SHIPPED scripts/kconfig/zconf.tab.c
SHIPPED scripts/kconfig/zconf.lex.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
#
# configuration written to .config
#
[user/machineredacted* u-boot-tegra_dev] $ make all
scripts/kconfig/conf --silentoldconfig Kconfig
CHK include/config.h
UPD include/config.h
GEN include/autoconf.mk
GEN include/autoconf.mk.dep
CHK include/config/uboot.release
UPD include/config/uboot.release
CHK include/generated/version_autogenerated.h
UPD include/generated/version_autogenerated.h
CHK include/generated/timestamp_autogenerated.h
UPD include/generated/timestamp_autogenerated.h
CC lib/asm-offsets.s
lib/asm-offsets.c:1:0: error: bad value (armv5) for -march= switch
/*
^
Kbuild:43: recipe for target 'lib/asm-offsets.s' failed
make[1]: *** [lib/asm-offsets.s] Error 1
Makefile:1216: recipe for target 'prepare0' failed
make: *** [prepare0] Error 2
How do I go about making it skip even caring about anything armv5 related?
Or maybe there's a simple label to satisfy it so that the process completes?
From what I know, this is the author's mistake for not defining such.
edit---
For just a bit of story.. absolutely nothing will boot besides NOOBS and berryboot. The bootcode.bin will not be read at all with it partitioned for Arch (500MB fat16 with boot & lba flags and a second ext4 for root, simple extract to the partitions) nor with the official Ubuntu MATE image. Speaking of berryboot, every OS on the list (which doesn't include Ubuntu or Arch) fails immediately upon trying, complaining of a sha checksum mismatch.
I realize there's a Pi section on SE.. but since all else has failed, and they'll probably just suggest I use NOOBS (which doesn't offer any install of anything anymore besides Raspbian).
So I want u-boot so that I can control booting and add what the hell I want.
If anyone would like to compile it for me (or anyone else having issues with "make" in this or similar instance) then it'd be appreciated <3
Still, let's answer the question. ..maybe not specifically as-worded in the title.
How can this process be edited to allow the completion of the program and to complete and materialize the binary from u-boot's source code?
compiling raspberry-pi make source u-boot
edited Dec 8 at 0:17
Rui F Ribeiro
38.7k1479128
asked Jul 17 '15 at 23:10
Reimy
112
add a comment |
up vote
0
down vote
favorite
https://github.com/swarren/u-boot — I have this, need to get the binary so I can finally run something other than Raspbian on the Pi.
The instructions are:
"cd" to directory.. derp.
"make rpi_2_defconfig"
"make all"
However, this is how things turn out ---
[*userredacted*@*machineredacted* u-boot-tegra_dev] $ make rpi_2_defconfig
HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
SHIPPED scripts/kconfig/zconf.tab.c
SHIPPED scripts/kconfig/zconf.lex.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
#
# configuration written to .config
#
[user/machineredacted* u-boot-tegra_dev] $ make all
scripts/kconfig/conf --silentoldconfig Kconfig
CHK include/config.h
UPD include/config.h
GEN include/autoconf.mk
GEN include/autoconf.mk.dep
CHK include/config/uboot.release
UPD include/config/uboot.release
CHK include/generated/version_autogenerated.h
UPD include/generated/version_autogenerated.h
CHK include/generated/timestamp_autogenerated.h
UPD include/generated/timestamp_autogenerated.h
CC lib/asm-offsets.s
lib/asm-offsets.c:1:0: error: bad value (armv5) for -march= switch
/*
^
Kbuild:43: recipe for target 'lib/asm-offsets.s' failed
make[1]: *** [lib/asm-offsets.s] Error 1
Makefile:1216: recipe for target 'prepare0' failed
make: *** [prepare0] Error 2
How do I go about making it skip even caring about anything armv5 related?
Or maybe there's a simple label to satisfy it so that the process completes?
From what I know, this is the author's mistake for not defining such.
edit---
For just a bit of story.. absolutely nothing will boot besides NOOBS and berryboot. The bootcode.bin will not be read at all with it partitioned for Arch (500MB fat16 with boot & lba flags and a second ext4 for root, simple extract to the partitions) nor with the official Ubuntu MATE image. Speaking of berryboot, every OS on the list (which doesn't include Ubuntu or Arch) fails immediately upon trying, complaining of a sha checksum mismatch.
I realize there's a Pi section on SE.. but since all else has failed, and they'll probably just suggest I use NOOBS (which doesn't offer any install of anything anymore besides Raspbian).
So I want u-boot so that I can control booting and add what the hell I want.
If anyone would like to compile it for me (or anyone else having issues with "make" in this or similar instance) then it'd be appreciated <3
Still, let's answer the question. ..maybe not specifically as-worded in the title.
How can this process be edited to allow the completion of the program and to complete and materialize the binary from u-boot's source code?
compiling raspberry-pi make source u-boot
edited Dec 8 at 0:17
Rui F Ribeiro
38.7k1479128
asked Jul 17 '15 at 23:10
Reimy
112
Regarding the actual problem as opposed to the actual question (I know, I know, SE is all about questions, not the OP well being, excuse me in advance). There are installation instructions here that worked perfectly for me. I found it far easier to use multiple sd cards, than using a (still quite) buggy boot loader. You have to follow the instructions exactly... No 500MB boot partition for instance.
– user123418
Jul 18 '15 at 3:46
By the way RPi 2 is completely different from RPi (aka RPi 1)
– user123418
Jul 18 '15 at 3:50
On what machine are you doing the compilation? With what compiler? It looks like your compilation is choking on the first step that requires a compiler for ARM, so you're either missing a (probably cross-)compiler or not indicating its name correctly. The Pi has an ARM processor, so you are going to need to be able to compile for ARM.
– Gilles
Jul 18 '15 at 13:53
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
https://github.com/swarren/u-boot — I have this, need to get the binary so I can finally run something other than Raspbian on the Pi.
The instructions are:
"cd" to directory.. derp.
"make rpi_2_defconfig"
"make all"
However, this is how things turn out ---
[*userredacted*@*machineredacted* u-boot-tegra_dev] $ make rpi_2_defconfig
HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
SHIPPED scripts/kconfig/zconf.tab.c
SHIPPED scripts/kconfig/zconf.lex.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
#
# configuration written to .config
#
[user/machineredacted* u-boot-tegra_dev] $ make all
scripts/kconfig/conf --silentoldconfig Kconfig
CHK include/config.h
UPD include/config.h
GEN include/autoconf.mk
GEN include/autoconf.mk.dep
CHK include/config/uboot.release
UPD include/config/uboot.release
CHK include/generated/version_autogenerated.h
UPD include/generated/version_autogenerated.h
CHK include/generated/timestamp_autogenerated.h
UPD include/generated/timestamp_autogenerated.h
CC lib/asm-offsets.s
lib/asm-offsets.c:1:0: error: bad value (armv5) for -march= switch
/*
^
Kbuild:43: recipe for target 'lib/asm-offsets.s' failed
make[1]: *** [lib/asm-offsets.s] Error 1
Makefile:1216: recipe for target 'prepare0' failed
make: *** [prepare0] Error 2
How do I go about making it skip even caring about anything armv5 related?
Or maybe there's a simple label to satisfy it so that the process completes?
From what I know, this is the author's mistake for not defining such.
edit---
For just a bit of story.. absolutely nothing will boot besides NOOBS and berryboot. The bootcode.bin will not be read at all with it partitioned for Arch (500MB fat16 with boot & lba flags and a second ext4 for root, simple extract to the partitions) nor with the official Ubuntu MATE image. Speaking of berryboot, every OS on the list (which doesn't include Ubuntu or Arch) fails immediately upon trying, complaining of a sha checksum mismatch.
I realize there's a Pi section on SE.. but since all else has failed, and they'll probably just suggest I use NOOBS (which doesn't offer any install of anything anymore besides Raspbian).
So I want u-boot so that I can control booting and add what the hell I want.
If anyone would like to compile it for me (or anyone else having issues with "make" in this or similar instance) then it'd be appreciated <3
Still, let's answer the question. ..maybe not specifically as-worded in the title.
How can this process be edited to allow the completion of the program and to complete and materialize the binary from u-boot's source code?
compiling raspberry-pi make source u-boot
edited Dec 8 at 0:17
Rui F Ribeiro
38.7k1479128
asked Jul 17 '15 at 23:10
Reimy
112
https://github.com/swarren/u-boot — I have this, need to get the binary so I can finally run something other than Raspbian on the Pi.
The instructions are:
"cd" to directory.. derp.
"make rpi_2_defconfig"
"make all"
However, this is how things turn out ---
[*userredacted*@*machineredacted* u-boot-tegra_dev] $ make rpi_2_defconfig
HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
SHIPPED scripts/kconfig/zconf.tab.c
SHIPPED scripts/kconfig/zconf.lex.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
#
# configuration written to .config
#
[user/machineredacted* u-boot-tegra_dev] $ make all
scripts/kconfig/conf --silentoldconfig Kconfig
CHK include/config.h
UPD include/config.h
GEN include/autoconf.mk
GEN include/autoconf.mk.dep
CHK include/config/uboot.release
UPD include/config/uboot.release
CHK include/generated/version_autogenerated.h
UPD include/generated/version_autogenerated.h
CHK include/generated/timestamp_autogenerated.h
UPD include/generated/timestamp_autogenerated.h
CC lib/asm-offsets.s
lib/asm-offsets.c:1:0: error: bad value (armv5) for -march= switch
/*
^
Kbuild:43: recipe for target 'lib/asm-offsets.s' failed
make[1]: *** [lib/asm-offsets.s] Error 1
Makefile:1216: recipe for target 'prepare0' failed
make: *** [prepare0] Error 2
How do I go about making it skip even caring about anything armv5 related?
Or maybe there's a simple label to satisfy it so that the process completes?
From what I know, this is the author's mistake for not defining such.
edit---
For just a bit of story.. absolutely nothing will boot besides NOOBS and berryboot. The bootcode.bin will not be read at all with it partitioned for Arch (500MB fat16 with boot & lba flags and a second ext4 for root, simple extract to the partitions) nor with the official Ubuntu MATE image. Speaking of berryboot, every OS on the list (which doesn't include Ubuntu or Arch) fails immediately upon trying, complaining of a sha checksum mismatch.
I realize there's a Pi section on SE.. but since all else has failed, and they'll probably just suggest I use NOOBS (which doesn't offer any install of anything anymore besides Raspbian).
So I want u-boot so that I can control booting and add what the hell I want.
If anyone would like to compile it for me (or anyone else having issues with "make" in this or similar instance) then it'd be appreciated <3
Still, let's answer the question. ..maybe not specifically as-worded in the title.
How can this process be edited to allow the completion of the program and to complete and materialize the binary from u-boot's source code?
compiling raspberry-pi make source u-boot
compiling raspberry-pi make source u-boot
edited Dec 8 at 0:17
Rui F Ribeiro
38.7k1479128
asked Jul 17 '15 at 23:10
Reimy
112
edited Dec 8 at 0:17
Rui F Ribeiro
38.7k1479128
asked Jul 17 '15 at 23:10
Reimy
112
edited Dec 8 at 0:17
Rui F Ribeiro
38.7k1479128
edited Dec 8 at 0:17
Rui F Ribeiro
38.7k1479128
edited Dec 8 at 0:17
Rui F Ribeiro
38.7k1479128
38.7k1479128
asked Jul 17 '15 at 23:10
Reimy
112
asked Jul 17 '15 at 23:10
Reimy
112
asked Jul 17 '15 at 23:10
Reimy
112
112
Regarding the actual problem as opposed to the actual question (I know, I know, SE is all about questions, not the OP well being, excuse me in advance). There are installation instructions here that worked perfectly for me. I found it far easier to use multiple sd cards, than using a (still quite) buggy boot loader. You have to follow the instructions exactly... No 500MB boot partition for instance.
– user123418
Jul 18 '15 at 3:46
By the way RPi 2 is completely different from RPi (aka RPi 1)
– user123418
Jul 18 '15 at 3:50
On what machine are you doing the compilation? With what compiler? It looks like your compilation is choking on the first step that requires a compiler for ARM, so you're either missing a (probably cross-)compiler or not indicating its name correctly. The Pi has an ARM processor, so you are going to need to be able to compile for ARM.
– Gilles
Jul 18 '15 at 13:53
add a comment |
Regarding the actual problem as opposed to the actual question (I know, I know, SE is all about questions, not the OP well being, excuse me in advance). There are installation instructions here that worked perfectly for me. I found it far easier to use multiple sd cards, than using a (still quite) buggy boot loader. You have to follow the instructions exactly... No 500MB boot partition for instance.
– user123418
Jul 18 '15 at 3:46
By the way RPi 2 is completely different from RPi (aka RPi 1)
– user123418
Jul 18 '15 at 3:50
On what machine are you doing the compilation? With what compiler? It looks like your compilation is choking on the first step that requires a compiler for ARM, so you're either missing a (probably cross-)compiler or not indicating its name correctly. The Pi has an ARM processor, so you are going to need to be able to compile for ARM.
– Gilles
Jul 18 '15 at 13:53
Regarding the actual problem as opposed to the actual question (I know, I know, SE is all about questions, not the OP well being, excuse me in advance). There are installation instructions here that worked perfectly for me. I found it far easier to use multiple sd cards, than using a (still quite) buggy boot loader. You have to follow the instructions exactly... No 500MB boot partition for instance.
– user123418
Jul 18 '15 at 3:46
Regarding the actual problem as opposed to the actual question (I know, I know, SE is all about questions, not the OP well being, excuse me in advance). There are installation instructions here that worked perfectly for me. I found it far easier to use multiple sd cards, than using a (still quite) buggy boot loader. You have to follow the instructions exactly... No 500MB boot partition for instance.
– user123418
Jul 18 '15 at 3:46
By the way RPi 2 is completely different from RPi (aka RPi 1)
– user123418
Jul 18 '15 at 3:50
By the way RPi 2 is completely different from RPi (aka RPi 1)
– user123418
Jul 18 '15 at 3:50
On what machine are you doing the compilation? With what compiler? It looks like your compilation is choking on the first step that requires a compiler for ARM, so you're either missing a (probably cross-)compiler or not indicating its name correctly. The Pi has an ARM processor, so you are going to need to be able to compile for ARM.
– Gilles
Jul 18 '15 at 13:53
On what machine are you doing the compilation? With what compiler? It looks like your compilation is choking on the first step that requires a compiler for ARM, so you're either missing a (probably cross-)compiler or not indicating its name correctly. The Pi has an ARM processor, so you are going to need to be able to compile for ARM.
– Gilles
Jul 18 '15 at 13:53
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
I tried to comment out the -march=armv5 option in the "arch/arm/Makefile"
arch-$(CONFIG_CPU_V7) =$(call cc-option, -march=armv7-a, -march=armv5)
But with this I was getting unsupported commands error used as memory barriers written in armv5 assembly.
Most likely these commands (mcr) written in lib/asm_offset.c need to be re-written in armv7 assembly, or maybe they are not required in v7.
I think these builds were working for earlier version of gcc-arm-gnueabi compilers. If there is a possibility of setting the version used in the command-line for building your u-boot then surely it might work (this is purely a guess as I am not aware of that option available).
edited Jul 19 '15 at 12:42
user1794469
1,3531622
answered Jul 19 '15 at 11:51
user3301096
11
After reading some blog response from Robert Nelson I found that instead of passing/using $CC as it is in the command line we need to export the CROSS_COMPILER explicitly in the command line and not pass it along with the make commands. This worked for me, hope it works for you as well.
– user3301096
Jul 19 '15 at 12:05
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f216850%2fediting-make-process%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I tried to comment out the -march=armv5 option in the "arch/arm/Makefile"
arch-$(CONFIG_CPU_V7) =$(call cc-option, -march=armv7-a, -march=armv5)
But with this I was getting unsupported commands error used as memory barriers written in armv5 assembly.
Most likely these commands (mcr) written in lib/asm_offset.c need to be re-written in armv7 assembly, or maybe they are not required in v7.
I think these builds were working for earlier version of gcc-arm-gnueabi compilers. If there is a possibility of setting the version used in the command-line for building your u-boot then surely it might work (this is purely a guess as I am not aware of that option available).
edited Jul 19 '15 at 12:42
user1794469
1,3531622
answered Jul 19 '15 at 11:51
user3301096
11
After reading some blog response from Robert Nelson I found that instead of passing/using $CC as it is in the command line we need to export the CROSS_COMPILER explicitly in the command line and not pass it along with the make commands. This worked for me, hope it works for you as well.
– user3301096
Jul 19 '15 at 12:05
add a comment |
up vote
0
down vote
I tried to comment out the -march=armv5 option in the "arch/arm/Makefile"
arch-$(CONFIG_CPU_V7) =$(call cc-option, -march=armv7-a, -march=armv5)
But with this I was getting unsupported commands error used as memory barriers written in armv5 assembly.
Most likely these commands (mcr) written in lib/asm_offset.c need to be re-written in armv7 assembly, or maybe they are not required in v7.
I think these builds were working for earlier version of gcc-arm-gnueabi compilers. If there is a possibility of setting the version used in the command-line for building your u-boot then surely it might work (this is purely a guess as I am not aware of that option available).
edited Jul 19 '15 at 12:42
user1794469
1,3531622
answered Jul 19 '15 at 11:51
user3301096
11
After reading some blog response from Robert Nelson I found that instead of passing/using $CC as it is in the command line we need to export the CROSS_COMPILER explicitly in the command line and not pass it along with the make commands. This worked for me, hope it works for you as well.
– user3301096
Jul 19 '15 at 12:05
add a comment |
up vote
0
down vote
up vote
0
down vote
I tried to comment out the -march=armv5 option in the "arch/arm/Makefile"
arch-$(CONFIG_CPU_V7) =$(call cc-option, -march=armv7-a, -march=armv5)
But with this I was getting unsupported commands error used as memory barriers written in armv5 assembly.
Most likely these commands (mcr) written in lib/asm_offset.c need to be re-written in armv7 assembly, or maybe they are not required in v7.
I think these builds were working for earlier version of gcc-arm-gnueabi compilers. If there is a possibility of setting the version used in the command-line for building your u-boot then surely it might work (this is purely a guess as I am not aware of that option available).
edited Jul 19 '15 at 12:42
user1794469
1,3531622
answered Jul 19 '15 at 11:51
user3301096
11
I tried to comment out the -march=armv5 option in the "arch/arm/Makefile"
arch-$(CONFIG_CPU_V7) =$(call cc-option, -march=armv7-a, -march=armv5)
But with this I was getting unsupported commands error used as memory barriers written in armv5 assembly.
Most likely these commands (mcr) written in lib/asm_offset.c need to be re-written in armv7 assembly, or maybe they are not required in v7.
I think these builds were working for earlier version of gcc-arm-gnueabi compilers. If there is a possibility of setting the version used in the command-line for building your u-boot then surely it might work (this is purely a guess as I am not aware of that option available).
edited Jul 19 '15 at 12:42
user1794469
1,3531622
answered Jul 19 '15 at 11:51
user3301096
11
edited Jul 19 '15 at 12:42
user1794469
1,3531622
edited Jul 19 '15 at 12:42
user1794469
1,3531622
edited Jul 19 '15 at 12:42
user1794469
1,3531622
1,3531622
answered Jul 19 '15 at 11:51
user3301096
11
answered Jul 19 '15 at 11:51
user3301096
11
answered Jul 19 '15 at 11:51
user3301096
11
11
After reading some blog response from Robert Nelson I found that instead of passing/using $CC as it is in the command line we need to export the CROSS_COMPILER explicitly in the command line and not pass it along with the make commands. This worked for me, hope it works for you as well.
– user3301096
Jul 19 '15 at 12:05
add a comment |
After reading some blog response from Robert Nelson I found that instead of passing/using $CC as it is in the command line we need to export the CROSS_COMPILER explicitly in the command line and not pass it along with the make commands. This worked for me, hope it works for you as well.
– user3301096
Jul 19 '15 at 12:05
After reading some blog response from Robert Nelson I found that instead of passing/using $CC as it is in the command line we need to export the CROSS_COMPILER explicitly in the command line and not pass it along with the make commands. This worked for me, hope it works for you as well.
– user3301096
Jul 19 '15 at 12:05
After reading some blog response from Robert Nelson I found that instead of passing/using $CC as it is in the command line we need to export the CROSS_COMPILER explicitly in the command line and not pass it along with the make commands. This worked for me, hope it works for you as well.
– user3301096
Jul 19 '15 at 12:05
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f216850%2fediting-make-process%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Regarding the actual problem as opposed to the actual question (I know, I know, SE is all about questions, not the OP well being, excuse me in advance). There are installation instructions here that worked perfectly for me. I found it far easier to use multiple sd cards, than using a (still quite) buggy boot loader. You have to follow the instructions exactly... No 500MB boot partition for instance.
– user123418
Jul 18 '15 at 3:46
By the way RPi 2 is completely different from RPi (aka RPi 1)
– user123418
Jul 18 '15 at 3:50
On what machine are you doing the compilation? With what compiler? It looks like your compilation is choking on the first step that requires a compiler for ARM, so you're either missing a (probably cross-)compiler or not indicating its name correctly. The Pi has an ARM processor, so you are going to need to be able to compile for ARM.
– Gilles
Jul 18 '15 at 13:53