From: Paul E Condon on
I'm in the process of working a bug on my desktop PC. The CPU is a
Semperon (32bit AMD). I recall that I once used i686. But now I think
I am using i386. When I make a bug report, reportbug includes the
line:
"Architecture: i386 (i686)"

I guess that i686 has somehow been merged into i386, but I cannot
confirm this guess by googling. I only get old discussion, nothing
announcing a resolution to the discussion. I'm sure there is an
announcement somewhere that explains how the issue was resolved
and why everyone should be happy. I'd like to read it and be happy.
But I can't find it.

Please help.

--
Paul E Condon
pecondon(a)mesanetworks.net


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/20100611164216.GA13257(a)big.lan.gnu
From: Jordan Metzmeier on
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 06/11/2010 12:42 PM, Paul E Condon wrote:
> I'm in the process of working a bug on my desktop PC. The CPU is a
> Semperon (32bit AMD). I recall that I once used i686. But now I think
> I am using i386. When I make a bug report, reportbug includes the
> line:
> "Architecture: i386 (i686)"
>
> I guess that i686 has somehow been merged into i386, but I cannot
> confirm this guess by googling. I only get old discussion, nothing
> announcing a resolution to the discussion. I'm sure there is an
> announcement somewhere that explains how the issue was resolved
> and why everyone should be happy. I'd like to read it and be happy.
> But I can't find it.
>
> Please help.
>

My guess would be i386 arch with the i686 (default) kernel. However, it
is just a guess and you are looking for solid evidence.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iQIcBAEBCAAGBQJMEmlLAAoJEKj/C3qNthmTX80P/0GZ/NgdEB/mytmWfHn250ou
BgnyFeXsxl0nAKdnoQQGxd/hQWj0Er0BMLxDLhrkRGmLH9P935WAZo1XH4IIrZA/
yLg9km6hIsUAT6AfNR50TOxafZqRdHQ587+UoV8sJRleVvMxhuUV9UJuon+hsSvJ
8BBa2jHT+ewYmOfczXY5po+JcLFLu9v13Jq4N0Tq5gjbrVkKCfzDsJlkBkntdM5G
dpx8s4BfrKiWlARj4+L2pbvszHUHLhDyxDZeGF3A9IE0qXqAb/7IFz09MLMbITok
Ej19TGfaWqZeVkMc0zVPBE0kG4eE7G9lWUCvDP6uv5s1kgsN8tVkF5ovpEvTDS5V
VtCDda+1w8Nb6bhD4PAbhOhDhA4A3ux1KXRjCHEuX7KzE0fmA0kOriXuzl8K5G8I
0rs1/akouS5UN6hpXyek+lucy8gsGlg4waY7yPXQv/jiHB0kO42mTWyKFxESr+qB
iVSwQi7Ydpqr/VebOkLE7jRNWzlDpCU34+RAreLudUknB1IiRgj6sHpm1eRc6Hjb
/Gh4I9cnsw+4QmukTDtu5Un+zYnLgA37nejnySW9cmXm428KAn2HRjyEG2LGG12K
4Qnrx+mdcEyaepml+fM82kzLr072PJfaQEghLk8WYEuT90FYiuXPFc/Z+PwXpHCc
0xVRmnG72LjgMx3A120q
=E8Tl
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4C12694C.6020404(a)gmail.com
From: Sven Joachim on
On 2010-06-11 18:42 +0200, Paul E Condon wrote:

> I'm in the process of working a bug on my desktop PC. The CPU is a
> Semperon (32bit AMD). I recall that I once used i686. But now I think
> I am using i386.

No, you always used the Debian architecture i386. The kernel may be
built for a 686-compatible processor, though.

> When I make a bug report, reportbug includes the line:
> "Architecture: i386 (i686)"
>
> I guess that i686 has somehow been merged into i386, but I cannot
> confirm this guess by googling.

This is wrong. The first string is the output from
"dpkg --print-architecture", the one in parentheses comes from
"uname -m".

Sven


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/87hbl9v774.fsf(a)turtle.gmx.de
From: Aaron Toponce on
On 6/11/2010 11:03 AM, Boyd Stephen Smith Jr. wrote:
> I'm not exactly sure what the policy is for packages in the i386 archives in
> general, but I believe they are supposed to have -586 or -686 in their package
> name is they require those instruction sets. Some of the A/V codec libraries
> had stuff like that for a while, IIRC. I believe currently they auto-probe
> for the processor features and use what is available at runtime.

Other than the kernel, which is compiled for 686 instruction sets, and
maybe a few core packages that would benefit from targeting the 686
architecture, Debian compiles the rest of the packages against 386.

--
. O . O . O . . O O . . . O .
. . O . O O O . O . O O . . O
O O O . O . . O O O O . O O O

From: Boyd Stephen Smith Jr. on
On Friday 11 June 2010 11:42:16 Paul E Condon wrote:
> I'm in the process of working a bug on my desktop PC. The CPU is a
> Semperon (32bit AMD). I recall that I once used i686. But now I think
> I am using i386. When I make a bug report, reportbug includes the
> line:
> "Architecture: i386 (i686)"
>
> I guess that i686 has somehow been merged into i386,

They were never entirely separate architectures. The i486, i586, and i686
instruction sets were strict supersets of the i386 instruction set.

Mostly likely this line is reporting your dpkg architecture and your kernel
architecture. The dpkg architecture is still called i386, but I believe the
libc requires the i486 instruction set, and there is no pre-compiled kernel
image that does not require at least the i486 instruction set.

I think all the 32-bit processors on the market right now are i686 or better,
but there might be some i586 embedded processors on the market still. Debian
provides a pre-compiled kernel images that depends on the i686 architecture,
and can therefore take advantage of the extra (faster) instructions in i686
processors.

I'm not exactly sure what the policy is for packages in the i386 archives in
general, but I believe they are supposed to have -586 or -686 in their package
name is they require those instruction sets. Some of the A/V codec libraries
had stuff like that for a while, IIRC. I believe currently they auto-probe
for the processor features and use what is available at runtime.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
bss(a)iguanasuicide.net ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/ \_/