Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Paul <pbor1234@zonnet.nl>
To: buildroot@busybox.net
Subject: [Buildroot] How to configure proftpd 1.3.0a package inbuildroot
Date: Wed, 16 Jan 2008 21:17:43 +0100	[thread overview]
Message-ID: <20080116201747.EBF95C6FB@green.qinip.net> (raw)
In-Reply-To: <20080116192701.GD27237@aon.at>

Bernhard,
Thanks, i added:

  toolchain/patch-kernel.sh $(PROFTPD_DIR) package/proftpd/ *.patch

To .unpacked: in /buildroot/package/proftpd/proftpd.mk

And it works.
Paul


-----Original Message-----
From: Bernhard Fischer [mailto:rep.dot.nop at gmail.com] 
Sent: woensdag 16 januari 2008 20:27
To: Paul
Cc: buildroot at uclibc.org
Subject: Re: [Buildroot] How to configure proftpd 1.3.0a package inbuildroot

On Wed, Jan 16, 2008 at 07:46:41PM +0100, Paul wrote:
>As a newby i'm stuck in the following, help is appreciated.
>
>I have selected the proftpd (1.3.0a) package in 'make menuconfig' and it
>build fine.
>
>Now I want to add the iconv patch (see for example
>http://home.h01.itscom.net/para/software/misc/proftpd-iconv/index-e.html)
>where it is described to run ./configure with some options to add the
>modules in question. If i do this (in the buildroot/build_powerpc/...) it
>fails and i think this is due to the fact that the staging_dir tools should
>be used which is not done the way i run ./configure.
>
> 
>
>My question: how should i do this correctly?

you would apply the patch before configuring, usually in the .unpacked
. See patch-kernel.sh usage in other packages.

HTH,
Bernhard

      reply	other threads:[~2008-01-16 20:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16 18:46 [Buildroot] How to configure proftpd 1.3.0a package in buildroot Paul
2008-01-16 19:27 ` Bernhard Fischer
2008-01-16 20:17   ` Paul [this message]

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=20080116201747.EBF95C6FB@green.qinip.net \
    --to=pbor1234@zonnet.nl \
    --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