From: Nick Peirson <nick@netcentral.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] proftpd does not compile
Date: Mon, 6 Oct 2008 09:25:27 +0100 [thread overview]
Message-ID: <48E9CB77.8060808@netcentral.co.uk> (raw)
In-Reply-To: <gc8fta$bif$1@ger.gmane.org>
Micha Nelissen wrote:
> Further some warnings about bcopy also, I guess:
>
> #undef HAVE_BCOPY
> should be
> #define HAVE_BCOPY 1
>
> Obviously this is not a correct patch, but not sure about correct one?
> Kernel headers broken? configure script broken? toolchain headers?
>
You need to enable UCLIBC_SUSV3_LEGACY and/or UCLIBC_SUSV3_LEGACY_MACROS
(not sure exactly which combination, can anyone shed any light?) to
provide bcopy, bzero, index, etc. Alternatively you can submit an
upstream patch to proftpd, or patch it locally, to replace bcopy with
memmove as per:
http://www.opengroup.org/onlinepubs/000095399/functions/bcopy.html
--
Regards
Nick Peirson
Developer
Internet Central Ltd
Tel: +44 (0)1782 667788
Fax: +44 (0)1782 667799
Email: nick at netcentral.co.uk
Web: http://www.internet-central.net
Innovation Centre
Keele Science Park
Keele
Staffordshire
ST5 5NB
Registered office: Ivy House Foundry, Hanley, Stoke-on-Trent ST1 3NR
Registered in England. Reg. No. 3079542
VAT Reg No. GB 655 657 108
"This communication is confidential to the addressee shown in the main text of the message. It must not be disclosed to or used by anyone other than the addressee unless disclosure is a legal requirement or has been agreed to by a separate written agreement. The company scans for but accepts no responsibility for viruses and it is the addressee's responsibility to scan attachments."
next prev parent reply other threads:[~2008-10-06 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-04 19:22 [Buildroot] proftpd does not compile Micha Nelissen
2008-10-06 8:25 ` Nick Peirson [this message]
2008-10-06 15:58 ` Micha Nelissen
2008-10-06 16:20 ` Nick Peirson
2008-10-07 20:39 ` Micha Nelissen
2008-10-07 20:59 ` Bernhard Reutner-Fischer
2008-10-07 21:14 ` Micha Nelissen
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=48E9CB77.8060808@netcentral.co.uk \
--to=nick@netcentral.co.uk \
--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 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.