<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 23.04.2009 1:35 Uhr, Carl-Daniel Hailfinger wrote:
<blockquote cite="mid:49EFA9DB.6000805@gmx.net" type="cite">
<pre wrap="">On 23.04.2009 01:28, Stefan Reinauer wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 23.04.2009 1:09 Uhr, Joseph Smith wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Wed, 22 Apr 2009 13:50:54 -0700, ron minnich <a class="moz-txt-link-rfc2396E" href="mailto:rminnich@gmail.com"><rminnich@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Tue, Apr 21, 2009 at 4:41 AM, Joseph Smith <a class="moz-txt-link-rfc2396E" href="mailto:joe@settoplinux.org"><joe@settoplinux.org></a>
</pre>
</blockquote>
<pre wrap="">wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">This really sounds like an unitialized variable or a bad pointer.
</pre>
</blockquote>
<pre wrap="">Wouldn't gcc catch these and error when building?
</pre>
</blockquote>
<pre wrap="">not always. that's what sparse can be useful for.
</pre>
</blockquote>
<pre wrap="">Why can't I just send the build output to a text file and then look through
it for all the warnings/errors?
$ make > buildlog.txt
</pre>
</blockquote>
<pre wrap="">You can..
btw.. qa.coreboot.org holds logs of each revision too (the last few
200-1000 depending when I clean up)
<a class="moz-txt-link-freetext" href="http://qa.coreboot.org/log_buildbrd.php?revision=4187&device=ip1000&vendor=thomson&num=2">http://qa.coreboot.org/log_buildbrd.php?revision=4187&device=ip1000&vendor=thomson&num=2</a>
But please note that gcc does not catch all the tricky mistakes we make.
</pre>
</blockquote>
<pre wrap=""><!---->
Or you run
cd util/abuild; abuild -t thomson/ip1000
and look at coreboot-builds/thomson_ip1000/make.log
</pre>
</blockquote>
or <br>
<br>
util/abuild/abuild -t thomson/ip1000 $PWD<br>
<br>
to build on the top level.<br>
<br>
You can also specify a payload directory with -p<br>
<br>
mkdir payloads<br>
cp /somewhere/filo.elf payloads<br>
then add a file payloads/payload.sh which prints the name of the
payload to use (and takes the mainboard as a parameter)<br>
such as<br>
echo "`dirname $0`/build/filo.elf"<br>
<br>
then you can build a fully working image with payload by specifying:<br>
<br>
util/abuild/abuild -t thomson/ip1000 -p ./payloads $PWD <br>
<br>
Specify -c max or -c 2 if you have an SMP system, to speed compilation
up.<br>
<br>
Stefan<br>
<br>
<pre class="moz-signature" cols="72">--
coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br.
Tel.: +49 761 7668825 • Fax: +49 761 7664613
Email: <a class="moz-txt-link-abbreviated" href="mailto:info@coresystems.de">info@coresystems.de</a> • <a class="moz-txt-link-freetext" href="http://www.coresystems.de/">http://www.coresystems.de/</a>
Registergericht: Amtsgericht Freiburg • HRB 7656
Geschäftsführer: Stefan Reinauer • Ust-IdNr.: DE245674866
</pre>
</body>
</html>