All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Daniel Phillips <phillips@arcor.de>
Cc: Jeff Dike <jdike@karaya.com>,
	linux-kernel@vger.kernel.org,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: uml-patch-2.5.62-1
Date: Thu, 27 Feb 2003 10:40:17 +0300	[thread overview]
Message-ID: <20030227104017.A29863@namesys.com> (raw)
In-Reply-To: <20030226225413.ACF29EAF62@mx12.arcor-online.net>

Hello!

On Thu, Feb 27, 2003 at 06:45:27AM +0100, Daniel Phillips wrote:
> > This patch updates UML to 2.5.63...
> Built and booted.  However, without CONFIG_MODULES=y it doesn't build:
> gcc -Wp,-MD,arch/um/sys-i386/.module.o.d -D__KERNEL__ -Iinclude -Wall 
> -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common 
> -U__i386__ -Ui386 -g -D__arch_um__ -DSUBARCH=\"i386\" -D_LARGEFILE64_SOURCE 
> -Iarch/um/include -Derrno=kernel_errno -Dsigprocmask=kernel_sigprocmask 
> -I/m/src/uml.2.5.63/arch/um/kernel/tt/include 
> -I/m/src/uml.2.5.63/arch/um/kernel/skas/include -nostdinc -iwithprefix 
> include    -DKBUILD_BASENAME=module -DKBUILD_MODNAME=module -c -o 
> arch/um/sys-i386/module.o arch/um/sys-i386/module.c
> arch/um/sys-i386/module.c: In function `apply_relocate':
> arch/um/sys-i386/module.c:89: dereferencing pointer to incomplete type
> arch/um/sys-i386/module.c: In function `apply_relocate_add':
> arch/um/sys-i386/module.c:103: dereferencing pointer to incomplete type
> make[1]: *** [arch/um/sys-i386/module.o] Error 1
> make: *** [arch/um/sys-i386] Error 2
> Native 2.5.63 (i386) is ok with or without CONFIG_MODULES=y.

Patch below (that Jeff have not picked up yet) fixes that.

Bye,
    Oleg

# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
#	           ChangeSet	1.949   -> 1.950  
#	arch/um/sys-i386/Makefile	1.15    -> 1.16   
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 03/02/13	green@angband.namesys.com	1.950
# Only build module.c if we have modules support selected
# --------------------------------------------
#
diff -Nru a/arch/um/sys-i386/Makefile b/arch/um/sys-i386/Makefile
--- a/arch/um/sys-i386/Makefile	Thu Feb 27 10:38:20 2003
+++ b/arch/um/sys-i386/Makefile	Thu Feb 27 10:38:20 2003
@@ -1,7 +1,8 @@
-obj-y = bugs.o checksum.o extable.o fault.o ksyms.o ldt.o module.o \
+obj-y = bugs.o checksum.o extable.o fault.o ksyms.o ldt.o \
 	ptrace.o ptrace_user.o semaphore.o sigcontext.o syscalls.o sysrq.o
 
 obj-$(CONFIG_HIGHMEM) += highmem.o
+obj-$(CONFIG_MODULES) += module.o
 
 USER_OBJS := bugs.o ptrace_user.o sigcontext.o fault.o
 USER_OBJS := $(foreach file,$(USER_OBJS),$(obj)/$(file))

  reply	other threads:[~2003-02-27  7:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-26 19:05 uml-patch-2.5.62-1 Jeff Dike
2003-02-27  5:45 ` uml-patch-2.5.62-1 Daniel Phillips
2003-02-27  7:40   ` Oleg Drokin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-19 20:08 uml-patch-2.5.62-1 Jeff Dike
2003-02-20  8:08 ` uml-patch-2.5.62-1 Oleg Drokin

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=20030227104017.A29863@namesys.com \
    --to=green@namesys.com \
    --cc=jdike@karaya.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@arcor.de \
    --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 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.