From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot build issue
Date: Thu, 27 Jun 2013 00:50:58 +0200 [thread overview]
Message-ID: <201306270050.58470.marex@denx.de> (raw)
In-Reply-To: <20130626220617.056EF380DCD@gemini.denx.de>
Dear Wolfgang Denk,
> Dear Marek,
>
> In message <201306261655.18605.marek.vasut@gmail.com> you wrote:
> > remember when the Jenkins was failing on random targets and the log
> > always contained this message, where it stated it can't compile some
> > object file due to missing dependency, whose path was "trimmed" ?
>
> ...
>
> > btw. tool versions:
> >
> > marex at bfu:~/U-Boot/u-boot-imx$ arm-linux-gnueabi-gcc --version
> > arm-linux-gnueabi-gcc (Debian 4.8.0-7) 4.8.0
> > [...]
> > marex at bfu:~/U-Boot/u-boot-imx$ arm-linux-gnueabi-ld --version
> > GNU ld (GNU Binutils for Debian) 2.23.52.20130612
>
> Does it happen with ELDK, too?
Yes, because Jenkins uses ELDK and no other toolchain to build-test U-Boot .
> > marex at bfu:~/U-Boot/u-boot-imx$ make --version
> > GNU Make 3.81
>
> Does it hapen with a recent version of make, too? [That would be the
> first thing to check, me thinks].
It happens with make 3.82 , yes .
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-06-26 22:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 14:55 [U-Boot] U-Boot build issue Marek Vasut
2013-06-26 22:06 ` Wolfgang Denk
2013-06-26 22:50 ` Marek Vasut [this message]
2013-06-27 11:21 ` Marek Vasut
2013-06-27 13:03 ` Tom Rini
2013-06-27 13:23 ` Marek Vasut
[not found] <BFD690A35E15C044967F875DD3A1A3721CD4C003@POCITMSEXMB04.LntUniverse.com>
[not found] ` <20141120113927.B1B20380316@gemini.denx.de>
[not found] ` <BFD690A35E15C044967F875DD3A1A3721CD4C725@POCITMSEXMB04.LntUniverse.com>
2014-11-22 5:39 ` [U-Boot] u-boot " Lalitkumar Choudhary
2014-11-22 23:04 ` Wolfgang Denk
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=201306270050.58470.marex@denx.de \
--to=marex@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.