[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: armel package building



Thanks for the reply,

I am using the commands you listed below, except my CFLAGS are set in a gcc script that points to either gcc-4.1 or gcc-4.2 for easy change.  Did not add -O2 or -g, but that should not matter since I'm not getting that far :(

I use dpkg-buildpackage -rfakeroot -b -us -uc, but again tried your -B suggestion with the same results (m4 failure)
...
autoconf
/usr/bin/m4:configure.in:966: ERROR: end of file in string
autom4te: /usr/bin/m4 failed with exit status: 1
make: *** [build-stamp] Error 1
dpkg-buildpackage: failure: debian/rules build gave error exit status 2

I am running in a chroot'd armel/lenny from Debian   All Debian tools on a v7 variant.  sources.list is:
deb http://http.us.debian.org/debian lenny main non-free contrib
deb-src http://http.us.debian.org/debian lenny main non-free contrib

Are there any special kernel rqmnts for m4?  I run a minimal chroot system and kernel...
Thanks for the assistance
J

On Thu, May 22, 2008 at 4:35 AM, Riku Voipio <riku.voipio@iki.fi> wrote:
On Wed, May 21, 2008 at 04:32:53PM -0400, Joe Foster wrote:
>    We have see errors during dpkg-buildpackage when m4 is invoked:

What your build commands / enviroinment ?

apt-get source xaos
cd xaos-*/
apt-get build-dep xaos
export CFLAGS="-mfpu=vfp -mfloat-abi=softfp -O2 -g"
dpkg-buildpackage -B

and xaos configured and build fine.




>    ...
>    rmdir src/lib || true
>     debian/rules build
>    dh_testdir
>    ln -sf /usr/share/misc/config.sub
>    ln -sf /usr/share/misc/config.guess
>    autoconf
>    /usr/bin/m4:[1]configure.in:966: Warning: excess arguments to builtin
>    `m4_define' ignored
>    autom4te: /usr/bin/m4 failed with exit status: 1
>    make: *** [build-stamp] Error 1
>    dpkg-buildpackage: failure: debian/rules build gave error exit status 2
>    Failed to dpkg-buildpackage while processing package xaos
>
>    The autom4te/m4 tool fails on other builds as well (xpdf as an example).
>
>    Is there a fix or does anyone have suggestions?
>
>    Thanks
>    Joe
>
> References
>
>    Visible links
>    1. http://configure.in:966/

--
"rm -rf" only sounds scary if you don't have backups


Reply to: