From: Marcel Holtmann <marcel@holtmann.org>
To: sparclinux@vger.kernel.org
Subject: Re: Compile problem on sparc64
Date: Thu, 25 Mar 2004 23:25:54 +0000 [thread overview]
Message-ID: <1080257154.2283.24.camel@pegasus> (raw)
In-Reply-To: <20040324121914.00fb9bf9.davem@redhat.com>
Hi Dave,
> Marcel, I think you're using gcc-3.5, because gcc-3.3.x does not
> even warn for these things at all, else I'd be seeing this for
> ages.
>
> Can you double check what "gcc --version" gives?
actually it is the default gcc from Debian Sid and it looks like the
3.3.x version.
gcc (GCC) 3.3.3 (Debian 20040321)
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
This is only an Ultra5, so compiling takes some time and for fixing big
endian and 64-bit bugs in the Bluetooth subsystem I made use of ccache.
ccache version 2.3
Copyright Andrew Tridgell 2002
Released under the GNU GPL v2 or later
And this is my only important modification to the kernel source
--- 1.468/Makefile Sun Mar 21 09:00:57 2004
+++ edited/Makefile Sun Mar 21 20:12:07 2004
@@ -160,7 +160,7 @@
else if [ -x /bin/bash ]; then echo /bin/bash; \
else echo sh; fi ; fi)
-HOSTCC = gcc
+HOSTCC = sparc32 gcc
HOSTCXX = g++
HOSTCFLAGS = -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer
HOSTCXXFLAGS = -O2
Regards
Marcel
prev parent reply other threads:[~2004-03-25 23:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 12:15 Compile problem on sparc64 Marcel Holtmann
2004-03-24 20:19 ` David S. Miller
2004-03-24 20:19 ` David S. Miller
2004-03-24 20:32 ` Marcel Holtmann
2004-03-24 20:32 ` Marcel Holtmann
2004-03-24 22:30 ` David S. Miller
2004-03-24 22:30 ` David S. Miller
2004-03-24 22:56 ` Marcel Holtmann
2004-03-24 22:56 ` Marcel Holtmann
2004-03-25 20:06 ` David S. Miller
2004-03-25 23:25 ` Marcel Holtmann [this message]
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=1080257154.2283.24.camel@pegasus \
--to=marcel@holtmann.org \
--cc=sparclinux@vger.kernel.org \
/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.