From: Joel Soete <joel.soete@freebel.net>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: parisc-linux@parisc-linux.org
Subject: gcc-3.2 Ok gcc-3.1.1 Ko (was Re: [parisc-linux] gcc-3.2 bootstrap?)
Date: Wed, 17 Jul 2002 19:09:54 +0200 (CEST) [thread overview]
Message-ID: <1026925794.3d35a4e296ccf@webmail.tiscalinet.be> (raw)
In-Reply-To: <200207161812.g6GICDIp023677@hiauly1.hia.nrc.ca>
Quoting John David Anglin <dave@hiauly1.hia.nrc.ca>:
> > > Your problem appears to be with arch/parisc/kernel/parisc_ksyms.c.
> > > It imports the symbol.
> > >
> >
> > Simply comment it out will broken to compile with gcc-3.0.x, I
> suppose?
>
> I suspect that you can just delete
>
> extern void $$mulU(void);
>
> and
>
> #ifndef __LP64__
> EXPORT_SYMBOL_NOVERS($$mulU);
> #endif
>
> I didn't see any assembly usage of this function in linux and I don't
> believe gcc uses it (even 3.0.x), so probably the lines can just be
> deleted.
>
To summarise:
This clean should be applied without problem (test with gcc-3.2 and gcc-3.0.4)
This allow me to produce an operational kernel with gcc-3.2 (bootstrap an x);
telnet, ftp and ssh connection OK
But with gcc-3.1.1 still crashing at the first remote connection?
I will try a more recent CVS update.
Joel
-------------------------------------------------
This mail sent through Tiscali Webmail (http://webmail.tiscali.be)
next parent reply other threads:[~2002-07-17 17:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200207161812.g6GICDIp023677@hiauly1.hia.nrc.ca>
2002-07-17 17:09 ` Joel Soete [this message]
2002-07-17 17:13 ` gcc-3.2 Ok gcc-3.1.1 Ko (was Re: [parisc-linux] gcc-3.2 bootstrap?) John David Anglin
2002-07-17 17:30 ` joel.soete
2002-07-17 17:32 ` Matthew Wilcox
2002-07-17 17:44 ` joel.soete
2002-07-17 18:10 ` Matthew Wilcox
2002-07-18 6:15 ` joel.soete
2002-07-18 12:06 ` joel.soete
2002-07-18 17:43 ` joel.soete
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=1026925794.3d35a4e296ccf@webmail.tiscalinet.be \
--to=joel.soete@freebel.net \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@parisc-linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox