From: Dan Kegel <dank@kegel.com>
To: Christian <evilninja@gmx.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: gcc4 compile fixes
Date: Mon, 04 Apr 2005 07:10:12 -0700 [thread overview]
Message-ID: <42514AC4.8030602@kegel.com> (raw)
In-Reply-To: <425147C4.10906@gmx.net>
Christian wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> replying to myself:
>
> Christian wrote:
>
>>now it [1] fails with:
>>
>>In file included from arch/ppc/kernel/time.c:68:
>>include/asm/time.h:61: warning: type qualifiers ignored on function return
>>type
>
> [...]
>
> ..and there were other error messages too. not knowing a *bit* of C, i was
> able to do minor alterations which i deduced from gcc's error messages.
> now compiling for ppc604 (PReP) with gcc4 succeeds.
Thanks for the report and the patch.
Parts of that patch look like ones I've already collected at:
http://www.kegel.com/crosstool/crosstool-0.30/patches/linux-2.6.11.3/
Here are the patches I have so far:
kaz-types.patch
linux-2.6.11-allow-gcc-4.0-asm-i386.patch
linux-2.6.11-allow-gcc-4.0-asm-m68k.patch
linux-2.6.11-allow-gcc-4.0-asm-ppc64.patch
linux-2.6.11-allow-gcc-4.0-asm-x86_64.patch
linux-2.6.11-allow-gcc-4.0-i2c.patch
linux-2.6.11-allow-gcc-4.0-ppc-mikpe.patch
In particular,
http://www.kegel.com/crosstool/crosstool-0.30/patches/linux-2.6.11.3/linux-2.6.11-allow-gcc-4.0-ppc-mikpe.patch
covers some of what you found.
Maybe if I apply your first patch, I'll make it all the way through.
Thanks,
Dan
--
Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html
prev parent reply other threads:[~2005-04-04 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-19 0:55 gcc4 compile fixes Dan Kegel
2005-04-04 1:51 ` Christian
2005-04-04 13:57 ` Christian
2005-04-04 14:10 ` Dan Kegel [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=42514AC4.8030602@kegel.com \
--to=dank@kegel.com \
--cc=evilninja@gmx.net \
--cc=linuxppc-dev@ozlabs.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.