From: Esteban Maringolo <esteban.maringolo@secont.com.ar>
To: lartc@vger.kernel.org
Subject: [LARTC] Problems compiling patched bridge-utils
Date: Tue, 17 Sep 2002 16:43:23 +0000 [thread overview]
Message-ID: <marc-lartc-103228116413150@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]
Hello,
I've applied ``bridge-utils-0.9.5-ipmode-1.diff'' to be able to use my
shaper as bridge and don't lose the netfilter capabilities, the patch
applies with no error messages, which makes me supose everything is
working fine.
But when i try to recompile the bridge-utils utilities i get the
message transcript below:
esteban@inercia:~/devel/nexusbm/bridge-utils-0.9.5$ make
make -C libbridge
make[1]: Entering directory
`/home/esteban/devel/bridge-shaper/bridge-utils-0.9.5/libbridge'
gcc -Wall -g -c libbridge_devif.c
libbridge_devif.c: In function `br_set_bridge_ip_mode':
libbridge_devif.c:151: `BRCTL_SET_BRIDGE_IP_MODE' undeclared (first use
in this function)
libbridge_devif.c:151: (Each undeclared identifier is reported only once
libbridge_devif.c:151: for each function it appears in.)
make[1]: *** [libbridge_devif.o] Error 1
make[1]: Leaving directory
`/home/esteban/devel/bridge-shaper/bridge-utils-0.9.5/libbridge'
make: *** [libbridge/libbridge.a] Error 2
If I compile the bridge-utils with no patch applied (or with the lower
version diff applied) it compiles seamsly, and I can build a .deb with
it too :-)
Any Clue?
--
Esteban A. Maringolo
Buenos Aires, Argentina
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2002-09-17 16:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 16:43 Esteban Maringolo [this message]
2002-09-17 17:10 ` [LARTC] Problems compiling patched bridge-utils Julian Anastasov
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-lartc-103228116413150@msgid-missing \
--to=esteban.maringolo@secont.com.ar \
--cc=lartc@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.