Your message dated Wed, 7 Sep 2005 12:30:19 -0400
with message-id <[EMAIL PROTECTED]>
and subject line changes in build environment causing problems
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 31 Jul 2005 01:23:43 +0000
>From [EMAIL PROTECTED] Sat Jul 30 18:23:43 2005
Return-path: <[EMAIL PROTECTED]>
Received: from c-24-10-6-146.hsd1.ca.comcast.net (nofear.bounceme.net)
[24.10.6.146]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1Dz2YJ-0003Bt-00; Sat, 30 Jul 2005 18:23:43 -0700
Received: from [10.1.1.66] (hades [10.1.1.66])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client did not present a certificate)
by nofear.bounceme.net (Postfix) with ESMTP id 8A5F27356D
for <[EMAIL PROTECTED]>; Sat, 30 Jul 2005 18:23:08 -0700 (PDT)
Message-ID: <[EMAIL PROTECTED]>
Date: Sat, 30 Jul 2005 18:24:15 -0700
From: "C.Y.M" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Organization: CooLNeT
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Submit Debian Bugs <[EMAIL PROTECTED]>
Subject: changes in build environment causing problems
X-Enigmail-Version: 0.92.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: tvtime
Version: 0.9.15-1
Since the change of the build environment over to gcc-4.0 in Sid, something has
happened to the build environment for *all* of the compilers (including gcc-3.3
and gcc-3.4). At the beginning the the debian/rules in the tvtime source
package, there are these lines which get DEB_HOST_GUN_TYPE and
DEB_BUILD_GNU_TYPE:
--SNIP--
DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
--SNIP--
When I manually run these commands I get this value for both in return:
i486-linux-gnu
So, when tvtime is built, it appears the rules are trying to optimize for an
i486 (even though my machine in an athon XP2100+ or i686):
--SNIP--
checking whether we are using the GNU C compiler... yes
checking whether i486-linux-gnu-gcc accepts -g... yes
checking for i486-linux-gnu-gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of i486-linux-gnu-gcc... gcc3
checking for i486-linux-gnu-gcc... yes
checking for i486-linux-gnu-g++... i486-linux-gnu-g++
checking whether we are using the GNU C++ compiler... yes
checking whether i486-linux-gnu-g++ accepts -g... yes
checking dependency style of i486-linux-gnu-g++... gcc3
checking for i486-linux-gnu-g++... yes
--SNIP--
This causes the build to fail using gcc-3.3 and gcc-3.4 (I have not tried
gcc-4.0). But, the point is that previous to debians compiler upgrades,
DEB_BUILD_GNU_TYPE and DEB_HOST_GNU_TYPE returned i386 *not* i486.
--SNIP--
`-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead.
if i486-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -MT greedyh.o -MD
-MP -MF ".deps/greedyh.Tpo" \
-c -o greedyh.o `test -f '../plugins/greedyh.cpp' || echo
'./'`../plugins/greedyh.cpp; \
then mv -f ".deps/greedyh.Tpo" ".deps/greedyh.Po"; \
else rm -f ".deps/greedyh.Tpo"; exit 1; \
fi
../plugins/greedyh.asm: In function 'void
greedyh_filter_mmx(TDeinterlaceInfo*)':
../plugins/greedyh.asm:270: error: unknown register name 'mm7' in 'asm'
../plugins/greedyh.asm:270: error: unknown register name 'mm6' in 'asm'
../plugins/greedyh.asm:270: error: unknown register name 'mm5' in 'asm'
../plugins/greedyh.asm:270: error: unknown register name 'mm4' in 'asm'
../plugins/greedyh.asm:270: error: unknown register name 'mm3' in 'asm'
../plugins/greedyh.asm:270: error: unknown register name 'mm2' in 'asm'
../plugins/greedyh.asm:270: error: unknown register name 'mm1' in 'asm'
../plugins/greedyh.asm:270: error: unknown register name 'mm0' in 'asm'
make[3]: *** [greedyh.o] Error 1
--SNIP--
It appears that tvtime will not build if it is optimized to i486. If I remove
these two lines in the rules file, then tvtime builds fine optimized towards
i686 (which i what .configure detects):
--SNIP--
./configure --host=$(DEB_HOST_GNU_TYPE) \
--build=$(DEB_BUILD_GNU_TYPE) \
--SNIP--
So, my question is why doesnt DEB_BUILD_GNU_TYPE and DEB_HOST_GNU_TYPE return
i686 in the first place? Or, why do we hardcode the build types in our debian
rules when autoconf should do this for us?
Best Regards,
C.
Note: This is also the same issue with MjpegTools.
---------------------------------------
Received: (at 320644-close) by bugs.debian.org; 7 Sep 2005 16:30:54 +0000
>From [EMAIL PROTECTED] Wed Sep 07 09:30:54 2005
Return-path: <[EMAIL PROTECTED]>
Received: from smtp102.rog.mail.re2.yahoo.com [206.190.36.80]
by spohr.debian.org with smtp (Exim 3.36 1 (Debian))
id 1ED2p4-0006I1-00; Wed, 07 Sep 2005 09:30:54 -0700
Received: (qmail 16885 invoked from network); 7 Sep 2005 16:30:23 -0000
Received: from unknown (HELO alps.law.yi.org) ([EMAIL PROTECTED] with login)
by smtp102.rog.mail.re2.yahoo.com with SMTP; 7 Sep 2005 16:30:23 -0000
Received: from sfllaw by alps.law.yi.org with local (Exim 3.36 #1 (Debian))
id 1ED2oW-0001BY-00
for <[EMAIL PROTECTED]>; Wed, 07 Sep 2005 12:30:20 -0400
Date: Wed, 7 Sep 2005 12:30:19 -0400
From: Simon Law <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: changes in build environment causing problems
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.9i
Sender: Simon Law <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
"C.Y.M" <[EMAIL PROTECTED]> wrote:
> So, my question is why doesnt DEB_BUILD_GNU_TYPE and DEB_HOST_GNU_TYPE
> return i686 in the first place? Or, why do we hardcode the build types
> in our debian rules when autoconf should do this for us?
The reason we do this is because Debian is built to support 486 machines
and higher. If we compiled tvtime for whatever the build machine was,
this would not be completely useful users with less capable machines.
You can always set DEB_BUILD_GNU_TYPE and DEB_HOST_GNU_TYPE explicitly
when building Debian packages. You might consider wrapping debuild so
it does this for you.
--
Simon Law http://www.law.yi.org/~sfllaw/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
