archive mirror
 help / color / mirror / Atom feed
From: Mariusz Mazur <>
To: Andrew Walrond <>
Subject: Re: [ANNOUNCE] linux-libc-headers
Date: Wed, 12 Jan 2005 12:11:23 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On środa 12 styczeń 2005 11:49, Andrew Walrond wrote:
> Upgrading from to causes a mysql build failure on x86:
> gcc -DDEFAULT_CHARSET_HOME=\"/pkg/mysql.1\"
> -DDATADIR=\"/pkg/mysql.1/state\" -DSHAREDIR=\"/pkg/mysql.1/share/mysql\"
> -DDONT_USE_RAID -DMYSQL_CLIENT -fPIC -I. -I. -I.. -I../include -O3
> -DDBUG_OFF -march=i686 -O2 -MT password.lo -MD -MP -MF .deps/password.Tpo
> -c password.c  -fPIC -DPIC -o .libs/password.o In file included from
> ../include/my_global.h:291,
>                  from password.c:62:
> /usr/include/asm/atomic.h: In function `atomic_add_return':
> /usr/include/asm/atomic.h:189: error: `boot_cpu_data' undeclared (first use
> in this function)
> It builds fine on x86_64 though. I don't know where the fault lies here;
> mysql, libc-headers or linux-2.6.10, so this is just a FYI.

Looks like you've linked your kernel's config.h to llh and that causes the 
problem. You shouldn't do that unless you have a specific reason to, 
otherwise you might end up with problems I'm unable to test for (I can't 
check every possible combination of kernel CONFIG_'s).

I'll state that more clearly in the docs.

In the year eighty five ten
God is gonna shake his mighty head
He'll either say,
"I'm pleased where man has been"
Or tear it down, and start again

  reply	other threads:[~2005-01-12 11:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-08 15:13 [ANNOUNCE] linux-libc-headers Mariusz Mazur
2005-01-10 15:16 ` Randy.Dunlap
2005-01-12 10:49 ` Andrew Walrond
2005-01-12 11:11   ` Mariusz Mazur [this message]
2005-01-12 12:04     ` Andrew Walrond
2005-01-13  8:13     ` Andrew Walrond
2005-01-13  9:42       ` Mariusz Mazur
2005-01-13 11:00         ` Andrew Walrond
2005-01-13 11:46           ` Rahul Karnik
2005-01-13 11:51             ` Jakub Jelinek
2005-01-13 16:14               ` Rahul Karnik
2005-01-13 16:29               ` Mariusz Mazur
2005-01-13 12:18             ` Andrew Walrond

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).