public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Faccini, Bruno" <bruno.faccini@intel.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Problems building "2.4.0-test9" kernel source on/for IA-64
Date: Wed, 18 Oct 2000 06:35:46 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205589@msgid-missing> (raw)

[-- Attachment #1: Type: text/plain, Size: 2177 bytes --]


Hello,

I am posting this just in case it has not been already reported and/or fixed
thru the latest patch versions (ie somewhere between the base "-test9"
source tree version and the current/latest "2.4.0-test10/pre3").
Trying to build "-test9" full tar-ball on/for an IA-64 SDV, I got the
following problems/errors :
	_ multiple compilation errors for "arch/ia64/kernel/setup.c" source
starting with line #215 and apparently related to "definitions/declarations"
issues when it pointed to a routine ("setup_arch()") body !!
In fact this was due to a bug (typo ??) in "setup_arch()" routine itself,
where an "if{}else" statement contained an unnecessary "}" ("} else" at line
#160 in the original "setup.c" source) finally shortening the routine's body
and causing next routines statement to be parsed as
"definitions/declarations".
The following fix/diff corrected the problem :
-------------------------
$ diff setup.c.bfi setup.c.orig
160,165c160
< /*            } else
< This accolade appear to be a "typo" which mainly cause the upper "if"
statemen
t
< and the routine itself to close/end prematurelly, thus causing compilation
< errors for the rest of the routines statements now left outside !!
< B.Faccini (bruno.faccini@intel.com) */
<               else
---
>               } else         
$
-------------------------

	_ "unsatisfied externals" for "[disable,reenable]_usb()" entry
points, in source file "arch/ia64/kernel/irq_ia64.c". This appear to be
caused by a joint setup/configuration of
"CONFIG_ITANIUM_A1_SPECIFIC"+"CONFIG_USB". Since "[disable,reenable]_usb()"
are no longer part of any "-test9" Kernel source, I was only abble to fix
this by not using "CONFIG_ITANIUM_A1_SPECIFIC" setting since this build was
intended for an A3 stepping system, I  assume it should work ...

I did not have already tested this Kernel build, hope it will run/boot ok,
and I will post any further issue.

Bruno.

> Bruno Faccini - Tech. Mktg. Engr.
> Technical Marketing/Internet Solutions Group (EMEA)
> Intel GmbH, Germany
> Phone (Intel office): +33-(0)146947228
>       Fax: +33-(0)146947068
>       email: bruno.faccini@intel.com
> 
 <<Bruno Faccini (E-mail).vcf>> 

[-- Attachment #2: Bruno Faccini (E-mail).vcf --]
[-- Type: application/octet-stream, Size: 873 bytes --]

BEGIN:VCARD
VERSION:2.1
N:Faccini;Bruno;;;
FN:Bruno Faccini
ORG:Intel;Technical Marketing/Content Group EMEA
TITLE:Tech. Mktg. Engr.
TEL;WORK;VOICE:+33 (0) 146947228
TEL;WORK;VOICE:+33 (0) 155498427
TEL;HOME;VOICE:
TEL;CELL;VOICE:
TEL;WORK;FAX:+33 (0) 146947068
ADR;WORK;ENCODING=QUOTED-PRINTABLE:;Munich, Germany.;Intel Corporation=0D=0ATour Chenonceaux=0D=0A204 Rond Poin=
t Du Pont De Sevres;Boulogne Billancourt;Cedex;92516;France
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Munich, Germany.=0D=0AIntel Corporation=0D=0ATour Chenonceaux=0D=0A204 Rond =
Point Du Pont De Sevres=0D=0ABoulogne Billancourt, Cedex 92516=0D=0AFrance
ADR;HOME:;;20 Rue Du Marechal Joffre;Brie Comte Robert;;77170;France
LABEL;HOME;ENCODING=QUOTED-PRINTABLE:20 Rue Du Marechal Joffre=0D=0ABrie Comte Robert 77170=0D=0AFrance
EMAIL;PREF;INTERNET:bruno.faccini@intel.com
REV:20000527T141533Z
END:VCARD

             reply	other threads:[~2000-10-18  6:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-18  6:35 Faccini, Bruno [this message]
2000-10-18 19:49 ` [Linux-ia64] Problems building "2.4.0-test9" kernel source on/for IA-64 David Mosberger
2000-10-24  6:39 ` [Linux-ia64] Problems building "2.4.0-test9" kernel source on Faccini, Bruno
2000-10-25  7:12 ` Faccini, Bruno

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-105590678205589@msgid-missing \
    --to=bruno.faccini@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