From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: With new Patches 030-041 'dnsmasq' 2.75 won't compile anymore
Date: Tue, 05 Jan 2016 20:53:52 +0100 [thread overview]
Message-ID: <568C1F50.7080804@ipfire.org> (raw)
In-Reply-To: <1451948440.31655.275.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
Hi,
On 05.01.2016 00:00, Michael Tremer wrote:
> please add the dnsmasq list and let Simon know.
Did that and made a small step forward - 'dnsmasq' is compiling now, but...
I don't know if you're reading the dnsmasq list - the only solution until now was
to compile *with* dhcp-support by removing...
***SNIP***
"-e 's|#define HAVE_DHCP|//#define HAVE_DHCP|g' \"
***SNAP***
Only warning during build:
***SNIP***
isc.c: In function 'dhcp_lease_new':
isc.c:40:3: warning: ignoring return value of 'asprintf', declared with attribute warn_unused_result [-Wunused-result]
asprintf(&lease->fqdn, "%s.%s", hostname, daemon->domain_suffix);
^
***SNAP***
I hope this will make no big difference for testing, since as far as I know,
'dnsmasq' has dhcp-server disabled by default. To enable it you have to
uncomment dhcp-related lines in '/etc/dnsmasq.conf'(e.g.), which doesn't exist.
But this was the only chance by now.
What do you think?
Best,
Matthias
next prev parent reply other threads:[~2016-01-05 19:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-02 11:55 Matthias Fischer
2016-01-04 16:42 ` Michael Tremer
2016-01-04 19:04 ` Matthias Fischer
2016-01-04 22:59 ` Matthias Fischer
2016-01-04 23:00 ` Michael Tremer
2016-01-04 23:30 ` Matthias Fischer
2016-01-05 19:53 ` Matthias Fischer [this message]
2016-01-06 19:31 ` Michael Tremer
2016-01-06 19:55 ` Matthias Fischer
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=568C1F50.7080804@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox