From: Shinya Kuribayashi <skuribay@ruby.dti.ne.jp>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] ColdFire: Get information from the correct GCC
Date: Tue, 06 May 2008 18:32:47 +0900 [thread overview]
Message-ID: <482025BF.3060808@ruby.dti.ne.jp> (raw)
In-Reply-To: <481DE5AE.8010801@freescale.com>
Hi Kurt,
Kurt Mahan wrote:
> Shinya Kuribayashi wrote:
>> Liew Tsi Chung wrote:
>>> I am using Fedora 8. Also, the problem can be generated if using
>>> Fedora 4 and 5 except 3. If you have a Fedora 4 and above, please try
>>> it. I bet you will run into the same problem as Kurt and I did.
> I ran into the problem with OpenSuSE 10.2
>
>> I can't try Fedora[458] in the immediate future, sorry. But at last I'm
>> convinced that it seems GNU make on those distros behaves in different
>> ways; differed expansion of CFLAGS is suspicious, but I'm not going to
>> dig into further.
> The version of make that I'm running is:
>
> ~> make --version
> GNU Make 3.81
me, too. But Debian's seems to have some extra bug fixes. As for Debian
specific bugfixes, see [1].
--------------------------------
Package: make
State: installed
Automatically installed: no
Version: 3.81-4
Priority: optional
Section: devel
Maintainer: Manoj Srivastava <srivasta@debian.org>
Uncompressed Size: 991k
Depends: libc6 (>= 2.7-1)
Suggests: make-doc
Description: The GNU version of the "make" utility.
GNU Make is a program that determines which pieces of a large program need to
be recompiled and issues the commands to recompile them, when necessary. More
information about GNU Make can be found in the `make' Info page. The upstream
sources for this package are available at the location
ftp://ftp.gnu.org/gnu/make/. The documentation for this package does not meet
the Debian Free Software Guidelines, and has been removed from this package.
--------------------------------
I reverted Debian specific patches and repackaged GNU make; this will be
pure GNU make 3.81 release. Next, I reverted Wolfgang's config.mk patch
and tried M54455EVB_config again. But this *still* works fine.
Therefore I believe Debian's patches have no effect on our issue.
At this moment, I'm interested in VPATH (or vpath) on those systems when
finally generating PLATFORM_LIBS. Passing -print-data-base to make will
help in that case.
Otherwise, Fedora or OpenSuSE applies its specific patches on make...
But anyway, it seems the problem is already verified. I'm not going to
dig into further :-)
thanks,
Shinya
[1] http://packages.debian.org/changelogs/pool/main/m/make-dfsg/make-dfsg_3.81-4/changelog
next prev parent reply other threads:[~2008-05-06 9:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 17:10 [U-Boot-Users] [PATCH] ColdFire: Get information from the correct GCC Tsi-Chung Liew
2008-04-30 20:36 ` Wolfgang Denk
2008-05-01 3:42 ` Shinya Kuribayashi
2008-05-01 21:34 ` Liew Tsi Chung
2008-05-01 22:05 ` Wolfgang Denk
2008-05-02 22:03 ` Liew Tsi Chung
2008-05-02 22:57 ` Wolfgang Denk
2008-05-03 3:25 ` Shinya Kuribayashi
2008-05-04 5:37 ` Liew Tsi Chung
2008-05-04 5:49 ` Shinya Kuribayashi
2008-05-04 8:37 ` Liew Tsi Chung
2008-05-04 9:56 ` Shinya Kuribayashi
2008-05-04 16:34 ` Kurt Mahan
2008-05-04 18:44 ` Wolfgang Denk
2008-05-06 9:32 ` Shinya Kuribayashi [this message]
2008-05-05 14:14 ` Liew Tsi Chung
2008-05-05 22:02 ` Wolfgang Denk
2008-05-06 6:41 ` Liew Tsi Chung
2008-05-05 15:43 ` Liew Tsi Chung
2008-05-04 15:40 ` Wolfgang Denk
2008-05-03 21:11 ` 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=482025BF.3060808@ruby.dti.ne.jp \
--to=skuribay@ruby.dti.ne.jp \
--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