From: Andrew McGregor <andrew@indranet.co.nz>
To: Ferry van Steen <freaky@www.bananateam.nl>, linux-kernel@vger.kernel.org
Subject: Re: Partially closed source module, more of gcc/ld question.
Date: Thu, 16 Jan 2003 22:01:25 +1300 [thread overview]
Message-ID: <28230000.1042707685@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.33.0301160825140.6306-100000@www.bananateam.nl>
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/
>
>
prev parent reply other threads:[~2003-01-16 8:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=28230000.1042707685@localhost.localdomain \
--to=andrew@indranet.co.nz \
--cc=freaky@www.bananateam.nl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox