I never found the real problem causing this. At some point in all my changes, this problem 'went away'. Truth is that problems don't go away, they just go into hiding waiting for the next critical point to show up again. Maybe this one got fixed somewhere else.
...Thanks, ...Ken Kenneth Loafman wrote: > Folks, > > I'm getting an unrecognized option `-Qy' in the ARM build for Diablo and > Fremantle. The build fails, of course. I don't specify this anywhere, > so where is it coming from and how do I get rid of it? > > ...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-developers mailing list > [email protected] > https://lists.maemo.org/mailman/listinfo/maemo-developers > _______________________________________________ maemo-developers mailing list [email protected] https://lists.maemo.org/mailman/listinfo/maemo-developers
