From: Tony Vroon <tony@linx.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linux-wireless@vger.kernel.org,
"Diego E. 'Flameeyes' Pettenò" <flameeyes@gmail.com>
Subject: Re: [ANN] crda v1.0.0
Date: Sat, 24 Jan 2009 15:55:57 +0000 [thread overview]
Message-ID: <1232812557.19657.6.camel@localhost> (raw)
In-Reply-To: <20090123235725.GC30761@tesla>
[-- Attachment #1: Type: text/plain, Size: 5351 bytes --]
On Fri, 2009-01-23 at 15:57 -0800, Luis R. Rodriguez wrote:
> The crda code has been intact for a while now, no main issues
> have been found or reported. As such this wraps up its 1.0.0
> release, and I doubt it will be changed for a while.
Thanks Luis.
Two questions:
1) Could you please drop that v from the tarball name. It's new, and it
means extra work for me. The old naming was perfect for automatic
handling.
2) You say the only changes were manpages, example directories and a
spec file, but it introduces a new build failure for me:
>>> Unpacking source...
>>> Unpacking crda-v1.0.0.tar.bz2
to /var/tmp/portage/net-wireless/crda-1.0.0/work
>>> Source unpacked in /var/tmp/portage/net-wireless/crda-1.0.0/work
>>> Compiling source
in /var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0 ...
make -j8 CC=x86_64-pc-linux-gnu-gcc
GEN keys-gcrypt.c
CC crda.o
CC intersect.o
CC print-regdom.o
CC regdbdump.o
CC reglib.o
LD regdbdump
LD intersect
CHK /usr/lib/crda/regulatory.bin
LD crda
crda.o: In function `nl_socket_alloc':
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:28:
undefined reference to `nl_handle_alloc'
crda.o: In function `nl80211_init':
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:64:
undefined reference to `genl_connect'
crda.o: In function `__genl_ctrl_alloc_cache':
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:38:
undefined reference to `genl_ctrl_alloc_cache'
crda.o: In function `nl80211_init':
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:76:
undefined reference to `genl_ctrl_search_by_name'
crda.o: In function `main':
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:252:
undefined reference to `nlmsg_alloc'
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:259:
undefined reference to `genl_family_get_id'
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:259:
undefined reference to `genlmsg_put'
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:270:
undefined reference to `nla_put'
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:320:
undefined reference to `nlmsg_free'
crda.o: In function `nl80211_cleanup':
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:94:
undefined reference to `genl_family_put'
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:95:
undefined reference to `nl_cache_free'
crda.o: In function `nl_socket_free':
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:33:
undefined reference to `nl_handle_destroy'
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:33:
undefined reference to `nl_handle_destroy'
crda.o: In function `main':
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:272:
undefined reference to `nla_nest_start'
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:280:
undefined reference to `nla_nest_start'
crda.o: In function `put_reg_rule':
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:130:
undefined reference to `nla_put'
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:131:
undefined reference to `nla_put'
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:132:
undefined reference to `nla_put'
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:133:
undefined reference to `nla_put'
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:134:
undefined reference to `nla_put'
crda.o:/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:135: more undefined references to `nla_put' follow
crda.o: In function `main':
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:288:
undefined reference to `nla_nest_end'
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:291:
undefined reference to `nla_nest_end'
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:293:
undefined reference to `nl_cb_alloc'
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:297:
undefined reference to `nl_send_auto_complete'
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:304:
undefined reference to `nl_cb_set'
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:305:
undefined reference to `nl_cb_set'
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:306:
undefined reference to `nl_cb_err'
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:318:
undefined reference to `nl_cb_put'
crda.o: In function `nl80211_init':
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:86:
undefined reference to `nl_cache_free'
crda.o: In function `main':
/var/tmp/portage/net-wireless/crda-1.0.0/work/crda-v1.0.0/crda.c:309:
undefined reference to `nl_wait_for_ack'
collect2: ld returned 1 exit status
make: *** [crda] Error 1
Is it possible that you inadvertently broke the ability to build in
parallel? This is make -j8 on a dual quad-core Opteron, so there are 8
cores ready to handle jobs. I've seen it break compilations before.
I have CC'd Diego on the e-mail, just in case it's an easy fix.
Regards,
Tony V.
P.S. Resend, accidentally used wrong FROM address. Apologies.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-24 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 23:57 [ANN] crda v1.0.0 Luis R. Rodriguez
2009-01-24 15:54 ` Tony Vroon
2009-01-24 15:55 ` Tony Vroon [this message]
2009-01-24 16:05 ` Diego E. 'Flameeyes' Petteno`
2009-01-24 20:41 ` Luis R. Rodriguez
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=1232812557.19657.6.camel@localhost \
--to=tony@linx.net \
--cc=flameeyes@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
/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;
as well as URLs for NNTP newsgroup(s).