All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gareth Wheelton" <gareth@hasslemonkey.net>
To: bridge@lists.osdl.org
Subject: RE: [Bridge] SUSE 8.1 build failure
Date: Wed, 18 Aug 2004 17:26:20 +0100	[thread overview]
Message-ID: <000b01c48540$189cb1e0$ba00a8c0@hasslemonkey.net> (raw)
In-Reply-To: <1092728709.2909.4.camel@scaramouche>

I think 'libbride_private.h' was missing '#include <linux/hz.h>'

OK that's sorts out the compile, leaving the following link error:

gcc  brctl.o brctl_cmd.o brctl_disp.o  -L ../libbridge -lbridge  -o brctl
../libbridge/libbridge.a(libbridge_devif.o): In function `get_hz':
/usr/src/linux/include/linux/hz.h:19: undefined reference to `__HZ'
collect2: ld returned 1 exit status
make: *** [brctl] Error 1


Using 'nm' I found many modules under '/lib/modules/2.4.21-241-athlon'
referencing an undefined symbol '__HZ_R799069f6'. Maybe this is related?

My kernel is configured correctly i.e. CONFIG_BRIDGE=m


So where does '__HZ' live?


Cheers again.


gareth



-----Original Message-----
From: Torsten Luettgert [mailto:t.luettgert@pressestimmen.de] 
Sent: 17 August 2004 08:45
To: Gareth Wheelton
Cc: bridge@lists.osdl.org
Subject: RE: [Bridge] SUSE 8.1 build failure

On Die, 2004-08-17 at 02:35, Gareth Wheelton wrote:
> Does anyone know where 'HZ' is declared in the 2.4.xx source?

grep is your friend:

# fgrep -r '#define HZ' /usr/src/linux
[...]
/usr/src/linux/include/asm-i386/param.h:#define HZ 100
[...]

so, you should insert

#include <asm/param.h>

into the module that doesn't compile.

- Torsten




  reply	other threads:[~2004-08-18 16:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-15 14:12 [Bridge] SUSE 8.1 build failure Gareth Wheelton
2004-08-17  0:35 ` Gareth Wheelton
2004-08-17  7:45   ` Torsten Luettgert
2004-08-18 16:26     ` Gareth Wheelton [this message]
2004-08-24 20:59 ` Stephen Hemminger

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='000b01c48540$189cb1e0$ba00a8c0@hasslemonkey.net' \
    --to=gareth@hasslemonkey.net \
    --cc=bridge@lists.osdl.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.