Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Maemo: Community

Re: Unrecognized Option in ARM Build on Fremantle

 

 

Maemo community RSS feed   Index | Next | Previous | View Threaded


bartosh at gmail

Apr 27, 2009, 1:09 PM

Post #1 of 2 (496 views)
Permalink
Re: Unrecognized Option in ARM Build on Fremantle

Hi Ken,

Sorry for the delay. I wasn't able to read my mail last days.

2009/4/23 Kenneth Loafman <kenneth [at] loafman>:
> I'm getting an unrecognized option in the ARM build for Fremantle and the
> build fails, of course. I don't specify this anywhere, so where is it
> coming from and how do I nuke it?
>
The reason of this error is that scratchbox is using it's own python
by default. As far as I remember it's python 2.3. The problem is that
scratchbox python has bugs when building extensions as you can see.
And it's not only one problem with it, believe me :)

The solution is to use python2.5 from extras repository. To do that
you should replace python to python2.5 in debian/rules of your
package:

--- rules.orig 2009-04-27 23:05:57.000000000 +0300
+++ rules 2009-04-27 23:04:19.000000000 +0300
@@ -19,6 +19,8 @@
# we use dpatch
include /usr/share/dpatch/dpatch.make

+PYTHON:=python2.5
+
configure: configure-stamp
configure-stamp:
dh_testdir
@@ -32,7 +34,7 @@
dh_testdir

# Add here commands to compile the package.
- python setup.py build
+ $(PYTHON) setup.py build
touch build-stamp


@@ -54,7 +56,7 @@
dh_installdirs

# Add here commands to install the package into debian/duplicity.
- python setup.py install --prefix=$(PREFIX) --no-compile
--install-layout=deb || python setup.py install --prefix=$(PREFIX)
--no-compile
+ $(PYTHON) setup.py install --prefix=$(PREFIX) --no-compile
--install-layout=deb || $(PYTHON) setup.py install --prefix=$(PREFIX)
--no-compile

# remove docs as we create them with debhelper
rm -rf $(PREFIX)/share/doc/duplicity-*

It should do the trick for you.

Regards,
Ed

> ...Thanks,
> ...Ken
>
> running build_ext
> building 'duplicity._librsync' extension
> creating build/temp.linux-arm-2.3
> /scratchbox/compilers/host-gcc/bin/gcc
> -specs=/scratchbox/compilers/host-gcc/host-gcc.specs -pthread
> -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC
> -I/scratchbox/tools/include/python2.3 -c _librsyncmodule.c -o
> build/temp.linux-arm-2.3/_librsyncmodule.o
> /scratchbox/compilers/cs2007q3-glibc2.5-arm7/bin/sbox-arm-none-linux-gnueabi-as:
> unrecognized option `-Qy'
> error: command '/scratchbox/compilers/host-gcc/bin/gcc' failed with exit
> status 1
> make: *** [build-stamp] Error 1
>
> _______________________________________________
> maemo-community mailing list
> maemo-community [at] maemo
> https://lists.maemo.org/mailman/listinfo/maemo-community
>


--
BR,
Ed
_______________________________________________
maemo-community mailing list
maemo-community [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-community


kenneth at loafman

Apr 27, 2009, 2:26 PM

Post #2 of 2 (462 views)
Permalink
Re: Unrecognized Option in ARM Build on Fremantle [In reply to]

Ed Bartosh wrote:
> Hi Ken,
>
> Sorry for the delay. I wasn't able to read my mail last days.
>
> 2009/4/23 Kenneth Loafman <kenneth [at] loafman>:
>> I'm getting an unrecognized option in the ARM build for Fremantle and the
>> build fails, of course. I don't specify this anywhere, so where is it
>> coming from and how do I nuke it?
>>
> The reason of this error is that scratchbox is using it's own python
> by default. As far as I remember it's python 2.3. The problem is that
> scratchbox python has bugs when building extensions as you can see.
> And it's not only one problem with it, believe me :)
>
> The solution is to use python2.5 from extras repository. To do that
> you should replace python to python2.5 in debian/rules of your
> package:

Thanks! I appreciate the help.

I did figure this out, plus how to get it to install in site-packages
rather than getting it hidden somewhere that's not on the Python path.
That's the one I fought the longest since I really wanted to minimize
the changes rather than forking the source.

Been finding other differences along the way too, bash in Scratchbox vs
BusyBox on the device, that kind of thing. Still able to find portable
solutions, so all is starting to take shape, finally.

...Ken
_______________________________________________
maemo-community mailing list
maemo-community [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-community

Maemo community RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.