Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Micha Nelissen <micha@neli.hopto.org>
To: buildroot@busybox.net
Subject: [Buildroot] proftpd does not compile
Date: Mon, 06 Oct 2008 17:58:45 +0200	[thread overview]
Message-ID: <gcdcjp$v98$1@ger.gmane.org> (raw)
In-Reply-To: <48E9CB77.8060808@netcentral.co.uk>

Nick Peirson wrote:
> 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:

I'm not sure if you understood me right. The problem is that bcopy is 
declared twice (I get a redefinition warning). It is *not* that bcopy is 
undefined.

If I'm wrong please correct me, thanks.

Micha

  reply	other threads:[~2008-10-06 15:58 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
2008-10-06 15:58   ` Micha Nelissen [this message]
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='gcdcjp$v98$1@ger.gmane.org' \
    --to=micha@neli.hopto.org \
    --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