VectorLinux

Please login or register.

Login with username, password and session length
Advanced search  

News:

Visit our home page for VL info. For support and documentation, visit the Vector Linux Knowledge Center or search the Knowledge Center and this Forum using the search box above.

Author Topic: i486, i686 etc  (Read 1606 times)

joec

  • Member
  • *
  • Posts: 29
i486, i686 etc
« on: June 20, 2007, 12:29:29 pm »

what does  "i486" stand for?
Logged

M0E-lnx

  • Administrator
  • Vectorian
  • *****
  • Posts: 3217
Re: i486, i686 etc
« Reply #1 on: June 20, 2007, 12:40:14 pm »

That would be the system architecture

nightflier

  • Administrator
  • Vectorian
  • *****
  • Posts: 4085
Re: i486, i686 etc
« Reply #2 on: June 20, 2007, 01:54:01 pm »

Suspect the "i" is for Intel (or compatible, like AMD), 486 = 80486, 586 = Pentium 1, 686 = Pentium II or higher.
Logged

joec

  • Member
  • *
  • Posts: 29
Re: i486, i686 etc
« Reply #3 on: June 20, 2007, 03:10:22 pm »

so in looking for packages it is important to match this # in the package to whatever cgip you might have?
Logged

The Headacher

  • Louder than you
  • Global Moderator
  • Vectorian
  • *****
  • Posts: 1553
  • I like the bass to go BOOM!
    • Multimedia on VL (work in progress)
Re: i486, i686 etc
« Reply #4 on: June 20, 2007, 03:40:36 pm »

Vector packages are usually built with the "CFLAGS" -march=i586 -mtune=i686 (and -O2 but that doesn't really matter now) : This means the compiler must make code that is compatible with i586 processors, but tuned for use on i686 machines.

Quote
in looking for packages it is important to match this # in the package to whatever cgip you might have?
Generally a package with either i386, i486, i586 and i686 should work on VL. For optimization an i686 package MIGHT perform slightly better. You'll get in trouble when you try to use packages that were built for powerpc or 64 bit systems, but you won't find such packages in either the slackware or the VL repositories.
Logged
Most music on my soundcloud page was arranged in programs running on VL.