From owner-freebsd-questions Thu Sep 14 4:54:48 2000 Delivered-To: freebsd-questions@freebsd.org Received: from plab.ku.dk (plab.ku.dk [130.225.105.65]) by hub.freebsd.org (Postfix) with ESMTP id 8E13737B423 for ; Thu, 14 Sep 2000 04:54:46 -0700 (PDT) Received: from raven.plab.ku.dk (raven.plab.ku.dk [130.225.105.67]) by plab.ku.dk (8.11.0/8.9.3) with ESMTP id e8EBsju20863 for ; Thu, 14 Sep 2000 13:54:45 +0200 (CEST) (envelope-from postmaster@plab.ku.dk) In-Reply-To: Alex Popa's message of "Thu, 14 Sep 2000 09:44:26 +0300" Subject: netscape plugins? Content-Transfer-Encoding: 8bit To: freebsd-questions@FreeBSD.ORG From: Dmitry Karasik Content-Type: text/plain; charset="koi8-r" Lines: 26 Date: 14 Sep 2000 13:54:44 +0200 X-Mailer: Mail::Mailer[v1.18] Net::SMTP[v2.13] Message-Id: Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I tried to port netscape plugin for freebsd, but the netscape doesn't recognize it - I think that's because of the different executable formats. Since my netscape-navigator-4.-something was pre-compiled, I cannot find out what compiler and linker options were used for creating its own plugins. However, I found that some plugins are already available in the ports collection, but they are pre-compiled also. So my question is: does anybody know how to compile the damn thing correctly? Or, maybe, you know the right person to contact? One version is that everything compiled with a-out ( on 2.2.7 freebsd, for example), do not require some special options. But I'm using 4.1-stable, and my gcc seems incapable of compiling shared libraries in a-out format. I read somewhere in the docs that freebsd's future is to remove eventually a-out support from the kernel. Aren't these the first steps? If not, I would like to comment that it might be considered as a bug ( feature?) that crt0.o required for the creation of shared object is not present in the installation tree - and the 'make buildworld' doesn't make one. -- Sincerely, Dmitry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message