The rpms that are architechture independent have "noarch" somewhere in their names. Compilers are in charge of matching your source with the actual architecture you have, so you do not necessarilly have to learn architecture specific code, and you achieve high portability. But, some processes are better performed if you make routines in machine language and use the best capabilities of your hardware, and if you use them, then your programs become hardware dependent.
A good example is Linux itself. It exploits the characteristics of 32 bit processors, but it wont work in 8 or 16 bit processors. So Linux for INTEL is dependent on the processor family. Best regards, -Manuel. -----Original Message----- From: "Ismael Touama" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Date: Fri, 8 Mar 2002 11:47:06 +0100 Subject: SRPMS > Hi, in the flow! > OK I remark that we can download Source of RPMs. > There is just one for many architectures available. > Ok, don't know C language, so I suppose that it's the > compilation which provides all different version. > Is that correct ? > It means one source for differents architecture but I don't understand > why some architectures are affected and other not. > Which is the thing determine that ? one source for severals > architecture, > it's kind of weird to me. > > ism (loves weird) > > > > _______________________________________________ > Redhat-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
