Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] new package: proxychains
Date: Tue, 08 Jan 2013 20:17:06 +0200	[thread overview]
Message-ID: <50EC62A2.8020505@petroprogram.com> (raw)
In-Reply-To: <20130108180957.30c9f629@skate>

Hi Thomas

8.1.2013 19:09, Thomas Petazzoni kirjoitti:
> Dear Stefan Fr?berg,
>
> On Sun, 23 Dec 2012 02:20:29 +0200, Stefan Fr?berg wrote:
>> Signed-off-by: Stefan Fr?berg <stefan.froberg@petroprogram.com>
>> ---
>>  package/Config.in                  |    1 +
>>  package/proxychains/Config.in      |    7 +++++++
>>  package/proxychains/proxychains.mk |   10 ++++++++++
>>  3 files changed, 18 insertions(+), 0 deletions(-)
>>  create mode 100644 package/proxychains/Config.in
>>  create mode 100644 package/proxychains/proxychains.mk
> This new package generates the following build failure:
>
>   http://autobuild.buildroot.org/results/7364b557c1fea642a3631c4735dd93f02ba70dd5/build-end.log
>
> Can you try to investigate and see if you can provide a patch to fix it?
>
> Thanks!
>
> Thomas

Well, I can try to make a patch to that  libproxychains.c:291:5: error:
conflicting types for 'getnameinfo'  error but I can't test it in arm
because I don't
have any real arm machine here and my poor hard drive is already so
stuffed that building arm qemu-image would be difficult
 :-(

But I will take a look of this

Stefan

  reply	other threads:[~2013-01-08 18:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-23  0:20 [Buildroot] [PATCH] new package: proxychains Stefan Fröberg
2012-12-23 21:17 ` Peter Korsgaard
2013-01-08 17:09 ` Thomas Petazzoni
2013-01-08 18:17   ` Stefan Fröberg [this message]
2013-01-08 18:47     ` Stefan Fröberg
2013-01-08 18:57   ` Stefan Fröberg
2013-01-08 19:18     ` Thomas Petazzoni
2013-01-08 19:31       ` Stefan Fröberg
2013-01-08 21:10         ` Stefan Fröberg

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=50EC62A2.8020505@petroprogram.com \
    --to=stefan.froberg@petroprogram.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