Bug#516585: [Pkg-alsa-devel] Bug#516585: RFH: alsa-lib
On Sun, Feb 22, 2009 at 07:49:12PM +0100, Andreas Metzler wrote: > Afaiui multilib and cross-compiling work differently and you wanted > multilib, not cross compiling. But my understanding of this area is > almost non-existing. If you wanted to cross compile for amd64 on > i386 you would set > > --build i486-linux-gnu --host x86_64-linux-gnu > > and this would cause ./configure to use amd64-pc-linux-gnu-gcc as > compiler. > > > Second: Why does it build on ppc ? > > No idea. :-( > > cu and- not getting the point of 64bit alsa on i486 anyway. - reas That's another point we wanted to discuss. Can anyone tell us if there's actually some point in providing lib64* packages /at all/? Should we drop them? If we should drop them, what is lib64z1, lib64ncurses, lib64readline5 and so on good for? The building of these packages came with the original biarch patch that was contributed ages ago. Jordi -- Jordi Mallach Pérez -- Debian developer http://www.debian.org/ jo...@sindominio.net jo...@debian.org http://www.sindominio.net/ GnuPG public key information available at http://oskuro.net/ -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#516585: RFH: alsa-lib
On 2009-02-22 Elimar Riesebieter wrote: > * Andreas Metzler [090222 17:42 +0100] >> On 2009-02-22 Elimar Riesebieter wrote: [...] >>> I want to prepare alsa-lib 1.0.19 for upload. Building alsa-lib on i386 and >>> amd64 gives: >>> ... >>> checking for strip... strip >>> checking for cross-compiler... i486-i486-pc-linux-gnu-gcc >>> checking for i486-linux-gnu-gcc... i486-i486-pc-linux-gnu-gcc >>> checking for C compiler default output file name... >>> configure: error: C compiler cannot create executables >>> See `config.log' for more details. [...] >> I am not sure, but I think (see >> /usr/share/doc/autotools-dev/README.Debian.gz) you are invoking >> ./configure the wrong way. This makes it build successfully for me: >> --- >> --- debian/rules(Revision 2165) >> +++ debian/rules(Arbeitskopie) [...] >> - --host=$(DEB_HOST_GNU_TYPE) \ >> + --build $(DEB_BUILD_GNU_TYPE) \ >> --- > Yes, but in that case: > > checking whether we are cross compiling... no > > This is what we don't want. Afaiui multilib and cross-compiling work differently and you wanted multilib, not cross compiling. But my understanding of this area is almost non-existing. If you wanted to cross compile for amd64 on i386 you would set --build i486-linux-gnu --host x86_64-linux-gnu and this would cause ./configure to use amd64-pc-linux-gnu-gcc as compiler. > Second: Why does it build on ppc ? No idea. :-( cu and- not getting the point of 64bit alsa on i486 anyway. - reas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#516585: RFH: alsa-lib
On Sun, 22 Feb 2009 17:42:06 +0100
Andreas Metzler wrote:
> On 2009-02-22 Elimar Riesebieter wrote:
> > Package: wnpp
> > Severity: normal
>
> > Hi Debian ALSA developers,
>
> > I want to prepare alsa-lib 1.0.19 for upload. Building alsa-lib on i386 and
> > amd64 gives:
> > ...
> > checking for strip... strip
> > checking for cross-compiler... i486-i486-pc-linux-gnu-gcc
> > checking for i486-linux-gnu-gcc... i486-i486-pc-linux-gnu-gcc
> > checking for C compiler default output file name...
> > configure: error: C compiler cannot create executables
> > See `config.log' for more details.
> [...]
> > The correct compiler should be: i486-linux-gnu-gcc and not
> > i486-i486-pc-linux-gnu-gcc!
It should actually probably be just gcc or cc. i486-linux-gnu-gcc is how
a cross-compiler would be called. See the discussion on debian-devel
some months back:
http://lists.debian.org/debian-devel/2007/11/msg00151.html
Steve Langasek wrote:
"There *is* a need to specify --build when not cross-compiling, if
your upstream build rules do clever things when the architecture is
detected as "i686" instead of "i386". This was the point in my previous
comment.
There is no need to specify --host when not cross-compiling, and
specifying it will result in autoconf believing that the compiler
should be invoked as a cross-compiler. Sometimes this has strange side
effects as well."
The issue here is that --host should only be passed when
cross-compiling and --build should be passed alone in a native build.
> I am not sure, but I think (see
> /usr/share/doc/autotools-dev/README.Debian.gz) you are invoking
> ./configure the wrong way. This makes it build successfully for me:
Slight tweak, needed. See: http://wiki.debian.org/EmdebianGuide
DEB_HOST_GNU_TYPE=$(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
DEB_BUILD_GNU_TYPE=$(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
ifneq ($(DEB_HOST_GNU_TYPE),$(DEB_BUILD_GNU_TYPE))
CONF_ARGS= --build $(DEB_BUILD_GNU_TYPE) --host $(DEB_HOST_GNU_TYPE)
else
CONF_ARGS= --build $(DEB_BUILD_GNU_TYPE)
endif
The actual variable name you use is at your discretion, the point is
that it only contains '--build $(DEB_BUILD_GNU_TYPE)' unless
cross-compiling when it also adds the relevant --host entry.
Then replace:
> - --host=$(DEB_BUILD_GNU_TYPE) \
> + --build $(DEB_BUILD_GNU_TYPE) \
with
+ $(CONF_ARGS)
>
> ---
> --- debian/rules(Revision 2165)
> +++ debian/rules(Arbeitskopie)
> @@ -56,7 +56,7 @@
> --mandir=\$${prefix}/share/man \
> --infodir=\$${prefix}/share/info \
> --datadir=\$${prefix}/share \
> - --host=$(DEB_BUILD_GNU_TYPE) \
> + --build $(DEB_BUILD_GNU_TYPE) \
> --enable-static --disable-maintainer-mode
> touch configure-stamp
>
> @@ -72,7 +72,7 @@
> --mandir=\$${prefix}/share/man \
> --infodir=\$${prefix}/share/info \
> --datadir=\$${prefix}/share \
> - --host=$(DEB_HOST_GNU_TYPE) \
> + --build $(DEB_BUILD_GNU_TYPE) \
> --enable-static --disable-maintainer-mode \
> --disable-python --with-plugindir=/$(bilibdir)/alsa-lib
> #ln -sf . include/alsa
> ---
--
Neil Williams
=
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/
pgpqX69JBRuPF.pgp
Description: PGP signature
Bug#516585: RFH: alsa-lib
* Andreas Metzler [090222 17:42 +0100]
> On 2009-02-22 Elimar Riesebieter wrote:
> > Package: wnpp
> > Severity: normal
>
> > Hi Debian ALSA developers,
>
> > I want to prepare alsa-lib 1.0.19 for upload. Building alsa-lib on i386 and
> > amd64 gives:
> > ...
> > checking for strip... strip
> > checking for cross-compiler... i486-i486-pc-linux-gnu-gcc
> > checking for i486-linux-gnu-gcc... i486-i486-pc-linux-gnu-gcc
> > checking for C compiler default output file name...
> > configure: error: C compiler cannot create executables
> > See `config.log' for more details.
> [...]
> > The correct compiler should be: i486-linux-gnu-gcc and not
> > i486-i486-pc-linux-gnu-gcc!
>
> > From upstreams changelog:
>
> > "Don't use AC_CANONICAL_SYSTEM, only use AC_CANONICAL_HOST"
>
> Hello,
>
> I am not sure, but I think (see
> /usr/share/doc/autotools-dev/README.Debian.gz) you are invoking
> ./configure the wrong way. This makes it build successfully for me:
>
> ---
> --- debian/rules(Revision 2165)
> +++ debian/rules(Arbeitskopie)
> @@ -56,7 +56,7 @@
> --mandir=\$${prefix}/share/man \
> --infodir=\$${prefix}/share/info \
> --datadir=\$${prefix}/share \
> - --host=$(DEB_BUILD_GNU_TYPE) \
> + --build $(DEB_BUILD_GNU_TYPE) \
> --enable-static --disable-maintainer-mode
> touch configure-stamp
>
> @@ -72,7 +72,7 @@
> --mandir=\$${prefix}/share/man \
> --infodir=\$${prefix}/share/info \
> --datadir=\$${prefix}/share \
> - --host=$(DEB_HOST_GNU_TYPE) \
> + --build $(DEB_BUILD_GNU_TYPE) \
> --enable-static --disable-maintainer-mode \
> --disable-python --with-plugindir=/$(bilibdir)/alsa-lib
> #ln -sf . include/alsa
> ---
Yes, but in that case:
checking whether we are cross compiling... no
This is what we don't want.
Second: Why does it build on ppc ?
Elimar
--
Numeric stability is probably not all that
important when you're guessing;-)
signature.asc
Description: Digital signature
Bug#516585: RFH: alsa-lib
On 2009-02-22 Elimar Riesebieter wrote:
> Package: wnpp
> Severity: normal
> Hi Debian ALSA developers,
> I want to prepare alsa-lib 1.0.19 for upload. Building alsa-lib on i386 and
> amd64 gives:
> ...
> checking for strip... strip
> checking for cross-compiler... i486-i486-pc-linux-gnu-gcc
> checking for i486-linux-gnu-gcc... i486-i486-pc-linux-gnu-gcc
> checking for C compiler default output file name...
> configure: error: C compiler cannot create executables
> See `config.log' for more details.
[...]
> The correct compiler should be: i486-linux-gnu-gcc and not
> i486-i486-pc-linux-gnu-gcc!
> From upstreams changelog:
> "Don't use AC_CANONICAL_SYSTEM, only use AC_CANONICAL_HOST"
Hello,
I am not sure, but I think (see
/usr/share/doc/autotools-dev/README.Debian.gz) you are invoking
./configure the wrong way. This makes it build successfully for me:
---
--- debian/rules(Revision 2165)
+++ debian/rules(Arbeitskopie)
@@ -56,7 +56,7 @@
--mandir=\$${prefix}/share/man \
--infodir=\$${prefix}/share/info \
--datadir=\$${prefix}/share \
- --host=$(DEB_BUILD_GNU_TYPE) \
+ --build $(DEB_BUILD_GNU_TYPE) \
--enable-static --disable-maintainer-mode
touch configure-stamp
@@ -72,7 +72,7 @@
--mandir=\$${prefix}/share/man \
--infodir=\$${prefix}/share/info \
--datadir=\$${prefix}/share \
- --host=$(DEB_HOST_GNU_TYPE) \
+ --build $(DEB_BUILD_GNU_TYPE) \
--enable-static --disable-maintainer-mode \
--disable-python --with-plugindir=/$(bilibdir)/alsa-lib
#ln -sf . include/alsa
---
And the new buildlog (the gcc invokations) is basically identical to
1.0.18-1.
[...]
> The orig tgz must be loaded from:
> wget ftp://ftp.alsa-project.org/pub/lib/alsa-lib-1.0.19.tar.bz2
> tar jxf alsa-lib-1.0.19.tar.bz2
> tar zcf alsa-lib-1.0.19.tar.gz alsa-lib-1.0.19
> mv alsa-lib-1.0.19.tar.gz alsa-lib_1.0.19.orig.tar.gz
I prefer this for bz2- only packages:
bzcat alsa-lib-1.0.19.tar.bz2 | gzip -9 --rsyncable >
alsa-lib_1.0.19.orig.tar.gz
* Saves diskspace
* Faster
* mdsum of upstream tarball and repacked one stay identical.
cu andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#516585: RFH: alsa-lib
Package: wnpp Severity: normal Hi Debian ALSA developers, I want to prepare alsa-lib 1.0.19 for upload. Building alsa-lib on i386 and amd64 gives: ... checking for strip... strip checking for cross-compiler... i486-i486-pc-linux-gnu-gcc checking for i486-linux-gnu-gcc... i486-i486-pc-linux-gnu-gcc checking for C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details. make: *** [configure-biarch-stamp] Error 77 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 debuild: fatal error at line 1319: dpkg-buildpackage -rfakeroot -D -us -uc failed Command /bin/sh -c debuild "-rfakeroot" failed in , how to continue now? [Qri?]: q Aborting. The correct compiler should be: i486-linux-gnu-gcc and not i486-i486-pc-linux-gnu-gcc! From upstreams changelog: "Don't use AC_CANONICAL_SYSTEM, only use AC_CANONICAL_HOST" Hmmm. Building on ppc runs fine. Others I can't test. You can co the version I tried from svn (r 2165): svn://svn.debian.org/pkg-alsa/trunk/alsa-lib http://svn.debian.org/wsvn/pkg-alsa/trunk/alsa-lib/ The orig tgz must be loaded from: wget ftp://ftp.alsa-project.org/pub/lib/alsa-lib-1.0.19.tar.bz2 tar jxf alsa-lib-1.0.19.tar.bz2 tar zcf alsa-lib-1.0.19.tar.gz alsa-lib-1.0.19 mv alsa-lib-1.0.19.tar.gz alsa-lib_1.0.19.orig.tar.gz Any hints? Thanks for cooperation Elimar -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) -- Learned men are the cisterns of knowledge, not the fountainheads ;-) -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
