All of lore.kernel.org
 help / color / mirror / Atom feed
From: info <css@sniip.ru>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk,
	Arnaldo Carvalho de Melo <acme@conectiva.com.br>
Subject: Repeating 2.4.3 compile error with ipx makefile patch
Date: Thu, 12 Apr 2001 12:49:20 +0400	[thread overview]
Message-ID: <01041212543100.09115@sh.lc> (raw)
In-Reply-To: <4AB83BD5FB4@vcnet.vc.cvut.cz> <20010411180235.A29195@vana.vc.cvut.cz>
In-Reply-To: <20010411180235.A29195@vana.vc.cvut.cz>

óÒÄ, 11 áÐÒ 2001 × ÓÏÏÂÝÅÎÉÉ ÎÁ ÔÅÍÕ "Re: 2.4.3 compile error No 3" ÷Ù ÎÁÐÉÓÁÌÉ:
> diff -urdN linux/net/ipx/Makefile linux/net/ipx/Makefile
................

Petr, first of all I save text of patch you sent me to file
"ipx-makefile.patch" in /usr/src and try to patch.
Result:
-------------------------------------------------------------------
[root@sh src]# patch -p0 < ipx-makefile.patch
patching file linux/net/ipx/Makefile
patch: **** malformed patch at line 6: export-objs = af_ipx.o af_spx.o
        
[root@sh src]#   
--------------------------------------------

So I  try to patched linux/net/ipx/Makefile manually with you text.
Resulting Makefile:

_______________________________________________________
#
# Makefile for the Linux IPX layer.
#
# Note! Dependencies are done automagically by 'make dep', which also
# removes any old dependencies. DON'T put your own dependencies here
# unless it's something special (ie not a .c file).
#
# Note 2! The CFLAGS definition is now in the main makefile...

# We only get in/to here if CONFIG_IPX = 'y' or 'm'

O_TARGET := ipx.o

export-objs = af_ipx.o af_spx.o

obj-y	:= af_ipx.o sysctl_net_ipx.o

ifeq ($(CONFIG_IPX),m)
  obj-m += $(O_TARGET)
endif

obj-$(CONFIG_SPX) += af_spx.o

include $(TOPDIR)/Rules.make

tar:
		tar -cvf /dev/f1 .
________________________________
Then try to compile
Result - the same error.

_______________________________________________________________________
make[1]: Leaving directory `/usr/src/linux/arch/i386/lib'
ld -m elf_i386 -T /usr/src/linux/arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o init/version.o \
        --start-group \
        arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o \
        drivers/block/block.o drivers/char/char.o drivers/misc/misc.o drivers/net/net.o drivers/media/media.o  drivers/parport/driver.o drivers/ide/idedriver.o
drivers/cdrom/driver.o drivers/pci/driver.o drivers/video/video.o \
        net/network.o \
        /usr/src/linux/arch/i386/lib/lib.a /usr/src/linux/lib/lib.a /usr/src/linux/arch/i386/lib/lib.a \
        --end-group \
        -o vmlinux
net/network.o(.data+0x2c84): undefined reference to `sysctl_ipx_pprop_broadcasting' 
_________________________________________________

  parent reply	other threads:[~2001-04-12  9:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4AB83BD5FB4@vcnet.vc.cvut.cz>
2001-04-11 16:02 ` 2.4.3 compile error No 3 Petr Vandrovec
2001-04-11 13:29   ` Arnaldo Carvalho de Melo
2001-04-11 16:15   ` info
2001-04-12  8:49   ` info [this message]
2001-04-12 14:52 Repeating 2.4.3 compile error with ipx makefile patch Petr Vandrovec

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=01041212543100.09115@sh.lc \
    --to=css@sniip.ru \
    --cc=acme@conectiva.com.br \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vandrove@vc.cvut.cz \
    /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.