<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Thanks, that is what I am missing.<br>
<br>
I have a configuration derived from src/soc/intel/baytrail and
didn't notice the new selections.<br>
<br>
Sean<br>
<br>
On 05/11/2014 10:52 AM, Furquan Shaikh wrote:<br>
</div>
<blockquote
cite="mid:CALYf1SP1p0k5x5TYKmTU-O=UR+wvMEc7Eq5EXecYUjqHtdyw9w@mail.gmail.com"
type="cite">
<div dir="ltr">Ah okay!
<div><br>
</div>
<div>1) What board are you trying this for? Does it use a
different cpu / soc than the ones for which we have support
upstream?</div>
<div><br>
</div>
<div>2) The variables ARCH-*-y depend on the config variables
ARCH_*_X86_32 selected in cpu/soc specific Kconfig files.
E.g.: In file <span
style="color:rgb(0,0,0);font-family:sans-serif;font-weight:bold"> </span>src<span
style="color:rgb(0,0,0);font-family:sans-serif;font-weight:bold">/</span>cpu<span
style="color:rgb(0,0,0);font-family:sans-serif;font-weight:bold">/</span>intel<span
style="color:rgb(0,0,0);font-family:sans-serif;font-weight:bold">/</span>haswell<span
style="color:rgb(0,0,0);font-family:sans-serif;font-weight:bold">/</span>Kconfig,
the options selected are:</div>
select ARCH_BOOTBLOCK_X86_32<br>
select ARCH_ROMSTAGE_X86_32<br>
select ARCH_RAMSTAGE_X86_32
<div>
<div class="gmail_extra"><font color="#000000"
face="monospace"><span
style="font-size:12.222222328186035px;white-space:pre"><br>
</span></font>Make sure that architecture is specified for
each of the three stages i.e. bootblock, romstage and
ramstage.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sat, May 10, 2014 at 8:18 PM,
Sean McNeil <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:seanmcneil3@gmail.com" target="_blank">seanmcneil3@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>The below commit has already been merged and does
not resolve the issue. My /bin/sh is also a symlink
to bash.<br>
<br>
It appears to be 2 things:<br>
<br>
1) I don't have the following definitions anywhere<br>
<br>
ARCH-BOOTBLOCK-y := i386<br>
ARCH-ROMSTAGE-y := i386<br>
ARCH-RAMSTAGE-y := i386<br>
<br>
this is what causes the command not found problems.<br>
<br>
2) target build/cbfs/fallback/bootblock.bin is
missing. It looks the same in the older codebase
Makefile.inc and perhaps is a side-affect of the
bootblock class?
<div>
<div class="h5"><br>
<br>
On 05/11/2014 01:10 AM, Furquan Shaikh wrote:<br>
</div>
</div>
</div>
<div>
<div class="h5">
<blockquote type="cite">This CL has been submitted
which should fix the issue:<br>
<br>
<a moz-do-not-send="true"
href="http://review.coreboot.org/#/c/5701/"
target="_blank">http://review.coreboot.org/#/c/5701/</a><br>
<br>
<br>
<p dir="ltr">On Saturday, May 10, 2014 3:02:44
AM, Sean McNeil <<a moz-do-not-send="true"
href="mailto:seanmcneil3@gmail.com"
target="_blank">seanmcneil3@gmail.com</a>>
wrote:</p>
<blockquote>
<p dir="ltr">Up until recently, compiling
coreboot with the options </p>
<p dir="ltr">CONFIG_COMPILER_GCC=y <br>
CONFIG_ANY_TOOLCHAIN=y </p>
<p dir="ltr">on a 64-bit linux system worked
just fine. Over the last few days I now get
the errors: </p>
<p dir="ltr">make <br>
Warning: no suitable GCC for armv7. <br>
Warning: no suitable GCC for aarch64. <br>
/bin/sh: -print-libgcc-file-name: command
not found <br>
/bin/sh: -print-libgcc-file-name: command
not found <br>
/bin/sh: -print-libgcc-file-name: command
not found <br>
/bin/sh: -print-libgcc-file-name: command
not found <br>
/bin/sh: -print-libgcc-file-name: command
not found <br>
/bin/sh: -print-libgcc-file-name: command
not found <br>
# <br>
# configuration written to .config <br>
# <br>
make: *** No rule to make target
`build/cbfs/fallback/bootblock.bin', needed
by `build/coreboot.pre1'. Stop. </p>
<p dir="ltr">--<br>
coreboot mailing list: <a
moz-do-not-send="true"
href="mailto:coreboot@coreboot.org"
target="_blank">coreboot@</a><a
moz-do-not-send="true"
href="mailto:coreboot@coreboot.org"
target="_blank">coreboot.org</a><br>
<a moz-do-not-send="true"
href="http://www.coreboot.org/mailman/listinfo/coreboot"
target="_blank">http://</a><a
moz-do-not-send="true"
href="http://www.coreboot.org/mailman/listinfo/coreboot"
target="_blank">www.coreboot.org</a><a
moz-do-not-send="true"
href="http://www.coreboot.org/mailman/listinfo/coreboot"
target="_blank">/mailman/</a><a
moz-do-not-send="true"
href="http://www.coreboot.org/mailman/listinfo/coreboot"
target="_blank">listinfo</a><a
moz-do-not-send="true"
href="http://www.coreboot.org/mailman/listinfo/coreboot"
target="_blank">/coreboot</a><br>
</p>
</blockquote>
<p dir="ltr"><br>
</p>
</blockquote>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>