From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot for AM3358 AM3359 with wireless-tools shared library
Date: Fri, 28 Dec 2012 14:21:15 +0100 [thread overview]
Message-ID: <20121228142115.50e3643d@skate> (raw)
In-Reply-To: <1351596954.5576.22.camel@debian.fritz.box>
Dear J?rgen Benjamin Ronshausen,
On Tue, 30 Oct 2012 12:35:54 +0100, J?rgen Benjamin Ronshausen wrote:
> i am developing wireless tracking software. i use the wireless-tools
> library to scan for wireless networks in the area.
>
> i hope to use buildroot for compiling the c program, and to handle the
> library part. my program includes #include <iwlib.h>.
>
> on my old board (arm926t) i could compile by
> ~/buildroot-2012.08/output/host/usr/bin/arm-linux-gcc -Wall -o
> "oldboard" "main.c" -liw
>
> The new Board is a AM335x Starter Kit with a Sitara AM3358 Cortex A8 cpu
> and WL1271 Wifi/bluetooth module.
>
> to make my toolchain i issue:
>
> make beaglebone_defconfig
> make menuconfig and select under packages, networking wireless-tools and
> library. i included contents of .config below.
>
> The first problem is, that there are no files in
> /home/john/AM335/buildroot/output/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/lib
> i am not sure about it, but i think there should be the .so files for
> the compiler.
The problem you reported at
https://raw.github.com/steven11/the-hunt-for-wireless-tools/master/logfile1
was fixed in the current Git repository of Buildroot. It was a problem
on 32 bits hosts while building a toolchain with largefile support
disabled.
The commit fixing it is
http://git.buildroot.net/buildroot/commit/?id=7ce93438c12ca68c9bb12ed28c4d15d1fa840c94.
You can either use the current Git of Buildroot, of backport this fix
in 2012.11 (which should be trivial).
Do not hesitate to let us know if this solves your problem, or if you
face other issues.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2012-12-28 13:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 17:42 [Buildroot] buildroot for AM3358 AM3359 with wireless-tools shared library Michael Stieler
2012-10-25 18:18 ` Thomas Petazzoni
2012-10-25 18:23 ` Baruch Siach
2012-10-28 9:36 ` Peter Korsgaard
2012-10-30 11:35 ` Jürgen Benjamin Ronshausen
2012-10-30 22:13 ` Thomas Petazzoni
2012-10-31 11:30 ` Jürgen Benjamin Ronshausen
2012-10-31 23:06 ` Arnout Vandecappelle
2012-11-07 11:04 ` Jürgen Benjamin Ronshausen
2012-11-12 6:14 ` Arnout Vandecappelle
2012-12-28 13:21 ` Thomas Petazzoni [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=20121228142115.50e3643d@skate \
--to=thomas.petazzoni@free-electrons.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