public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gonzalo Aguilar <gad@reymad.com>
To: linux-kernel@vger.kernel.org
Subject: sched.h problem in 2.4.x and new gcc compilers
Date: Wed, 27 Jun 2001 23:38:38 +0200	[thread overview]
Message-ID: <3B3A525E.B321BC5@reymad.com> (raw)

Hello, there is a little problem with some headers and
new glibs and compilers. Kernel fails to compile and worst
is the extern declaration in sched.h

Don't if this is a gcc or glib problem (surely gcc) but doesn't
works...

The patch is only redeclaring xtime in extern:

*************************** cut here ******************************
--- include/linux/sched.h	Wed Jun 27 23:19:04 2001
+++ include/linux/sched.h~	Thu Jun 21 12:36:26 2001
@@ -537,7 +537,7 @@
 extern unsigned long volatile jiffies;
 extern unsigned long itimer_ticks;
 extern unsigned long itimer_next;
-extern volatile struct timeval xtime __attribute__ ((aligned (16)));
+extern struct timeval xtime;
 extern void do_timer(struct pt_regs *);
 
 extern unsigned int * prof_buffer;
***************************** cut here ******************************

I made it with the copy that joe editor does, you know the change is:

-extern volatile struct timeval xtime __attribute__ ((aligned (16)));
+extern struct timeval xtime;

There are other problems with multiline string literals all over the
code
but this is only a warning... One is this...

/mnt/hd2/src/linux-2.4.5/include/asm/checksum.h:72:30: warning:
multi-line string literals are deprecated

Hope it helps. It's a ridiculous patch but now it's fixed.

Thanks
-- 
Gonzalo Aguilar. Madrid, España (Spain) |
Reymad Studios | gad@reymad.com		|
Privado        | eshero@airtel.net	|
----------------------------------------+

                 reply	other threads:[~2001-06-27 21:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3B3A525E.B321BC5@reymad.com \
    --to=gad@reymad.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox