public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Partially closed source module, more of gcc/ld question.
@ 2003-01-16  7:29 Ferry van Steen
  2003-01-16  9:01 ` Andrew McGregor
  0 siblings, 1 reply; 2+ messages in thread
From: Ferry van Steen @ 2003-01-16  7:29 UTC (permalink / raw)
  To: linux-kernel

Hey there,

some of you might have read my message on the promise fasttrak last time.
I'm sorry to say that I started yelling to them through e-mail and the
replied now! This is the so manied company that suddenly replies if you
yell... Oh well, they released some new module, which I want to try later
on.

Sortta like nvidia, you get a Makefile, some others an object and 3 C
files. Now for the question. Loading a gcc v2 compiled module into a v3
compiled kernel causes problems. Is it correct to assume then that if the
object were compiled with v2, and the C files with v3 and those get linked
together into a module, that you might experience the same problems?

Is there any way I can see with which version the object was compiled
(the kernel seems to be able to, or atleast, partially it doesn't give
specific version just v2 or v3)?

Kind regards



^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Partially closed source module, more of gcc/ld question.
  2003-01-16  7:29 Partially closed source module, more of gcc/ld question Ferry van Steen
@ 2003-01-16  9:01 ` Andrew McGregor
  0 siblings, 0 replies; 2+ messages in thread
From: Andrew McGregor @ 2003-01-16  9:01 UTC (permalink / raw)
  To: Ferry van Steen, linux-kernel

Check out the patches for the NVIDIA driver on www.minion.de, there's a 
linker hack in the most recent patch which fixes this.

Andrew

--On Thursday, January 16, 2003 08:29:31 +0100 Ferry van Steen 
<freaky@www.bananateam.nl> wrote:

> Hey there,
>
> some of you might have read my message on the promise fasttrak last time.
> I'm sorry to say that I started yelling to them through e-mail and the
> replied now! This is the so manied company that suddenly replies if you
> yell... Oh well, they released some new module, which I want to try later
> on.
>
> Sortta like nvidia, you get a Makefile, some others an object and 3 C
> files. Now for the question. Loading a gcc v2 compiled module into a v3
> compiled kernel causes problems. Is it correct to assume then that if the
> object were compiled with v2, and the C files with v3 and those get linked
> together into a module, that you might experience the same problems?
>
> Is there any way I can see with which version the object was compiled
> (the kernel seems to be able to, or atleast, partially it doesn't give
> specific version just v2 or v3)?
>
> Kind regards
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
>



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2003-01-16  8:57 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-01-16  7:29 Partially closed source module, more of gcc/ld question Ferry van Steen
2003-01-16  9:01 ` Andrew McGregor

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox