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:47:39 +0200	[thread overview]
Message-ID: <50EC69CB.20003@petroprogram.com> (raw)
In-Reply-To: <50EC62A2.8020505@petroprogram.com>


Thomas, this is what my getnameinfo() function from
$(STAGING_DIR)/usr/include/netdb.h  looks like:

/* Translate a socket address to a location and service name.

   This function is a possible cancellation point and therefore not
   marked with __THROW.  */
extern int getnameinfo (__const struct sockaddr *__restrict __sa,
            socklen_t __salen, char *__restrict __host,
            socklen_t __hostlen, char *__restrict __serv,
            socklen_t __servlen, unsigned int __flags);
#endif    /* POSIX */

__END_DECLS

#endif    /* netdb.h */

And here is the snip of my proxychain building

^[[7m>>> proxychains 3.1 Building^[[27m
PATH="/mnt/hee/new/buildroot-2012.08/output/host/bin:/mnt/hee/new/buildroot-2012.08/output/host/usr/bin:/mnt/hee/new/buildroot-2012.08/output/host/usr/sbin/:/root/perl5/bin:/root/perl5/bin:/root/perl5/bin:/usr/lib/ccache:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin"
PERLLIB="/mnt/hee/new/buildroot-2012.08/output/host/usr/lib/perl" 
/usr/bin/make -j4  -C
/mnt/hee/new/buildroot-2012.08/output/build/proxychains-3.1/
make[1]: Siirryt??n hakemistoon
"/mnt/hee/new/buildroot-2012.08/output/build/proxychains-3.1"
/usr/bin/make  all-recursive
make[2]: Siirryt??n hakemistoon
"/mnt/hee/new/buildroot-2012.08/output/build/proxychains-3.1"
Making all in proxychains
make[3]: Siirryt??n hakemistoon
"/mnt/hee/new/buildroot-2012.08/output/build/proxychains-3.1/proxychains"
Making all in docs
make[4]: Siirryt??n hakemistoon
"/mnt/hee/new/buildroot-2012.08/output/build/proxychains-3.1/proxychains/docs"
Making all in en
make[5]: Siirryt??n hakemistoon
"/mnt/hee/new/buildroot-2012.08/output/build/proxychains-3.1/proxychains/docs/en"
make[5]: Kohteelle "all" ei tarvitse tehd? mit??n.
make[5]: Poistutaan hakemistosta
"/mnt/hee/new/buildroot-2012.08/output/build/proxychains-3.1/proxychains/docs/en"
make[5]: Siirryt??n hakemistoon
"/mnt/hee/new/buildroot-2012.08/output/build/proxychains-3.1/proxychains/docs"
make[5]: Kohteelle "all-am" ei tarvitse tehd? mit??n.
make[5]: Poistutaan hakemistosta
"/mnt/hee/new/buildroot-2012.08/output/build/proxychains-3.1/proxychains/docs"
make[4]: Poistutaan hakemistosta
"/mnt/hee/new/buildroot-2012.08/output/build/proxychains-3.1/proxychains/docs"
make[4]: Siirryt??n hakemistoon
"/mnt/hee/new/buildroot-2012.08/output/build/proxychains-3.1/proxychains"
/bin/sh ../libtool --mode=compile
/mnt/hee/new/buildroot-2012.08/output/host/usr/bin/i586-unknown-linux-uclibc-gcc
-DHAVE_CONFIG_H -I. -I. -I..     -pipe -funit-at-a-time -Wno-error -Os
-Os  -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -c
libproxychains.c
/bin/sh ../libtool --mode=compile
/mnt/hee/new/buildroot-2012.08/output/host/usr/bin/i586-unknown-linux-uclibc-gcc
-DHAVE_CONFIG_H -I. -I. -I..     -pipe -funit-at-a-time -Wno-error -Os
-Os  -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -c
core.c
mkdir .libs
 /mnt/hee/new/buildroot-2012.08/output/host/usr/bin/i586-unknown-linux-uclibc-gcc
-DHAVE_CONFIG_H -I. -I. -I.. -pipe -funit-at-a-time -Wno-error -Os -Os
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
-Wp,-MD,.deps/libproxychains.pp -c libproxychains.c  -fPIC -DPIC -o
.libs/libproxychains.o
 /mnt/hee/new/buildroot-2012.08/output/host/usr/bin/i586-unknown-linux-uclibc-gcc
-DHAVE_CONFIG_H -I. -I. -I.. -pipe -funit-at-a-time -Wno-error -Os -Os
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
-Wp,-MD,.deps/core.pp -c core.c  -fPIC -DPIC -o .libs/core.o
 /mnt/hee/new/buildroot-2012.08/output/host/usr/bin/i586-unknown-linux-uclibc-gcc
-DHAVE_CONFIG_H -I. -I. -I.. -pipe -funit-at-a-time -Wno-error -Os -Os
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
-Wp,-MD,.deps/libproxychains.pp -c libproxychains.c -o libproxychains.o
>/dev/null 2>&1
 /mnt/hee/new/buildroot-2012.08/output/host/usr/bin/i586-unknown-linux-uclibc-gcc
-DHAVE_CONFIG_H -I. -I. -I.. -pipe -funit-at-a-time -Wno-error -Os -Os
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
-Wp,-MD,.deps/core.pp -c core.c -o core.o >/dev/null 2>&1
/bin/sh ../libtool --mode=link
/mnt/hee/new/buildroot-2012.08/output/host/usr/bin/i586-unknown-linux-uclibc-gcc 
-pipe -funit-at-a-time -Wno-error -Os -Os  -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Wl,-S -Wl,-O1
-Wl,--as-needed -Wl,-z -Wl,combreloc -Wl,--enable-new-dtags
-Wl,--hash-style=gnu -o libproxychains.la -rpath /usr/lib -version-info
3:0:0  libproxychains.lo core.lo -ldl
/mnt/hee/new/buildroot-2012.08/output/host/usr/bin/i586-unknown-linux-uclibc-gcc
-shared  .libs/libproxychains.o .libs/core.o  -ldl  -Wl,-S -Wl,-O1
-Wl,--as-needed -Wl,-z -Wl,combreloc -Wl,--enable-new-dtags
-Wl,--hash-style=gnu -Wl,-soname -Wl,libproxychains.so.3 -o
.libs/libproxychains.so.3.0.0
(cd .libs && rm -f libproxychains.so.3 && ln -s libproxychains.so.3.0.0
libproxychains.so.3)
(cd .libs && rm -f libproxychains.so && ln -s libproxychains.so.3.0.0
libproxychains.so)
/mnt/hee/new/buildroot-2012.08/output/host/usr/bin/i586-unknown-linux-uclibc-ar
cru .libs/libproxychains.a  libproxychains.o core.o
/mnt/hee/new/buildroot-2012.08/output/host/usr/bin/i586-unknown-linux-uclibc-ranlib
.libs/libproxychains.a
creating libproxychains.la


Stefan


8.1.2013 20:17, Stefan Fr?berg kirjoitti:
> 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
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2013-01-08 18:47 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
2013-01-08 18:47     ` Stefan Fröberg [this message]
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=50EC69CB.20003@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