public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Bahnsen, Bruce" <bruce.bahnsen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] Error compiling 2.4.20 for i386
Date: Fri, 17 Jan 2003 17:51:32 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805714@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805709@msgid-missing>

Thanks Bjorn

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?

The smp_threads_ready error is just gcc-3 being more picky about matching
volatile qualifiers. I can get ia64 to compile now. However, I'm getting
this link error now...

net/network.o(.debug_info+0x6f4b26): undefined reference to `L5661'

Bruce


-----Original Message-----
From: Bjorn Helgaas [mailto:bjorn_helgaas@hp.com]
Sent: Friday, January 17, 2003 8:06 AM
To: Bahnsen, Bruce; 'linux-ia64@linuxia64.org'
Subject: Re: [Linux-ia64] Error compiling 2.4.20 for i386


On Thursday 16 January 2003 5:42 pm, Bahnsen, Bruce wrote:
> I applied the ia64 patch to the 2.4.20 kernel (all from kernel.org). If I
> try to compile i386 using the default config, I get the following compile
> error:

If you want an i386 kernel, there is no reason to use the ia64 patch.

I'll look at this for the 2.4.21 patch, but in general, I do not pay
any attention to the i386 kernel when producing the ia64 patch.

2.4.20 has very old ACPI bits in it, so the ia64 patch contains a
large ACPI update.  The ia64-specific ACPI bits match, of course,
but I don't bother to update the i386-specific ACPI bits.  So it's
likely that this is a result of that mismatch.

> setup.c: In function `parse_cmdline_early':
> setup.c:792: `enable_acpi_smp_table' undeclared (first use in this
function)
 
> I am getting errors compiling ia64 as well, such as:
> ...
> smpboot.c:92: conflicting types for `smp_threads_ready'

Hmm...  Obviously I don't see this error, but I'm using an old (2.96)
gcc.  Maybe newer ones are pickier.  In any case, I've removed
the "volatile" declaration of smp_threads_ready in smpboot.c, so
this won't be an issue for 2.4.21.

Bjorn


  parent reply	other threads:[~2003-01-17 17:51 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 [this message]
2003-01-17 21:19 ` Bjorn Helgaas
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-105590709805714@msgid-missing \
    --to=bruce.bahnsen@intel.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