Hi Juergen
GB> arm-linux-gcc: unrecognized option '-02'
JB> ^^^^^ Whats that? Try with -O2 (O like
octopus, not zero)
To be honest I don't know where the -02 (zero-2) option is coming from, I
assumed it was supplied
by ptxdist environment. Is that likely ?
<SNIP...>
GB> /home/wrap/pxaproj1/local/arm-linux/include -isystem
GB> /home/wrap/pxaproj1/local/arm-linux/usr/include -02 -Os -MT
^^^^^^^
JB>Choose for -O2 *or* -Os.
Similar remark, I need to track down where this is coming from.
GB> src/ping_host.c:240: error: impossible constraint in 'asm'
GB> {standard input}: Assembler messages:
GB> {standard input}:392: Error: bad instruction `btsl r2,[r3,#-176]'
JB>Sounds like a toolchain failure. Can you repeat it with one of our
OSELAS-Toolchains?
How do I setup one of your OSELAS-Toolchains, something 'close to
arm-linux-gcc-4.1.1' ?
GB>$(STATEDIR)/bewt.prepare: $(bewt_prepare_deps_default)
GB> @$(call targetinfo, $@)
GB> @$(call clean, $(BEWT_DIR)/config.cache)
GB> cd $(BEWT_DIR) && \
GB> $(BEWT_PATH) $(BEWT_ENV) \
GB> ./configure $(BEWT_AUTOCONF)
GB> cd $(BEWT_DIR) && \
GB> $(BEWT_PATH) $(BEWT_ENV) \
GB> ./configure $(BEWT_AUTOCONF)
GB> @$(call touch, $@)
JB> What does this mean? Running configure twice?
Ooops ... That's my mistake. I'll clean that up and try again.
Thanks
Graeme
-----Original Message-----
From: Juergen Beisert [mailto:[EMAIL PROTECTED]
Sent: 31 July 2007 15:42
To: [email protected]
Cc: Brown,GN,Graeme,CXR2 R
Subject: Re: [ptxdist] Cross-compiling Problem with Boingo Embedded Wireless
Toolkit for arm target
Graeme,
On Tuesday 31 July 2007 15:59, [EMAIL PROTECTED] wrote:
> I am trying to integrate the Boingo Embedded Wireless Toolkit (BEWT)
> [see http://sourceforge.net/projects/boingowifitool/ ] to compile
> under ptxdist-1.0.0 for an arm-based target. I am trying to write
> rules/bewt.make in my local project rules directory.
> BEWT has dependencies on the wireless-tools and libcurl (I have
> integrated this into my configuration for my local project). BEWT
> comes with auto-tools Support for building. I have successfully done
> ptxdist get bewt -OK ptxdist prepare bewt - OK
>
> But
> ptxdist compile bewt - BREAKS
>
> My compiler is arm-linux-gcc version 4.1.1 supplied by my reference
> board vendor.
>
> Configuration step appears to be OK.
> However an assembler complains during complilation ...
> <SNIP...>
> ptxdist compile bewt
> <SNIP...>
> arm-linux-gcc: unrecognized option '-02'
^^^^^ Whats that? Try with -O2 (O like
octopus, not zero)
> arm-linux-g++ -DPACKAGE_NAME=\"boingowifitoolkit\"
> -DPACKAGE_TARNAME=\"boingowifitoolkit\" -DPACKAGE_VERSION=\"1.0\"
> "-DPACKAGE_STRING=\"boingowifitoolkit 1.0\""
> -DPACKAGE_BUGREPORT=\"[EMAIL PROTECTED]" -DPACKAGE=\"boingowifitoolkit\"
> -DVERSION=\"1.0\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1
> -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
> -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1
> -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_LIBM=1
> -DHAVE_LIBIW=1 -DHAVE_LIBCURL=1 -DHAVE_LIBPTHREAD=1 -DLINUX=1
> -DWIFI_DEVICE=1 -D_REENTRANT=1 -I. -I. -pipe -I/usr/include
> -I./../../lib/proxies/include -I./../../lib/storage/include
> -I./../../lib/platform/include -I./../../lib/wifiengine/include
> -I./../../lib/interpreter/include -I./../../lib/http/include
> -I./include -I./. -I./../../lib/updater/include
> -I./../../lib/xml/include -I./../../lib/networkreporter/include
> -DPAL_EXPORTS -DPLATFORM_EXPORTS -isystem
> /home/wrap/pxaproj1/local/arm-linux/include -isystem
> /home/wrap/pxaproj1/local/arm-linux/usr/include -02 -Os -MT
^^^^^^^
Choose for -O2 *or* -Os.
> PalLogging.lo -MD -MP -MF .deps/PalLogging.Tpo -c src/PalLogging.cpp
> -o PalLogging.o >/dev/null 2>&1
> src/ping_host.c: In function 'ping_host':
> src/ping_host.c:240: error: impossible constraint in 'asm'
> {standard input}: Assembler messages:
> {standard input}:392: Error: bad instruction `btsl r2,[r3,#-176]'
Sounds like a toolchain failure. Can you repeat it with one of our
OSELAS-Toolchains?
> PACKAGES-$(PTXCONF_BEWT) += bewt
>
> #
> # Paths and names
> #
> BEWT_VERSION := rev101
> BEWT := bewt2_$(BEWT_VERSION)
> BEWT_SUFFIX := tgz
> BEWT_URL :=
> http://kent.dl.sourceforge.net/sourceforge/boingowifitool/$(BEWT).$(BE
> WT
> _SUFFIX)
> BEWT_SOURCE := $(SRCDIR)/$(BEWT).$(BEWT_SUFFIX)
> BEWT_DIR := $(BUILDDIR)/$(BEWT)
>
> #
> ----------------------------------------------------------------------
> --
> ----
> # Get
> #
> ----------------------------------------------------------------------
> --
> ----
>
> bewt_get: $(STATEDIR)/bewt.get
>
> $(STATEDIR)/bewt.get: $(bewt_get_deps_default)
> @$(call targetinfo, $@)
> @$(call touch, $@)
>
> $(BEWT_SOURCE):
> @$(call targetinfo, $@)
> # @$(call get, BEWT)
>
> #
> ----------------------------------------------------------------------
> --
> ----
> # Extract
> #
> ----------------------------------------------------------------------
> --
> ----
>
> bewt_extract: $(STATEDIR)/bewt.extract
>
> $(STATEDIR)/bewt.extract: $(bewt_extract_deps_default)
> @$(call targetinfo, $@)
> @$(call clean, $(BEWT_DIR))
> @$(call extract, BEWT)
> @$(call patchin, BEWT)
> @$(call touch, $@)
>
> #
> ----------------------------------------------------------------------
> --
> ----
> # Prepare
> #
> ----------------------------------------------------------------------
> --
> ----
>
> bewt_prepare: $(STATEDIR)/bewt.prepare
>
> BEWT_PATH := PATH=$(CROSS_PATH)
> BEWT_ENV := $(CROSS_ENV)
>
> #
> # autoconf
> #
> BEWT_AUTOCONF := $(CROSS_AUTOCONF_USR)
>
> $(STATEDIR)/bewt.prepare: $(bewt_prepare_deps_default)
> @$(call targetinfo, $@)
> @$(call clean, $(BEWT_DIR)/config.cache)
> cd $(BEWT_DIR) && \
> $(BEWT_PATH) $(BEWT_ENV) \
> ./configure $(BEWT_AUTOCONF)
> cd $(BEWT_DIR) && \
> $(BEWT_PATH) $(BEWT_ENV) \
> ./configure $(BEWT_AUTOCONF)
> @$(call touch, $@)
What does this mean? Running configure twice?
> I have been able to cross-compile bewt under the scratchbox tool
> successfully (same version as here, Same dependent packages as here).
> However my ptxdist effort is broken !
Check configure results in both runs, and also both compile steps.
Juergen
--
Dipl.-Ing. Juergen Beisert | http://www.pengutronix.de
Pengutronix - Linux Solutions for Science and Industry
Handelsregister: Amtsgericht Hildesheim, HRA 2686
Vertretung Sued/Muenchen, Germany
Phone: +49-8766-939 228 | Fax: +49-5121-206917-9
--
ptxdist mailing list
[email protected]
