On Sun, 9 Sep 2007 15:06:34 -0700 Steve Langasek <[EMAIL PROTECTED]> wrote:
> > The upstream may be better but debian/rules still needs a tweak.
>
> Heh, fair enough; but I don't see anywhere that the original patch did
> anything to handle the cross-arch toolchain settings for the package
> either.
No, that's true. Things are still developing . .
;-)
> > First, set the cross-build detection:
> > DEB_HOST_GNU_TYPE := $(shell dpkg-architecture
> > -qDEB_HOST_GNU_TYPE) DEB_BUILD_GNU_TYPE := $(shell
> > dpkg-architecture -qDEB_BUILD_GNU_TYPE)
>
> > and one line to add to the ./configure arguments:
> > --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) \
>
> > Alternatively, create a $(CONFFLAGS) variable set the to --build and
> > --host arguments if $(DEB_HOST_GNU_TYPE) differs from
> > $(DEB_BUILD_GNU_TYPE) or blank otherwise.
>
> That really shouldn't be considered the "alternative". The first
> usage is wrong because it causes the compiler to be invoked /as/ a
> cross-compiler when it shouldn't be.
True. I'll update the docs so that the cross-compiler is only called
when necessary, as described. That will make it easier to add those
changes in Debian.
> > `yylex':
> > /opt/emdebian/trunk/p/pam/trunk/pam-0.99.7.1/Linux-PAM/conf/pam_conv1/pam_conv_l.c:831:
> > undefined reference to `yywrap' collect2: ld returned 1 exit status
> > make[5]: *** [pam_conv1] Error 1
>
> That means you're missing libfl in your cross-build environment.
Aha. Thanks for the tip. Identifying cross-build build-depends isn't
always straightforward. (Something else Emdebian developers are trying
to solve.)
$ sudo apt-cross -a arm -v -i flex
(set via debian/xcontrol)
> That's not a bug in the pam package, the build-dependencies are as
> correct as they can be.
Excellent. I'll sort that out and rebuild soon. I'll let you know the
result.
> ... most of which are wrong for Debian and should not be included.
Yes, these are works-in-progress and aren't ready for submission as
patches for Debian, yet.
> Does emdebian really not have a way of rendering
> dh_install{man,docs,changelogs,examples} inert without hacking
> individual packages?
Being implemented in dpkg by filtering - initially on install but also
upon build so that when building an emdebian package (modified version
string to identify it), certain filters are enabled that omit the files
that embedded devices don't need.
The current method is not scalable to the entire Debian archive but
then Emdebian isn't close to cross-building more than a hundred or so
packages out of the 18,000 so there's time to develop yet.
--
Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/
pgpV6QHXSQO5s.pgp
Description: PGP signature
