From: Uros Prestor <uros@turbolinux.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Undefined symbols
Date: Wed, 10 Jan 2001 19:34:52 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005016@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205911@msgid-missing>
Keith Owens wrote:
> On Tue, 09 Jan 2001 18:03:20 -0800,
> Uros Prestor <uros@turbolinux.com> wrote:
> > [root@borg linux]# egrep ' (jiffies|printk)' /proc/ksyms
> > e000000000b44c58 jiffies_R__ver_jiffies
> > e000000000a869f0 printk_R__ver_printk
>
> http://www.tux.org/lkml/#s8-8
>
> If you still get problems after that process, let me know.
It looks like `make dep' is broken if you're doing a parallel build.
For example, if I do
# make mrproper
# cp ../.config .
# make oldconfig
# make dep
# find . -name "*.ver" | xargs fgrep jiffies
./include/linux/modules/ksyms.ver:#define
__ver_sysctl_jiffies smp_1d9a67c4
./include/linux/modules/ksyms.ver:#define
sysctl_jiffies _set_ver(sysctl_jiffies)
./include/linux/modules/ksyms.ver:#define
__ver_proc_dointvec_jiffies smp_f9e749ca
./include/linux/modules/ksyms.ver:#define
proc_dointvec_jiffies _set_ver(proc_dointvec_jiffies)
./include/linux/modules/ksyms.ver:#define
__ver_proc_doulongvec_ms_jiffies_minmax smp_b3cd4e88
./include/linux/modules/ksyms.ver:#define
proc_doulongvec_ms_jiffies_minmax_set_ver(proc_doulongvec_ms_jiffies_minmax)
./include/linux/modules/ksyms.ver:#define __ver_jiffies
smp_0da02d67
./include/linux/modules/ksyms.ver:#define jiffies
_set_ver(jiffies)
On the other hand, if I do the same as above except for `make -j2 dep'
I don't get any versioning info for jiffies. Looks like parallel build
is broken.
Uros
--
Uros Prestor
uros@turbolinux.com
next prev parent reply other threads:[~2001-01-10 19:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 2:03 [Linux-ia64] Undefined symbols Uros Prestor
2001-01-10 2:36 ` Keith Owens
2001-01-10 19:34 ` Uros Prestor [this message]
2001-01-10 21:11 ` Keith Owens
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-105590693005016@msgid-missing \
--to=uros@turbolinux.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 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.