linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: itamar <itamar@ispbrasil.com.br>
Subject: Re: [uml-devel] 2.4.27 + uml-2.4.27-bs2-pre10 compile error.
Date: Sun, 10 Apr 2005 12:55:02 +0200	[thread overview]
Message-ID: <200504101255.04117.blaisorblade@yahoo.it> (raw)
In-Reply-To: <000501c53c97$5a00b050$0201a8c0@lualele>

On Saturday 09 April 2005 02:01, itamar wrote:
> I am trying to compile, but I am getting this error.
Try the patch on a more recent kernel. As I said (and as I'll think unless 
proved wrong), vanilla 2.4.27 cannot compile with GCC 3.4 (which is what you 
use). Currently I use a GCC 3.3. And I don't have a >2.4.27 kernel to try the 
patch on.

> make all_targets
> make[2]: Entering directory `/usr/src/linux-2.4.27/kernel'
> gcc -D__KERNEL__ -I/usr/src/linux-2.4.27/include -Wall -Wstrict-prototypes
> -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer
> -U__i386__ -Ui386 -DUM_FASTCALL  -D__arch_um__ -DSUBARCH="i386"
> -D_LARGEFILE64_SOURCE -I/usr/src/linux-2.4.27/arch/um/include
> -Derrno=kernel_errno -I/usr/src/linux-2.4.27/arch/um/kernel/tt/include
> -I/usr/src/linux-2.4.27/arch/um/kernel/skas/include -fno-unit-at-a-time  
> -nostdinc -iwithprefix
> include -DKBUILD_BASENAME=sched  -fno-omit-frame-pointer -c -o sched.o
> sched.c
> sched.c:213: error: conflicting types for 'reschedule_idle'
> sched.c:210: error: previous declaration of 'reschedule_idle' was here
> sched.c:213: error: conflicting types for 'reschedule_idle'
> sched.c:210: error: previous declaration of 'reschedule_idle' was here
> sched.c:371: error: conflicting types for 'wake_up_process'
> /usr/src/linux-2.4.27/include/linux/sched.h:603: error: previous
> declaration of 'wake_up_process' was here
> sched.c:371: error: conflicting types for 'wake_up_process'
> /usr/src/linux-2.4.27/include/linux/sched.h:603: error: previous
> declaration of 'wake_up_process' was here
> sched.c:409: error: conflicting types for 'schedule_timeout'
> /usr/src/linux-2.4.27/include/linux/sched.h:148: error: previous
> declaration of 'schedule_timeout' was here
> sched.c:409: error: conflicting types for 'schedule_timeout'
> /usr/src/linux-2.4.27/include/linux/sched.h:148: error: previous
> declaration of 'schedule_timeout' was here
> sched.c:739: error: conflicting types for '__wake_up'
> /usr/src/linux-2.4.27/include/linux/sched.h:595: error: previous
> declaration of '__wake_up' was here
> sched.c:739: error: conflicting types for '__wake_up'
> /usr/src/linux-2.4.27/include/linux/sched.h:595: error: previous
> declaration of '__wake_up' was here
> sched.c:749: error: conflicting types for '__wake_up_sync'
> /usr/src/linux-2.4.27/include/linux/sched.h:596: error: previous
> declaration of '__wake_up_sync' was here
> sched.c:749: error: conflicting types for '__wake_up_sync'
> /usr/src/linux-2.4.27/include/linux/sched.h:596: error: previous
> declaration of '__wake_up_sync' was here
> sched.c:759: error: conflicting types for 'complete'
> /usr/src/linux-2.4.27/include/linux/completion.h:31: error: previous
> declaration of 'complete' was here
> sched.c:759: error: conflicting types for 'complete'
> /usr/src/linux-2.4.27/include/linux/completion.h:31: error: previous
> declaration of 'complete' was here
> sched.c:769: error: conflicting types for 'wait_for_completion'
> /usr/src/linux-2.4.27/include/linux/completion.h:30: error: previous
> declaration of 'wait_for_completion' was here
> sched.c:769: error: conflicting types for 'wait_for_completion'
> /usr/src/linux-2.4.27/include/linux/completion.h:30: error: previous
> declaration of 'wait_for_completion' was here
> sched.c:804: error: conflicting types for 'interruptible_sleep_on'
> /usr/src/linux-2.4.27/include/linux/sched.h:600: error: previous
> declaration of 'interruptible_sleep_on' was here
> sched.c:804: error: conflicting types for 'interruptible_sleep_on'
> /usr/src/linux-2.4.27/include/linux/sched.h:600: error: previous
> declaration of 'interruptible_sleep_on' was here
> sched.c:815: error: conflicting types for 'interruptible_sleep_on_timeout'
> /usr/src/linux-2.4.27/include/linux/sched.h:601: error: previous
> declaration of 'interruptible_sleep_on_timeout' was here
> sched.c:815: error: conflicting types for 'interruptible_sleep_on_timeout'
> /usr/src/linux-2.4.27/include/linux/sched.h:601: error: previous
> declaration of 'interruptible_sleep_on_timeout' was here
> sched.c:828: error: conflicting types for 'sleep_on'
> /usr/src/linux-2.4.27/include/linux/sched.h:597: error: previous
> declaration of 'sleep_on' was here
> sched.c:828: error: conflicting types for 'sleep_on'
> /usr/src/linux-2.4.27/include/linux/sched.h:597: error: previous
> declaration of 'sleep_on' was here
> sched.c:839: error: conflicting types for 'sleep_on_timeout'
> /usr/src/linux-2.4.27/include/linux/sched.h:598: error: previous
> declaration of 'sleep_on_timeout' was here
> sched.c:839: error: conflicting types for 'sleep_on_timeout'
> /usr/src/linux-2.4.27/include/linux/sched.h:598: error: previous
> declaration of 'sleep_on_timeout' was here
> sched.c:210: warning: 'reschedule_idle' declared `static' but never defined
> make[2]: *** [sched.o] Error 1
> make[2]: Leaving directory `/usr/src/linux-2.4.27/kernel'
> make[1]: *** [first_rule] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.4.27/kernel'
> make: *** [_dir_kernel] Error 2
>
> Itamar Reis Peixoto
> +55 (34) 3238 3845
> e-mail : itamar@ispbrasil.com.br
> http://www.ispbrasil.com.br
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> User-mode-linux-devel mailing list
> User-mode-linux-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

      reply	other threads:[~2005-04-10 10:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-09  0:01 [uml-devel] 2.4.27 + uml-2.4.27-bs2-pre10 compile error itamar
2005-04-10 10:55 ` Blaisorblade [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=200504101255.04117.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=itamar@ispbrasil.com.br \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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