dieman at ringworld.org
Sat Sep 30 22:54:22 BST 2006
My 'hack' involved compiling part of it on a 32 bit machine, and part of
it on a 64 bit machine. I was unable to compile the 32 bit required
parts on a 64 bit machine.
I think you could do 2 source packages and have the 2nd package targeted
at amd64 pull in the 32bit parts and make them part of the 64 bit
package much like ia32-libs. But thats not how I did it.
Ahmed El-Mahmoudy wrote:
> On Sat, Sep 23, 2006 at 11:18:38AM -0500, Scott Dier wrote:
>> I'm sorry I haven't emailed out about this but I had worked up a package
>> of my own last week (sorry, its been busy with school having started
>> this month) and it stopped working a bit and crashed firefox once or
>> twice within an hour. It worked *well* when it did work, but sometimes
>> it would just stop inserting itself as a plugin after showing a few
>> different flash sites. Also, it doesn't look like a flash plugin to
>> noscript, so that sort of sucks, too. :)
>> I'm guessing a few more months of development will make nspluginwrapper
>> usable if its being actively worked on, but I don't have the resources
>> during my workday to hack on it in the near future.
> Matt Zimmerman has suggested in the "How long will 64bit Ubuntu users
> have to wait?" thread that ndiswrapper would be uploaded to
> universe even though it is buggy. As I understand the reason is that so
> that more people would be involved in solving those problems.
> I suggest that you upload your package to REVU since mine fails to
> compile on amd64.
Scott Dier <dieman at ringworld.org>
More information about the ubuntu-devel