From: Bjorn Helgaas <bjorn_helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Error compiling 2.4.20 for i386
Date: Fri, 17 Jan 2003 21:19:46 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805715@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805709@msgid-missing>
> I was under the mistaken impression that the ia64 patch for 2.4.18 and
> beyond would not break ia32. I am looking for a way to support both ia32 and
> ia64 from a single kernel source. Is there a plan for the ia64 patch to
> support this model?
No, I don't have a plan to support both ia32 and ia64 with the ia64
patch. I just don't have the time, equipment, or knowledge to maintain
the ia32 side of that equation. The ACPI update I mentioned is one
big issue. Another is the PCI BAR sizing problem -- ia64 requires
an approach that is unsafe on i386.
Of course, I do try to reduce the size of the ia64 patch by pushing
things upstream, and if it were ever reduced to zero, or to only
arch/ia64 things, then i386 should Just Work. That's not likely to
happen anytime soon, though.
> However, I'm getting
> this link error now...
>
> net/network.o(.debug_info+0x6f4b26): undefined reference to `L5661'
I don't have a clue on this one. I'd try a clean build from scratch
to make sure everything was built by the same toolchain, with the same
options, etc.
Bjorn
next prev parent reply other threads:[~2003-01-17 21:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 0:42 [Linux-ia64] Error compiling 2.4.20 for i386 Bahnsen, Bruce
2003-01-17 16:05 ` Bjorn Helgaas
2003-01-17 17:51 ` Bahnsen, Bruce
2003-01-17 21:19 ` Bjorn Helgaas [this message]
2003-01-17 22:01 ` Bahnsen, Bruce
2003-01-21 17:39 ` Bjorn Helgaas
2003-01-21 18:52 ` Bahnsen, Bruce
2003-01-21 19:11 ` Bjorn Helgaas
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=marc-linux-ia64-105590709805715@msgid-missing \
--to=bjorn_helgaas@hp.com \
--cc=linux-ia64@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