Dave,

Can I please ask you a question?  It is about GCC.  Let me know either on or off the 
list.
It is up to you.

Steven

*********** REPLY SEPARATOR  ***********

On 12/14/2000 at 21:53 Dave Reed wrote:

>> Date: Thu, 14 Dec 2000 20:11:41 -0600 (CST)
>> From: David Talkington <[EMAIL PROTECTED]>
>> Hello all --
>> 
>> Please let me qualify the following by saying that a) I'm not
>> C-literate, and b) I'll be perfectly happy with links to FAQs, or a
>> more appropriate forum to which to direct these questions.
>> 
>> If I wish to compile a binary on a fast machine and transfer this
>> binary to another box of lesser architecture and an older Linux
>> kernel, what steps are required?  (I'm restricting my scope to Intel
>> processors here.)  For instance, if I build ssh on an i686 with
>> 2.2.17, and want to run this binary on an i486 with 2.2.14, what must
>> I do?  'man gcc' suggests that the -b option is relevant, but it also
>> says "This is useful when you have installed GNU CC as a
>> cross-compiler", suggesting that there is some other configuration to
>> be done to gcc before I should try that ... and that doesn't address
>> the issue of kernel version.
>> 
>> Similarly, if I'm compiling someone else's source on the
>> aforementioned i686 and I want the binary to be optimized for that
>> processor, need I do anything special?  The man page says this about
>> the -b switch:  "When you do not specify `-b', it normally means to
>> compile for the same type of machine that you are using."  However, it
>> has been suggested to me that some extra flags to gcc in the makefile
>> may be required to make this explicit. I'd like some general guidance
>> on this before I start mucking about.
>> 
>> Thank you for any suggestions.
>
>A cross-compiler is for entirely different architectures (like
>compiling a i386 binary using a SPARC machine).  You're just looking
>at different variations of i386.  Unless you are invoking gcc with
>various -m options, the code should run on any Intel chip. 
>
>If you want to learn how to optimize for a specific architecture
>(which will prevent it from running on an earlier architecture), try:
>info gcc (or use emacs) and follow the links:
>
>invoking gcc, submodel options, i386 options.
>
>HTH,
>Dave
>
>
>
>_______________________________________________
>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

Reply via email to