From: Rick Foos <rick@synchromeshcomputing.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] undefined symbol BR2_PACKAGE_LIBDAEMON
Date: Fri, 3 Aug 2007 16:29:41 -0500 [thread overview]
Message-ID: <015001c7d615$67ba0510$8200000a@k2> (raw)
In-Reply-To: 0708032117420.13739@somehost
Had the same problem here. Attached is a simple patch to fix it preserving
the current function.
The libdaemon Config.in was never included in the past, but the libdaemon.mk
file was in place.
Avahi.mk refereces the libdaemon make target.
Now that the select dependency is in avahi/Config.in, the missing source
libdaemon/Config.in is a problem.
Cheers,
Rick
----- Original Message -----
From: "Cristian Ionescu-Idbohrn" <cristian.ionescu-idbohrn@axis.com>
To: <buildroot@uclibc.org>
Sent: Friday, August 03, 2007 2:20 PM
Subject: [Buildroot] [bug] undefined symbol BR2_PACKAGE_LIBDAEMON
> package/avahi/Config.in:3:warning: 'select' used by config symbol
> 'BR2_PACKAGE_AVAHI' refer to undefined symbol 'BR2_PACKAGE_LIBDAEMON'
>
>
> Cheers,
>
> --
> Cristian
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.476 / Virus Database: 269.11.2/933 - Release Date: 8/2/2007
> 2:22 PM
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libdaemon-avahi.patch
Type: application/octet-stream
Size: 423 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20070803/c4b11665/attachment.obj
next prev parent reply other threads:[~2007-08-03 21:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 19:20 [Buildroot] [bug] undefined symbol BR2_PACKAGE_LIBDAEMON Cristian Ionescu-Idbohrn
2007-08-03 21:29 ` Rick Foos [this message]
2007-08-03 23:23 ` [Buildroot] [PATCH] " Cristian Ionescu-Idbohrn
2007-08-04 15:27 ` Rick Foos
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='015001c7d615$67ba0510$8200000a@k2' \
--to=rick@synchromeshcomputing.com \
--cc=buildroot@busybox.net \
/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