public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Fix for a build ?
Date: Mon, 03 May 2010 22:34:20 +0200	[thread overview]
Message-ID: <20100503203420.0B09AB076D3@gemini.denx.de> (raw)
In-Reply-To: <h2y3e45db431005030651sacba80cz14740e8d79c4d178@mail.gmail.com>

Dear Sylvain Lamontagne,

In message <h2y3e45db431005030651sacba80cz14740e8d79c4d178@mail.gmail.com> you wrote:
>
> We have recently installed an automated build system in our company
> and occasionally there is a problem when U-Boot is built.
> One build will work the other will not without any changes to the sources
> (it is not: 1 work, then other fail... it is more like 3 may work the 4 will
> not but the 5 will). Our build system guy says that the problem is probably
> a race condition with a dependency in the U-Boot make.
...
> *[09:23:58]:* *make: ***
> [/home/slamon/server/TeamCity/buildAgent/work/19b40828dc62d35d/build/u-boot-1.3.4/cpu/mpc5xxx/start.o]
-----------------------------------------------------------------------^^^^^^^^^^^^

Ah, U-Boot release 1.3.4.

That's nearly two years old, which means it's ancient.

Yes, there may be race conditions during building, especially on SMP
machines.

> Is there a way to fix this ? It could be putting some "sleep" somewhere...

Please upgrade to a recent version.

> * Also, upgrading U-Boot is not an option... since we don't have the need
> nor resources to port a new version of U-Boot to this product. So please
> don't suggest that.

Heh. So what do you want? A solution, but no changes?

We will not fix for free any bugs in old versions of the code. You
have the following options:

- stick with the obsolete code you have and stop complaining
- update to the current release and ask again if there should still be
  problems (which I doubt)
- fix the problems yourself
- hire somebody else to fix the problems (and most probably the most
  efficient way to fix the problem will be an update to the current
  release)

For your next project you can try and learn a lesson from this issue:
the amount of effort saved by not pushing your port upstream into
mainline is often smaller than the added maintenance cost for an
out-of-tree port.

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 at denx.de
You never have the time to do things right,  but you will always have
the time to do them twice.

  parent reply	other threads:[~2010-05-03 20:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-03 13:51 [U-Boot] Fix for a build ? Sylvain Lamontagne
2010-05-03 18:52 ` Mike Frysinger
2010-05-03 20:14   ` Sylvain Lamontagne
2010-05-03 20:37     ` Wolfgang Denk
2010-05-03 20:34 ` Wolfgang Denk [this message]
2010-05-03 21:44   ` Mike Frysinger
2010-05-03 22:02   ` Sylvain Lamontagne
2010-05-03 23:30     ` Mike Frysinger
2010-05-04  7:56     ` Wolfgang Denk
2010-05-04 14:39       ` Sylvain Lamontagne
2010-05-04 18:44         ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2010-05-05 10:32 Igor Luri
2010-05-05 15:55 ` Sylvain Lamontagne

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100503203420.0B09AB076D3@gemini.denx.de \
    --to=wd@denx.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox