From: Andrea Arcangeli <andrea@suse.de>
To: Jeff Dike <jdike@karaya.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.7pre8aa1
Date: Fri, 20 Jul 2001 03:37:49 +0200 [thread overview]
Message-ID: <20010720033749.J31850@athlon.random> (raw)
In-Reply-To: <200107192245.f6JMjcR08865@karaya.com>
In-Reply-To: <200107192245.f6JMjcR08865@karaya.com>; from jdike@karaya.com on Thu, Jul 19, 2001 at 06:45:38PM -0400
On Thu, Jul 19, 2001 at 06:45:38PM -0400, Jeff Dike wrote:
> > Only in 2.4.7pre6aa1: 51_uml-ac-to-aa-2.bz2
> > Only in 2.4.7pre8aa1/: 51_uml-ac-to-aa-3.bz2
> > Moved part of it in the tux directory so it can compile
> > without tux (in reality I got errno compilation error
> > but it's low prio and I'll sort it out later, Jeff Dike any
> > hint is welcome ;).
>
> This is the patch I sent to Alan a while back which works around the problem.
>
> rmk suggested a better way which I'll add at some point.
>
> Jeff
>
>
> diff -Naur -X exclude-files ac_cur/arch/um/Makefile ac/arch/um/Makefile
> --- ac_cur/arch/um/Makefile Mon Jul 9 13:05:03 2001
> +++ ac/arch/um/Makefile Mon Jul 9 13:26:21 2001
> @@ -20,6 +20,8 @@
> LINK_PROFILE = $(PROFILE) -Wl,--wrap,__monstartup
> endif
>
> +CFLAGS := $(subst -fno-common,,$(CFLAGS))
> +
> SUBDIRS += $(ARCH_DIR)/fs $(ARCH_DIR)/drivers $(ARCH_DIR)/kernel \
> $(ARCH_DIR)/sys-$(SUBARCH)
works fine thanks! Of course I agree with rmk it would be better not to
disable -fno-common but this is ok for now ;) (after all we would catch
any potential important name collision during the compiles of the other
targets)
Andrea
next prev parent reply other threads:[~2001-07-20 1:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 22:45 2.4.7pre8aa1 Jeff Dike
2001-07-20 1:37 ` Andrea Arcangeli [this message]
2001-07-20 0:42 ` 2.4.7pre8aa1 Jeff Dike
2001-07-23 1:11 ` 2.4.7pre8aa1 Andrea Arcangeli
2001-07-23 3:49 ` 2.4.7pre8aa1 Jeff Dike
-- strict thread matches above, loose matches on Subject: below --
2001-07-19 18:38 2.4.7pre8aa1 Andrea Arcangeli
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=20010720033749.J31850@athlon.random \
--to=andrea@suse.de \
--cc=jdike@karaya.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 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.