Hi,
the current set of gcc in sid/i386 is OK (-march=i486 -mtune=i686).
gcc-3.3 3.3.6-12
gcc-3.4 3.4.5-2
gcc-4.0 4.0.2-7
Only experimental gcc-4.1 4.1-0exp6 have to re-enable
cpu-default-i486.dpatch
On the other hand, the (now tested) results
for gcc -m32 on amd64 are a little bit different:
Petr Salinger writes:
Hi,
the current set of gcc in sid/i386 is OK (-march=i486 -mtune=i686).
gcc-3.3 3.3.6-12
gcc-3.4 3.4.5-2
gcc-4.0 4.0.2-7
Only experimental gcc-4.1 4.1-0exp6 have to re-enable
cpu-default-i486.dpatch
yes, pending for the next upload.
it's currently not possible
Only experimental gcc-4.1 4.1-0exp6 have to re-enable
cpu-default-i486.dpatch
yes, pending for the next upload.
it's currently not possible to configure using --with-arch=i486 and
having the compiler be built as biarch. see the cpu-default-i486 patch
in the source package.
Yes, I saw
On Thu, Jan 19, 2006 at 05:41:52PM +, Martin Michlmayr wrote:
* Sjoerd Simons [EMAIL PROTECTED] [2006-01-19 18:13]:
There are various ways to work around this problem, but i would like to know
what the real cause is there? Is avahi using the -pthreads flag wrong or is
gcc not hanlding
--- Comment #4 from ayers at gcc dot gnu dot org 2006-01-24 21:57 ---
Subject: Bug 13946
Author: ayers
Date: Tue Jan 24 21:57:22 2006
New Revision: 110182
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=110182
Log:
2006-01-24 David Ayers [EMAIL PROTECTED]
PR
--- Comment #5 from ayers at gcc dot gnu dot org 2006-01-24 22:00 ---
Subject: Bug 13946
Author: ayers
Date: Tue Jan 24 22:00:26 2006
New Revision: 110183
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=110183
Log:
2006-01-24 David Ayers [EMAIL PROTECTED]
PR
6 matches
Mail list logo
