Messages in this thread | | | Date | Mon, 20 Sep 1999 18:31:11 +0300 | From | Matti Aarnio <> | Subject | Re: Possible GCC contamination of Linux |
| |
On Mon, Sep 20, 1999 at 11:07:32AM -0400, Richard B. Johnson wrote: > On Mon, 20 Sep 1999, David S. Miller wrote: > > > Date: Mon, 20 Sep 1999 10:45:05 -0400 (EDT) > > From: "Richard B. Johnson" <root@chaos.analogic.com> > > > > So, is there the possibility that something from the gcc library > > gets linked into the kernel? If so, how would I prevent it from > > happening? > > > > Yes, parts of libgcc.a are necessary for certain types "long long" > > arithmetic at the very least.
Said library is *not* (per standard sources) linked with the kernel. (At L-F-S work I am happy that it is *not* linked in per default.)
> > Later, > > David S. Miller > > davem@redhat.com > > > > Bingo! Do you know of any way to fix this? I only have one '486 machine > and it's way too slow to use for development. The target embeded machine > is a '486.
That theory works only if you use non-standard image linking.
A comparison of produced binary object files when compiled at the i686 vs. at the i486 would be most educative.
Which change, and in which manner. I presume the configuration is identical in both cases ? What does command egrep CONFIG_X86 .config tell ?
> Cheers, > Dick Johnson
/Matti Aarnio <matti.aarnio@sonera.fi>
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |