From owner-freebsd-stable@FreeBSD.ORG Tue Apr 16 02:41:42 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id BB1D654B for ; Tue, 16 Apr 2013 02:41:42 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8BD637AC for ; Tue, 16 Apr 2013 02:41:42 +0000 (UTC) Received: by mail-oa0-f54.google.com with SMTP id l20so25755oag.41 for ; Mon, 15 Apr 2013 19:41:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=VUQ6sVAfO0y0J90XeOPeL+dCG8qK4pkI+/QurHsjSKk=; b=EYKsXCy6duMFSZVShxvSFSHAx6lzZpz7PCwiTZdKBW1AXKEWcSv03XQe+gQqZc4U12 kPevxp5Cbk4vybiRRBoyNCasvJYCzpUsaL/IhoSU6DZiOKLaoGB66nc0RO2AVlka6740 Dtf9g8wBSFJd/OAapsx+TQ1YPV9eEru+GzB2PchLMbloxe+q0pbvdPjik6V4pyvb0H0D EsV2c+ZVAyTX9avNsYl5cqYaPlLLn0cArADMohawa8wYNSovRd2mYUzCdDifIcq+DSuF 4NM7wZQkg4b2TT1wv/C24Qn5y0Pq2+V/ASWOZaB+GZGD3uvvg7RFZ0/gHRZNU3NtAE/f WuCw== MIME-Version: 1.0 X-Received: by 10.182.39.201 with SMTP id r9mr152500obk.16.1366080096423; Mon, 15 Apr 2013 19:41:36 -0700 (PDT) Received: by 10.76.109.236 with HTTP; Mon, 15 Apr 2013 19:41:36 -0700 (PDT) In-Reply-To: <20130412142802.GA1657@regency.nsu.ru> References: <20130410052710.GA36137@regency.nsu.ru> <20130412101746.GA68687@regency.nsu.ru> <20130412142802.GA1657@regency.nsu.ru> Date: Mon, 15 Apr 2013 22:41:36 -0400 Message-ID: Subject: Re: fusefs-kmod does not work on 8-STABLE? From: Ryan Stone To: Alexey Dokuchaev Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Apr 2013 02:41:42 -0000 On Fri, Apr 12, 2013 at 10:28 AM, Alexey Dokuchaev wrote: > On Fri, Apr 12, 2013 at 05:17:46PM +0700, Alexey Dokuchaev wrote: > > On Wed, Apr 10, 2013 at 12:27:10PM +0700, Alexey Dokuchaev wrote: > > > I've got puzzled with the fact that fusefs-kmod apparently does not on > > > recent 8-STABLE: it builds and loads, but I don't see normal "fuse4bsd: > > > version 0.3.9-pre1, FUSE ABI 7.19" like I do on 9-STABLE (installed on > the > > > same laptop with almost identical kernel config). > > > > > > The result is that /dev/fuse0 never gets created, and any fuse mount > > > attempt results in this message: > > > > > > fuse: failed to open fuse device: No such file or directory > > > > I've traced the problem down a bit, it seems to be due to some weird > > brokenness of building modules outside the kernel: .ko file loads, but > > modevent() functions apparently does not execute at all. > > I've found the culprit: the problem is in this command of the build: > > ld -Bshareable -d -warn-common -o hello.ko.debug hello.kld > > I had put /usr/local/bin in my $PATH before /usr/bin for a reason I don't > currently recall, and have binutils-2.23.1 installed. As a result, ld(1) > in the quoted line above was called from /usr/local/bin/ld, which brought > in all the weird things I was observing: failure of fusefs-kmod, failure > of simple "hello world" KLD, "link_elf: symbol undefined" messages > when loading snd_hda(4) and nvidia(4) drivers. > > How, does anyone have a clue why new ld(1) plays so badly with our system > toolchain on 8.x (at least)? > > ./danfe > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > Is this for i386? When compiling modules with newer versions of ld I had to add the following flags to the ld invocation to get the module to work: -u __start_set_sysinit_set -u __start_set_sysuninit_set \ -u __start_set_sysctl_set -u __start_set_modmetadata_set \ -u __stop_set_sysinit_set -u __stop_set_sysuninit_set \ -u __stop_set_sysctl_set -u __stop_set_modmetadata_set