| Message ID | 20210105142057.5067-1-ahb.ipfire@gmail.com |
|---|---|
| State | Accepted |
| Commit | 02037c964fade3d58b0e4d9a05d3034955e8f5bc |
| Headers |
Return-Path: <development-bounces@lists.ipfire.org> Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by web04.haj.ipfire.org (Postfix) with ESMTPS id 4D9F6Q1YBgz3wgM for <patchwork@web04.haj.ipfire.org>; Tue, 5 Jan 2021 14:21:18 +0000 (UTC) Received: from mail02.haj.ipfire.org (mail02.haj.ipfire.org [172.28.1.201]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384 client-signature ECDSA (P-384) client-digest SHA384) (Client CN "mail02.haj.ipfire.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mail01.ipfire.org (Postfix) with ESMTPS id 4D9F6P0jJlzwv; Tue, 5 Jan 2021 14:21:17 +0000 (UTC) Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4D9F6N6yDWz2xnh; Tue, 5 Jan 2021 14:21:16 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4D9F6N452Zz2xX3 for <development@lists.ipfire.org>; Tue, 5 Jan 2021 14:21:16 +0000 (UTC) Received: from smtpq3.tb.mail.iss.as9143.net (smtpq3.tb.mail.iss.as9143.net [212.54.42.166]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail01.ipfire.org (Postfix) with ESMTPS id 4D9F6K2RMvzvr for <development@lists.ipfire.org>; Tue, 5 Jan 2021 14:21:13 +0000 (UTC) Received: from [212.54.42.137] (helo=smtp6.tb.mail.iss.as9143.net) by smtpq3.tb.mail.iss.as9143.net with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <ahb.ipfire@gmail.com>) id 1kwnCy-0008Lw-Jq; Tue, 05 Jan 2021 15:21:12 +0100 Received: from j103033.upc-j.chello.nl ([24.132.103.33] helo=rhea.saturn.pimb.org) by smtp6.tb.mail.iss.as9143.net with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <ahb.ipfire@gmail.com>) id 1kwnCx-008Vs8-OE; Tue, 05 Jan 2021 15:21:11 +0100 Received: from hyperion.saturn.pimb.org (hyperion.saturn.pimb.org [192.168.26.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by rhea.saturn.pimb.org (Postfix) with ESMTPSA id E08853EF3; Tue, 5 Jan 2021 15:21:10 +0100 (CET) From: Adolf Belka <ahb.ipfire@gmail.com> To: development@lists.ipfire.org Subject: [PATCH 1/2] sshfs: Update to 3.7.1 Date: Tue, 5 Jan 2021 15:20:57 +0100 Message-Id: <20210105142057.5067-1-ahb.ipfire@gmail.com> X-Mailer: git-send-email 2.30.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SourceIP: 24.132.103.33 X-Authenticated-Sender: adolf.belka@ziggo.nl (via SMTP) X-Ziggo-spambar: / X-Ziggo-spamscore: 0.0 X-Ziggo-spamreport: CMAE Analysis: v=2.4 cv=TcEoCTch c=1 sm=1 tr=0 ts=5ff475d7 a=N0UC3/faf55XGTeY5t7zSQ==:17 a=9+rZDBEiDlHhcck0kWbJtElFXBc=:19 a=EmqxpYm9HcoA:10 a=x7bEGLp0ZPQA:10 a=6yxbeI8x3IIA:10 a=RtR1fWGTAAAA:20 a=pGLkceISAAAA:8 a=1LR1zZV67QIzfe_T6FUA:9 X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=lists.ipfire.org; s=202003rsa; t=1609856473; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=q+lD/p9wmHrVDtoedJOgfNla0Hf0SwQc9CKeyI0hpGg=; b=fNeN/5/FwQ9i5PCcI0t5IcIrFM+uREZFRpSfczctdNcT0Yp0+wHyFKj5cUsvj02dxLY+iZ WyMLc8823sQDp/uzu3LcHmXekF3CAiIi6hocOY8vxBe3VlfSePsJHGhGUpYxxYmPuQnjri p6qVHJ5oao0UjlucwwdJrf2xy7Sot/7PDLqedXpxN3PL3CBl8YOuxF++d0pjHxL2BCcUB/ 8kUZ2yuMkjYmRqiZ3m+/xo5TaX/fr/k4KJEMdOQTgHchG28iDOJJJ8noIJKOCz7r1Ba7w9 PDDAoNpWYcNQ2bDFKaxmvol6ld5S+8wHoCUiTiuwCIUbDvpS6YtfiLKRsONtww== ARC-Authentication-Results: i=1; mail01.ipfire.org; dkim=none; spf=softfail (mail01.ipfire.org: 212.54.42.166 is neither permitted nor denied by domain of ahbipfire@gmail.com) smtp.mailfrom=ahbipfire@gmail.com ARC-Seal: i=1; s=202003rsa; d=lists.ipfire.org; t=1609856473; a=rsa-sha256; cv=none; b=RXjzzUdC+UDBe4HMsLEvzNdfAwHWdZRZiXY5wNxgibRsz9q/5/xl/2bh4vxmONaJtOILEw B6Me3MOM8wSKz4HEVjT/SI7TgcJESIpc0GcyXLCTQx09xKQa6lOOUfVfcg//gN8JO/8Qto wYgI7c0Txlq1b3CdqwvdRBM+GeP8drCAQxt3+d4pm3ajPl+xcymK73mpyjUpruvwjeW7eq D4T0EE5qr41GBhXMxid6QVJdW4MbB4wAa1IaKpkUyG8iV/WGHr/8ZbXtCFFuNtiBswW4oa P6Lt65EaEp4dkSa8rK1n86NspvVxFK4HEXpX/LAGwgDXOsxn6est+dy+eiu4DA== Authentication-Results: mail01.ipfire.org; dkim=none; spf=softfail (mail01.ipfire.org: 212.54.42.166 is neither permitted nor denied by domain of ahbipfire@gmail.com) smtp.mailfrom=ahbipfire@gmail.com; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=gmail.com (policy=none) X-Rspamd-Server: mail01.haj.ipfire.org X-Spamd-Result: default: False [-1.94 / 11.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_MISSING_CHARSET(2.50)[]; RWL_MAILSPIKE_GOOD(0.00)[212.54.42.166:from]; IP_REPUTATION_HAM(-1.84)[asn: 33915(-0.26), country: NL(-0.00), ip: 212.54.42.166(-0.65)]; BROKEN_CONTENT_TYPE(1.50)[]; R_SPF_SOFTFAIL(0.00)[~all]; ARC_SIGNED(0.00)[lists.ipfire.org:s=202003rsa:i=1]; RCVD_COUNT_THREE(0.00)[4]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:33915, ipnet:212.54.32.0/20, country:NL]; TAGGED_FROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; HAS_X_AS(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[212.54.42.166:from]; FROM_HAS_DN(0.00)[]; BAYES_HAM(-3.00)[99.99%]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; RECEIVED_SPAMHAUS_PBL(0.00)[24.132.103.33:received]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM(-1.00)[-1.000]; FREEMAIL_CC(0.00)[gmail.com]; RCVD_TLS_ALL(0.00)[]; DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none] X-Rspamd-Queue-Id: 4D9F6K2RMvzvr X-BeenThere: development@lists.ipfire.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IPFire development talk <development.lists.ipfire.org> List-Unsubscribe: <https://lists.ipfire.org/mailman/options/development>, <mailto:development-request@lists.ipfire.org?subject=unsubscribe> List-Archive: <http://lists.ipfire.org/pipermail/development/> List-Post: <mailto:development@lists.ipfire.org> List-Help: <mailto:development-request@lists.ipfire.org?subject=help> List-Subscribe: <https://lists.ipfire.org/mailman/listinfo/development>, <mailto:development-request@lists.ipfire.org?subject=subscribe> Errors-To: development-bounces@lists.ipfire.org Sender: "Development" <development-bounces@lists.ipfire.org> |
| Series |
[1/2] sshfs: Update to 3.7.1
|
|
Commit Message
Adolf Belka
Jan. 5, 2021, 2:20 p.m. UTC
- Update sshfs from 2.2 to 3.7.1
- Changelog is available at https://github.com/libfuse/sshfs/releases
- Build had to be changed from autotools to meson/ninja
- Change in rootfiles
Signed-off-by: Adolf Belka <ahb.ipfire@gmail.com>
---
config/rootfiles/common/sshfs | 2 ++
lfs/sshfs | 14 ++++++--------
2 files changed, 8 insertions(+), 8 deletions(-)
Comments
Dear all, Forgot to mention in the logs that I have also installed the built IPFire with new fuse and sshfs into my testbed system and was able to setup an sshfs mount from a remote computer into the IPFire system, so confirmed working. The only thing I had to do was run modprobe fuse as the fuse module was not loaded. Is that normal to need to do or did I miss something when I was building sshfs/fuse Regards, Adolf. On 05/01/2021 15:20, Adolf Belka wrote: > - Update sshfs from 2.2 to 3.7.1 > - Changelog is available at https://github.com/libfuse/sshfs/releases > - Build had to be changed from autotools to meson/ninja > - Change in rootfiles > > Signed-off-by: Adolf Belka <ahb.ipfire@gmail.com> > --- > config/rootfiles/common/sshfs | 2 ++ > lfs/sshfs | 14 ++++++-------- > 2 files changed, 8 insertions(+), 8 deletions(-) > > diff --git a/config/rootfiles/common/sshfs b/config/rootfiles/common/sshfs > index 2cafa3e24..579b938f5 100644 > --- a/config/rootfiles/common/sshfs > +++ b/config/rootfiles/common/sshfs > @@ -1,2 +1,4 @@ > usr/bin/sshfs > +#usr/sbin/mount.fuse.sshfs > +#usr/sbin/mount.sshfs > #usr/share/man/man1/sshfs.1 > diff --git a/lfs/sshfs b/lfs/sshfs > index 23fbd18ca..1e7706194 100644 > --- a/lfs/sshfs > +++ b/lfs/sshfs > @@ -24,10 +24,10 @@ > > include Config > > -VER = 2.2 > +VER = 3.7.1 > > -THISAPP = sshfs-fuse-$(VER) > -DL_FILE = $(THISAPP).tar.gz > +THISAPP = sshfs-$(VER) > +DL_FILE = $(THISAPP).tar.xz > DL_FROM = $(URL_IPFIRE) > DIR_APP = $(DIR_SRC)/$(THISAPP) > TARGET = $(DIR_INFO)/$(THISAPP) > @@ -40,7 +40,7 @@ objects = $(DL_FILE) > > $(DL_FILE) = $(DL_FROM)/$(DL_FILE) > > -$(DL_FILE)_MD5 = 26e9206eb5169e87e6f95f54bc005a4f > +$(DL_FILE)_MD5 = 22ac23d05ca7c56fb568627f086374d0 > > install : $(TARGET) > > @@ -72,9 +72,7 @@ $(subst %,%_MD5,$(objects)) : > > $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects)) > @$(PREBUILD) > - @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE) > - cd $(DIR_APP) && ./configure --prefix=/usr > - cd $(DIR_APP) && make $(MAKETUNING) > - cd $(DIR_APP) && make install > + @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE) > + cd $(DIR_APP) && meson --prefix=/usr builddir && cd builddir && ninja && ninja install > @rm -rf $(DIR_APP) > @$(POSTBUILD) >
Hi, > On 5 Jan 2021, at 14:20, Adolf Belka <ahb.ipfire@gmail.com> wrote: > > - Update sshfs from 2.2 to 3.7.1 > - Changelog is available at https://github.com/libfuse/sshfs/releases > - Build had to be changed from autotools to meson/ninja > - Change in rootfiles > > Signed-off-by: Adolf Belka <ahb.ipfire@gmail.com> > --- > config/rootfiles/common/sshfs | 2 ++ > lfs/sshfs | 14 ++++++-------- > 2 files changed, 8 insertions(+), 8 deletions(-) > > diff --git a/config/rootfiles/common/sshfs b/config/rootfiles/common/sshfs > index 2cafa3e24..579b938f5 100644 > --- a/config/rootfiles/common/sshfs > +++ b/config/rootfiles/common/sshfs > @@ -1,2 +1,4 @@ > usr/bin/sshfs > +#usr/sbin/mount.fuse.sshfs > +#usr/sbin/mount.sshfs > #usr/share/man/man1/sshfs.1 > diff --git a/lfs/sshfs b/lfs/sshfs > index 23fbd18ca..1e7706194 100644 > --- a/lfs/sshfs > +++ b/lfs/sshfs > @@ -24,10 +24,10 @@ > > include Config > > -VER = 2.2 > +VER = 3.7.1 > > -THISAPP = sshfs-fuse-$(VER) > -DL_FILE = $(THISAPP).tar.gz > +THISAPP = sshfs-$(VER) > +DL_FILE = $(THISAPP).tar.xz > DL_FROM = $(URL_IPFIRE) > DIR_APP = $(DIR_SRC)/$(THISAPP) > TARGET = $(DIR_INFO)/$(THISAPP) > @@ -40,7 +40,7 @@ objects = $(DL_FILE) > > $(DL_FILE) = $(DL_FROM)/$(DL_FILE) > > -$(DL_FILE)_MD5 = 26e9206eb5169e87e6f95f54bc005a4f > +$(DL_FILE)_MD5 = 22ac23d05ca7c56fb568627f086374d0 > > install : $(TARGET) > > @@ -72,9 +72,7 @@ $(subst %,%_MD5,$(objects)) : > > $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects)) > @$(PREBUILD) > - @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE) > - cd $(DIR_APP) && ./configure --prefix=/usr > - cd $(DIR_APP) && make $(MAKETUNING) > - cd $(DIR_APP) && make install > + @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE) > + cd $(DIR_APP) && meson --prefix=/usr builddir && cd builddir && ninja && ninja install You could have written those into separate lines instead of all in one. That would have been slightly easier to read and change. > @rm -rf $(DIR_APP) > @$(POSTBUILD) > -- > 2.30.0 >
Hi, > On 5 Jan 2021, at 14:28, Adolf Belka <ahb.ipfire@gmail.com> wrote: > > Dear all, > > Forgot to mention in the logs that I have also installed the built IPFire with new fuse and sshfs into my testbed system and was able to setup an sshfs mount from a remote computer into the IPFire system, so confirmed working. > > The only thing I had to do was run modprobe fuse as the fuse module was not loaded. Is that normal to need to do or did I miss something when I was building sshfs/fuse I would expect that sshfs is doing that automatically. > Regards, > Adolf. > > On 05/01/2021 15:20, Adolf Belka wrote: >> - Update sshfs from 2.2 to 3.7.1 >> - Changelog is available at https://github.com/libfuse/sshfs/releases >> - Build had to be changed from autotools to meson/ninja >> - Change in rootfiles >> Signed-off-by: Adolf Belka <ahb.ipfire@gmail.com> >> --- >> config/rootfiles/common/sshfs | 2 ++ >> lfs/sshfs | 14 ++++++-------- >> 2 files changed, 8 insertions(+), 8 deletions(-) >> diff --git a/config/rootfiles/common/sshfs b/config/rootfiles/common/sshfs >> index 2cafa3e24..579b938f5 100644 >> --- a/config/rootfiles/common/sshfs >> +++ b/config/rootfiles/common/sshfs >> @@ -1,2 +1,4 @@ >> usr/bin/sshfs >> +#usr/sbin/mount.fuse.sshfs >> +#usr/sbin/mount.sshfs >> #usr/share/man/man1/sshfs.1 >> diff --git a/lfs/sshfs b/lfs/sshfs >> index 23fbd18ca..1e7706194 100644 >> --- a/lfs/sshfs >> +++ b/lfs/sshfs >> @@ -24,10 +24,10 @@ >> include Config >> -VER = 2.2 >> +VER = 3.7.1 >> -THISAPP = sshfs-fuse-$(VER) >> -DL_FILE = $(THISAPP).tar.gz >> +THISAPP = sshfs-$(VER) >> +DL_FILE = $(THISAPP).tar.xz >> DL_FROM = $(URL_IPFIRE) >> DIR_APP = $(DIR_SRC)/$(THISAPP) >> TARGET = $(DIR_INFO)/$(THISAPP) >> @@ -40,7 +40,7 @@ objects = $(DL_FILE) >> $(DL_FILE) = $(DL_FROM)/$(DL_FILE) >> -$(DL_FILE)_MD5 = 26e9206eb5169e87e6f95f54bc005a4f >> +$(DL_FILE)_MD5 = 22ac23d05ca7c56fb568627f086374d0 >> install : $(TARGET) >> @@ -72,9 +72,7 @@ $(subst %,%_MD5,$(objects)) : >> $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects)) >> @$(PREBUILD) >> - @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE) >> - cd $(DIR_APP) && ./configure --prefix=/usr >> - cd $(DIR_APP) && make $(MAKETUNING) >> - cd $(DIR_APP) && make install >> + @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE) >> + cd $(DIR_APP) && meson --prefix=/usr builddir && cd builddir && ninja && ninja install >> @rm -rf $(DIR_APP) >> @$(POSTBUILD)
Hi, On 06/01/2021 16:22, Michael Tremer wrote: > Hi, > >> On 5 Jan 2021, at 14:20, Adolf Belka <ahb.ipfire@gmail.com> wrote: >> >> - Update sshfs from 2.2 to 3.7.1 >> - Changelog is available at https://github.com/libfuse/sshfs/releases >> - Build had to be changed from autotools to meson/ninja >> - Change in rootfiles >> >> Signed-off-by: Adolf Belka <ahb.ipfire@gmail.com> >> --- >> config/rootfiles/common/sshfs | 2 ++ >> lfs/sshfs | 14 ++++++-------- >> 2 files changed, 8 insertions(+), 8 deletions(-) >> >> diff --git a/config/rootfiles/common/sshfs b/config/rootfiles/common/sshfs >> index 2cafa3e24..579b938f5 100644 >> --- a/config/rootfiles/common/sshfs >> +++ b/config/rootfiles/common/sshfs >> @@ -1,2 +1,4 @@ >> usr/bin/sshfs >> +#usr/sbin/mount.fuse.sshfs >> +#usr/sbin/mount.sshfs >> #usr/share/man/man1/sshfs.1 >> diff --git a/lfs/sshfs b/lfs/sshfs >> index 23fbd18ca..1e7706194 100644 >> --- a/lfs/sshfs >> +++ b/lfs/sshfs >> @@ -24,10 +24,10 @@ >> >> include Config >> >> -VER = 2.2 >> +VER = 3.7.1 >> >> -THISAPP = sshfs-fuse-$(VER) >> -DL_FILE = $(THISAPP).tar.gz >> +THISAPP = sshfs-$(VER) >> +DL_FILE = $(THISAPP).tar.xz >> DL_FROM = $(URL_IPFIRE) >> DIR_APP = $(DIR_SRC)/$(THISAPP) >> TARGET = $(DIR_INFO)/$(THISAPP) >> @@ -40,7 +40,7 @@ objects = $(DL_FILE) >> >> $(DL_FILE) = $(DL_FROM)/$(DL_FILE) >> >> -$(DL_FILE)_MD5 = 26e9206eb5169e87e6f95f54bc005a4f >> +$(DL_FILE)_MD5 = 22ac23d05ca7c56fb568627f086374d0 >> >> install : $(TARGET) >> >> @@ -72,9 +72,7 @@ $(subst %,%_MD5,$(objects)) : >> >> $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects)) >> @$(PREBUILD) >> - @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE) >> - cd $(DIR_APP) && ./configure --prefix=/usr >> - cd $(DIR_APP) && make $(MAKETUNING) >> - cd $(DIR_APP) && make install >> + @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE) >> + cd $(DIR_APP) && meson --prefix=/usr builddir && cd builddir && ninja && ninja install > > You could have written those into separate lines instead of all in one. That would have been slightly easier to read and change. That makes sense to do it like that. Should I redo this patch as a v2. When I split the parts onto different lines do I need to prefix each line with the cd $(DIR_APP) like the old .configure, make, make install sequence had. > >> @rm -rf $(DIR_APP) >> @$(POSTBUILD) >> -- >> 2.30.0 >> >
Hi, On 06/01/2021 16:30, Michael Tremer wrote: > Hi, > >> On 5 Jan 2021, at 14:28, Adolf Belka <ahb.ipfire@gmail.com> wrote: >> >> Dear all, >> >> Forgot to mention in the logs that I have also installed the built IPFire with new fuse and sshfs into my testbed system and was able to setup an sshfs mount from a remote computer into the IPFire system, so confirmed working. >> >> The only thing I had to do was run modprobe fuse as the fuse module was not loaded. Is that normal to need to do or did I miss something when I was building sshfs/fuse > > I would expect that sshfs is doing that automatically. Then there may be a problem. When I ran the sshfs command I got a message that it could not find fuse and it suggested that I should run modprobe fuse, which I did, and then the same sshfs command worked. Not sure how to find out why sshfs did not have the modprobe command run automatically or how to make it do so. > >> Regards, >> Adolf. >> >> On 05/01/2021 15:20, Adolf Belka wrote: >>> - Update sshfs from 2.2 to 3.7.1 >>> - Changelog is available at https://github.com/libfuse/sshfs/releases >>> - Build had to be changed from autotools to meson/ninja >>> - Change in rootfiles >>> Signed-off-by: Adolf Belka <ahb.ipfire@gmail.com> >>> --- >>> config/rootfiles/common/sshfs | 2 ++ >>> lfs/sshfs | 14 ++++++-------- >>> 2 files changed, 8 insertions(+), 8 deletions(-) >>> diff --git a/config/rootfiles/common/sshfs b/config/rootfiles/common/sshfs >>> index 2cafa3e24..579b938f5 100644 >>> --- a/config/rootfiles/common/sshfs >>> +++ b/config/rootfiles/common/sshfs >>> @@ -1,2 +1,4 @@ >>> usr/bin/sshfs >>> +#usr/sbin/mount.fuse.sshfs >>> +#usr/sbin/mount.sshfs >>> #usr/share/man/man1/sshfs.1 >>> diff --git a/lfs/sshfs b/lfs/sshfs >>> index 23fbd18ca..1e7706194 100644 >>> --- a/lfs/sshfs >>> +++ b/lfs/sshfs >>> @@ -24,10 +24,10 @@ >>> include Config >>> -VER = 2.2 >>> +VER = 3.7.1 >>> -THISAPP = sshfs-fuse-$(VER) >>> -DL_FILE = $(THISAPP).tar.gz >>> +THISAPP = sshfs-$(VER) >>> +DL_FILE = $(THISAPP).tar.xz >>> DL_FROM = $(URL_IPFIRE) >>> DIR_APP = $(DIR_SRC)/$(THISAPP) >>> TARGET = $(DIR_INFO)/$(THISAPP) >>> @@ -40,7 +40,7 @@ objects = $(DL_FILE) >>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE) >>> -$(DL_FILE)_MD5 = 26e9206eb5169e87e6f95f54bc005a4f >>> +$(DL_FILE)_MD5 = 22ac23d05ca7c56fb568627f086374d0 >>> install : $(TARGET) >>> @@ -72,9 +72,7 @@ $(subst %,%_MD5,$(objects)) : >>> $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects)) >>> @$(PREBUILD) >>> - @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE) >>> - cd $(DIR_APP) && ./configure --prefix=/usr >>> - cd $(DIR_APP) && make $(MAKETUNING) >>> - cd $(DIR_APP) && make install >>> + @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE) >>> + cd $(DIR_APP) && meson --prefix=/usr builddir && cd builddir && ninja && ninja install >>> @rm -rf $(DIR_APP) >>> @$(POSTBUILD) >
Hi Michael, I suddenly thought I should also check the old version on Core 153, so I did that and the same thing happens. The fuse module is not loaded automatically when sshfs command is run, but the error message is very helpful. "fuse: device not found, try 'modprobe fuse' first" So the new sshfs version operates the same as the old one, so I am no longer so worried about this. Regards, Adolf On 06/01/2021 19:39, Adolf Belka wrote: > Hi, > > > On 06/01/2021 16:30, Michael Tremer wrote: >> Hi, >> >>> On 5 Jan 2021, at 14:28, Adolf Belka <ahb.ipfire@gmail.com> wrote: >>> >>> Dear all, >>> >>> Forgot to mention in the logs that I have also installed the built IPFire with new fuse and sshfs into my testbed system and was able to setup an sshfs mount from a remote computer into the IPFire system, so confirmed working. >>> >>> The only thing I had to do was run modprobe fuse as the fuse module was not loaded. Is that normal to need to do or did I miss something when I was building sshfs/fuse >> >> I would expect that sshfs is doing that automatically. > > Then there may be a problem. When I ran the sshfs command I got a message that it could not find fuse and it suggested that I should run modprobe fuse, which I did, and then the same sshfs command worked. > > Not sure how to find out why sshfs did not have the modprobe command run automatically or how to make it do so. > >> >>> Regards, >>> Adolf. >>> >>> On 05/01/2021 15:20, Adolf Belka wrote: >>>> - Update sshfs from 2.2 to 3.7.1 >>>> - Changelog is available at https://github.com/libfuse/sshfs/releases >>>> - Build had to be changed from autotools to meson/ninja >>>> - Change in rootfiles >>>> Signed-off-by: Adolf Belka <ahb.ipfire@gmail.com> >>>> --- >>>> config/rootfiles/common/sshfs | 2 ++ >>>> lfs/sshfs | 14 ++++++-------- >>>> 2 files changed, 8 insertions(+), 8 deletions(-) >>>> diff --git a/config/rootfiles/common/sshfs b/config/rootfiles/common/sshfs >>>> index 2cafa3e24..579b938f5 100644 >>>> --- a/config/rootfiles/common/sshfs >>>> +++ b/config/rootfiles/common/sshfs >>>> @@ -1,2 +1,4 @@ >>>> usr/bin/sshfs >>>> +#usr/sbin/mount.fuse.sshfs >>>> +#usr/sbin/mount.sshfs >>>> #usr/share/man/man1/sshfs.1 >>>> diff --git a/lfs/sshfs b/lfs/sshfs >>>> index 23fbd18ca..1e7706194 100644 >>>> --- a/lfs/sshfs >>>> +++ b/lfs/sshfs >>>> @@ -24,10 +24,10 @@ >>>> include Config >>>> -VER = 2.2 >>>> +VER = 3.7.1 >>>> -THISAPP = sshfs-fuse-$(VER) >>>> -DL_FILE = $(THISAPP).tar.gz >>>> +THISAPP = sshfs-$(VER) >>>> +DL_FILE = $(THISAPP).tar.xz >>>> DL_FROM = $(URL_IPFIRE) >>>> DIR_APP = $(DIR_SRC)/$(THISAPP) >>>> TARGET = $(DIR_INFO)/$(THISAPP) >>>> @@ -40,7 +40,7 @@ objects = $(DL_FILE) >>>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE) >>>> -$(DL_FILE)_MD5 = 26e9206eb5169e87e6f95f54bc005a4f >>>> +$(DL_FILE)_MD5 = 22ac23d05ca7c56fb568627f086374d0 >>>> install : $(TARGET) >>>> @@ -72,9 +72,7 @@ $(subst %,%_MD5,$(objects)) : >>>> $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects)) >>>> @$(PREBUILD) >>>> - @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE) >>>> - cd $(DIR_APP) && ./configure --prefix=/usr >>>> - cd $(DIR_APP) && make $(MAKETUNING) >>>> - cd $(DIR_APP) && make install >>>> + @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE) >>>> + cd $(DIR_APP) && meson --prefix=/usr builddir && cd builddir && ninja && ninja install >>>> @rm -rf $(DIR_APP) >>>> @$(POSTBUILD) >>
Hi, In the Git repository of fuse, there is an initscript that loads the kernel module when the system boots: https://github.com/libfuse/libfuse/blob/f54eb86e9a0b596dfeceb18277efa8f840d85919/util/init_script Maybe we want to integrate this. -Michael > On 6 Jan 2021, at 19:21, Adolf Belka <ahb.ipfire@gmail.com> wrote: > > Hi Michael, > > I suddenly thought I should also check the old version on Core 153, so I did that and the same thing happens. The fuse module is not loaded automatically when sshfs command is run, but the error message is very helpful. > > "fuse: device not found, try 'modprobe fuse' first" > > So the new sshfs version operates the same as the old one, so I am no longer so worried about this. > > > Regards, > > Adolf > > On 06/01/2021 19:39, Adolf Belka wrote: >> Hi, >> >> >> On 06/01/2021 16:30, Michael Tremer wrote: >>> Hi, >>> >>>> On 5 Jan 2021, at 14:28, Adolf Belka <ahb.ipfire@gmail.com> wrote: >>>> >>>> Dear all, >>>> >>>> Forgot to mention in the logs that I have also installed the built IPFire with new fuse and sshfs into my testbed system and was able to setup an sshfs mount from a remote computer into the IPFire system, so confirmed working. >>>> >>>> The only thing I had to do was run modprobe fuse as the fuse module was not loaded. Is that normal to need to do or did I miss something when I was building sshfs/fuse >>> >>> I would expect that sshfs is doing that automatically. >> >> Then there may be a problem. When I ran the sshfs command I got a message that it could not find fuse and it suggested that I should run modprobe fuse, which I did, and then the same sshfs command worked. >> >> Not sure how to find out why sshfs did not have the modprobe command run automatically or how to make it do so. >> >>> >>>> Regards, >>>> Adolf. >>>> >>>> On 05/01/2021 15:20, Adolf Belka wrote: >>>>> - Update sshfs from 2.2 to 3.7.1 >>>>> - Changelog is available at https://github.com/libfuse/sshfs/releases >>>>> - Build had to be changed from autotools to meson/ninja >>>>> - Change in rootfiles >>>>> Signed-off-by: Adolf Belka <ahb.ipfire@gmail.com> >>>>> --- >>>>> config/rootfiles/common/sshfs | 2 ++ >>>>> lfs/sshfs | 14 ++++++-------- >>>>> 2 files changed, 8 insertions(+), 8 deletions(-) >>>>> diff --git a/config/rootfiles/common/sshfs b/config/rootfiles/common/sshfs >>>>> index 2cafa3e24..579b938f5 100644 >>>>> --- a/config/rootfiles/common/sshfs >>>>> +++ b/config/rootfiles/common/sshfs >>>>> @@ -1,2 +1,4 @@ >>>>> usr/bin/sshfs >>>>> +#usr/sbin/mount.fuse.sshfs >>>>> +#usr/sbin/mount.sshfs >>>>> #usr/share/man/man1/sshfs.1 >>>>> diff --git a/lfs/sshfs b/lfs/sshfs >>>>> index 23fbd18ca..1e7706194 100644 >>>>> --- a/lfs/sshfs >>>>> +++ b/lfs/sshfs >>>>> @@ -24,10 +24,10 @@ >>>>> include Config >>>>> -VER = 2.2 >>>>> +VER = 3.7.1 >>>>> -THISAPP = sshfs-fuse-$(VER) >>>>> -DL_FILE = $(THISAPP).tar.gz >>>>> +THISAPP = sshfs-$(VER) >>>>> +DL_FILE = $(THISAPP).tar.xz >>>>> DL_FROM = $(URL_IPFIRE) >>>>> DIR_APP = $(DIR_SRC)/$(THISAPP) >>>>> TARGET = $(DIR_INFO)/$(THISAPP) >>>>> @@ -40,7 +40,7 @@ objects = $(DL_FILE) >>>>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE) >>>>> -$(DL_FILE)_MD5 = 26e9206eb5169e87e6f95f54bc005a4f >>>>> +$(DL_FILE)_MD5 = 22ac23d05ca7c56fb568627f086374d0 >>>>> install : $(TARGET) >>>>> @@ -72,9 +72,7 @@ $(subst %,%_MD5,$(objects)) : >>>>> $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects)) >>>>> @$(PREBUILD) >>>>> - @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE) >>>>> - cd $(DIR_APP) && ./configure --prefix=/usr >>>>> - cd $(DIR_APP) && make $(MAKETUNING) >>>>> - cd $(DIR_APP) && make install >>>>> + @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE) >>>>> + cd $(DIR_APP) && meson --prefix=/usr builddir && cd builddir && ninja && ninja install >>>>> @rm -rf $(DIR_APP) >>>>> @$(POSTBUILD) >>>
Hi Michael, On 07/01/2021 12:25, Michael Tremer wrote: > Hi, > > In the Git repository of fuse, there is an initscript that loads the kernel module when the system boots: > > https://github.com/libfuse/libfuse/blob/f54eb86e9a0b596dfeceb18277efa8f840d85919/util/init_script > > Maybe we want to integrate this. That could be an option but the downside would be that the fuse module would then be enabled for all IPFire users, even if they are not using fuse. I think if people aren't using fuse on a firewall it is probably better to not load it automatically. As there have been no questions on IPFire Community about fuse not being loaded or any problems with sshfs then either no one is using sshfs and fuse or they have been able to figure it out. My preference would be to leave it as it is. I was going to say that I could update the wiki to mention about the need to run modprobe fuse but I found that sshfs is not mentioned anywhere in the wiki (at least the search came back with zero results). Having found out about sshfs on IPFire, I will likely use it from time to time. Regards, Adolf > > -Michael > >> On 6 Jan 2021, at 19:21, Adolf Belka <ahb.ipfire@gmail.com> wrote: >> >> Hi Michael, >> >> I suddenly thought I should also check the old version on Core 153, so I did that and the same thing happens. The fuse module is not loaded automatically when sshfs command is run, but the error message is very helpful. >> >> "fuse: device not found, try 'modprobe fuse' first" >> >> So the new sshfs version operates the same as the old one, so I am no longer so worried about this. >> >> >> Regards, >> >> Adolf >> >> On 06/01/2021 19:39, Adolf Belka wrote: >>> Hi, >>> >>> >>> On 06/01/2021 16:30, Michael Tremer wrote: >>>> Hi, >>>> >>>>> On 5 Jan 2021, at 14:28, Adolf Belka <ahb.ipfire@gmail.com> wrote: >>>>> >>>>> Dear all, >>>>> >>>>> Forgot to mention in the logs that I have also installed the built IPFire with new fuse and sshfs into my testbed system and was able to setup an sshfs mount from a remote computer into the IPFire system, so confirmed working. >>>>> >>>>> The only thing I had to do was run modprobe fuse as the fuse module was not loaded. Is that normal to need to do or did I miss something when I was building sshfs/fuse >>>> >>>> I would expect that sshfs is doing that automatically. >>> >>> Then there may be a problem. When I ran the sshfs command I got a message that it could not find fuse and it suggested that I should run modprobe fuse, which I did, and then the same sshfs command worked. >>> >>> Not sure how to find out why sshfs did not have the modprobe command run automatically or how to make it do so. >>> >>>> >>>>> Regards, >>>>> Adolf. >>>>> >>>>> On 05/01/2021 15:20, Adolf Belka wrote: >>>>>> - Update sshfs from 2.2 to 3.7.1 >>>>>> - Changelog is available at https://github.com/libfuse/sshfs/releases >>>>>> - Build had to be changed from autotools to meson/ninja >>>>>> - Change in rootfiles >>>>>> Signed-off-by: Adolf Belka <ahb.ipfire@gmail.com> >>>>>> --- >>>>>> config/rootfiles/common/sshfs | 2 ++ >>>>>> lfs/sshfs | 14 ++++++-------- >>>>>> 2 files changed, 8 insertions(+), 8 deletions(-) >>>>>> diff --git a/config/rootfiles/common/sshfs b/config/rootfiles/common/sshfs >>>>>> index 2cafa3e24..579b938f5 100644 >>>>>> --- a/config/rootfiles/common/sshfs >>>>>> +++ b/config/rootfiles/common/sshfs >>>>>> @@ -1,2 +1,4 @@ >>>>>> usr/bin/sshfs >>>>>> +#usr/sbin/mount.fuse.sshfs >>>>>> +#usr/sbin/mount.sshfs >>>>>> #usr/share/man/man1/sshfs.1 >>>>>> diff --git a/lfs/sshfs b/lfs/sshfs >>>>>> index 23fbd18ca..1e7706194 100644 >>>>>> --- a/lfs/sshfs >>>>>> +++ b/lfs/sshfs >>>>>> @@ -24,10 +24,10 @@ >>>>>> include Config >>>>>> -VER = 2.2 >>>>>> +VER = 3.7.1 >>>>>> -THISAPP = sshfs-fuse-$(VER) >>>>>> -DL_FILE = $(THISAPP).tar.gz >>>>>> +THISAPP = sshfs-$(VER) >>>>>> +DL_FILE = $(THISAPP).tar.xz >>>>>> DL_FROM = $(URL_IPFIRE) >>>>>> DIR_APP = $(DIR_SRC)/$(THISAPP) >>>>>> TARGET = $(DIR_INFO)/$(THISAPP) >>>>>> @@ -40,7 +40,7 @@ objects = $(DL_FILE) >>>>>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE) >>>>>> -$(DL_FILE)_MD5 = 26e9206eb5169e87e6f95f54bc005a4f >>>>>> +$(DL_FILE)_MD5 = 22ac23d05ca7c56fb568627f086374d0 >>>>>> install : $(TARGET) >>>>>> @@ -72,9 +72,7 @@ $(subst %,%_MD5,$(objects)) : >>>>>> $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects)) >>>>>> @$(PREBUILD) >>>>>> - @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE) >>>>>> - cd $(DIR_APP) && ./configure --prefix=/usr >>>>>> - cd $(DIR_APP) && make $(MAKETUNING) >>>>>> - cd $(DIR_APP) && make install >>>>>> + @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE) >>>>>> + cd $(DIR_APP) && meson --prefix=/usr builddir && cd builddir && ninja && ninja install >>>>>> @rm -rf $(DIR_APP) >>>>>> @$(POSTBUILD) >>>> >
Hello, > On 7 Jan 2021, at 13:34, Adolf Belka <ahb.ipfire@gmail.com> wrote: > > Hi Michael, > > On 07/01/2021 12:25, Michael Tremer wrote: >> Hi, >> In the Git repository of fuse, there is an initscript that loads the kernel module when the system boots: >> https://github.com/libfuse/libfuse/blob/f54eb86e9a0b596dfeceb18277efa8f840d85919/util/init_script >> Maybe we want to integrate this. > > That could be an option but the downside would be that the fuse module would then be enabled for all IPFire users, even if they are not using fuse. I think if people aren't using fuse on a firewall it is probably better to not load it automatically. Yes, I would agree. I assumed fuse was a package. Maybe it should be one. > As there have been no questions on IPFire Community about fuse not being loaded or any problems with sshfs then either no one is using sshfs and fuse or they have been able to figure it out. > > My preference would be to leave it as it is. > I was going to say that I could update the wiki to mention about the need to run modprobe fuse but I found that sshfs is not mentioned anywhere in the wiki (at least the search came back with zero results). > > Having found out about sshfs on IPFire, I will likely use it from time to time. It is quite a nice tool :) > Regards, > Adolf > >> -Michael >>> On 6 Jan 2021, at 19:21, Adolf Belka <ahb.ipfire@gmail.com> wrote: >>> >>> Hi Michael, >>> >>> I suddenly thought I should also check the old version on Core 153, so I did that and the same thing happens. The fuse module is not loaded automatically when sshfs command is run, but the error message is very helpful. >>> >>> "fuse: device not found, try 'modprobe fuse' first" >>> >>> So the new sshfs version operates the same as the old one, so I am no longer so worried about this. >>> >>> >>> Regards, >>> >>> Adolf >>> >>> On 06/01/2021 19:39, Adolf Belka wrote: >>>> Hi, >>>> >>>> >>>> On 06/01/2021 16:30, Michael Tremer wrote: >>>>> Hi, >>>>> >>>>>> On 5 Jan 2021, at 14:28, Adolf Belka <ahb.ipfire@gmail.com> wrote: >>>>>> >>>>>> Dear all, >>>>>> >>>>>> Forgot to mention in the logs that I have also installed the built IPFire with new fuse and sshfs into my testbed system and was able to setup an sshfs mount from a remote computer into the IPFire system, so confirmed working. >>>>>> >>>>>> The only thing I had to do was run modprobe fuse as the fuse module was not loaded. Is that normal to need to do or did I miss something when I was building sshfs/fuse >>>>> >>>>> I would expect that sshfs is doing that automatically. >>>> >>>> Then there may be a problem. When I ran the sshfs command I got a message that it could not find fuse and it suggested that I should run modprobe fuse, which I did, and then the same sshfs command worked. >>>> >>>> Not sure how to find out why sshfs did not have the modprobe command run automatically or how to make it do so. >>>> >>>>> >>>>>> Regards, >>>>>> Adolf. >>>>>> >>>>>> On 05/01/2021 15:20, Adolf Belka wrote: >>>>>>> - Update sshfs from 2.2 to 3.7.1 >>>>>>> - Changelog is available at https://github.com/libfuse/sshfs/releases >>>>>>> - Build had to be changed from autotools to meson/ninja >>>>>>> - Change in rootfiles >>>>>>> Signed-off-by: Adolf Belka <ahb.ipfire@gmail.com> >>>>>>> --- >>>>>>> config/rootfiles/common/sshfs | 2 ++ >>>>>>> lfs/sshfs | 14 ++++++-------- >>>>>>> 2 files changed, 8 insertions(+), 8 deletions(-) >>>>>>> diff --git a/config/rootfiles/common/sshfs b/config/rootfiles/common/sshfs >>>>>>> index 2cafa3e24..579b938f5 100644 >>>>>>> --- a/config/rootfiles/common/sshfs >>>>>>> +++ b/config/rootfiles/common/sshfs >>>>>>> @@ -1,2 +1,4 @@ >>>>>>> usr/bin/sshfs >>>>>>> +#usr/sbin/mount.fuse.sshfs >>>>>>> +#usr/sbin/mount.sshfs >>>>>>> #usr/share/man/man1/sshfs.1 >>>>>>> diff --git a/lfs/sshfs b/lfs/sshfs >>>>>>> index 23fbd18ca..1e7706194 100644 >>>>>>> --- a/lfs/sshfs >>>>>>> +++ b/lfs/sshfs >>>>>>> @@ -24,10 +24,10 @@ >>>>>>> include Config >>>>>>> -VER = 2.2 >>>>>>> +VER = 3.7.1 >>>>>>> -THISAPP = sshfs-fuse-$(VER) >>>>>>> -DL_FILE = $(THISAPP).tar.gz >>>>>>> +THISAPP = sshfs-$(VER) >>>>>>> +DL_FILE = $(THISAPP).tar.xz >>>>>>> DL_FROM = $(URL_IPFIRE) >>>>>>> DIR_APP = $(DIR_SRC)/$(THISAPP) >>>>>>> TARGET = $(DIR_INFO)/$(THISAPP) >>>>>>> @@ -40,7 +40,7 @@ objects = $(DL_FILE) >>>>>>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE) >>>>>>> -$(DL_FILE)_MD5 = 26e9206eb5169e87e6f95f54bc005a4f >>>>>>> +$(DL_FILE)_MD5 = 22ac23d05ca7c56fb568627f086374d0 >>>>>>> install : $(TARGET) >>>>>>> @@ -72,9 +72,7 @@ $(subst %,%_MD5,$(objects)) : >>>>>>> $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects)) >>>>>>> @$(PREBUILD) >>>>>>> - @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE) >>>>>>> - cd $(DIR_APP) && ./configure --prefix=/usr >>>>>>> - cd $(DIR_APP) && make $(MAKETUNING) >>>>>>> - cd $(DIR_APP) && make install >>>>>>> + @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE) >>>>>>> + cd $(DIR_APP) && meson --prefix=/usr builddir && cd builddir && ninja && ninja install >>>>>>> @rm -rf $(DIR_APP) >>>>>>> @$(POSTBUILD) >>>>>
Hi, On 07/01/2021 14:53, Michael Tremer wrote: > Hello, > >> On 7 Jan 2021, at 13:34, Adolf Belka <ahb.ipfire@gmail.com> wrote: >> >> Hi Michael, >> >> On 07/01/2021 12:25, Michael Tremer wrote: >>> Hi, >>> In the Git repository of fuse, there is an initscript that loads the kernel module when the system boots: >>> https://github.com/libfuse/libfuse/blob/f54eb86e9a0b596dfeceb18277efa8f840d85919/util/init_script >>> Maybe we want to integrate this. >> That could be an option but the downside would be that the fuse module would then be enabled for all IPFire users, even if they are not using fuse. I think if people aren't using fuse on a firewall it is probably better to not load it automatically. > Yes, I would agree. I assumed fuse was a package. Maybe it should be one. So I have had a look at this and it seems like both sshfs and fuse could be converted to addons. Fuse is only mentioned on three other addons, samba, openvmtools and borgbackup and not for any core programs. Fuse would need to be added as a dependency to those addons. By having that dependency does it mean that any systems with one of those addons already installed will automatically have the fuse addon installed as part of the core update or will I need a separate script to check for that. Should I look at doing this change now or wait till after the next core update has been released. Regards, Adolf >> As there have been no questions on IPFire Community about fuse not being loaded or any problems with sshfs then either no one is using sshfs and fuse or they have been able to figure it out. >> >> My preference would be to leave it as it is. >> I was going to say that I could update the wiki to mention about the need to run modprobe fuse but I found that sshfs is not mentioned anywhere in the wiki (at least the search came back with zero results). >> >> Having found out about sshfs on IPFire, I will likely use it from time to time. > It is quite a nice tool :) > >> Regards, >> Adolf >> >>> -Michael >>>> On 6 Jan 2021, at 19:21, Adolf Belka <ahb.ipfire@gmail.com> wrote: >>>> >>>> Hi Michael, >>>> >>>> I suddenly thought I should also check the old version on Core 153, so I did that and the same thing happens. The fuse module is not loaded automatically when sshfs command is run, but the error message is very helpful. >>>> >>>> "fuse: device not found, try 'modprobe fuse' first" >>>> >>>> So the new sshfs version operates the same as the old one, so I am no longer so worried about this. >>>> >>>> >>>> Regards, >>>> >>>> Adolf >>>> >>>> On 06/01/2021 19:39, Adolf Belka wrote: >>>>> Hi, >>>>> >>>>> >>>>> On 06/01/2021 16:30, Michael Tremer wrote: >>>>>> Hi, >>>>>> >>>>>>> On 5 Jan 2021, at 14:28, Adolf Belka <ahb.ipfire@gmail.com> wrote: >>>>>>> >>>>>>> Dear all, >>>>>>> >>>>>>> Forgot to mention in the logs that I have also installed the built IPFire with new fuse and sshfs into my testbed system and was able to setup an sshfs mount from a remote computer into the IPFire system, so confirmed working. >>>>>>> >>>>>>> The only thing I had to do was run modprobe fuse as the fuse module was not loaded. Is that normal to need to do or did I miss something when I was building sshfs/fuse >>>>>> I would expect that sshfs is doing that automatically. >>>>> Then there may be a problem. When I ran the sshfs command I got a message that it could not find fuse and it suggested that I should run modprobe fuse, which I did, and then the same sshfs command worked. >>>>> >>>>> Not sure how to find out why sshfs did not have the modprobe command run automatically or how to make it do so. >>>>> >>>>>>> Regards, >>>>>>> Adolf. >>>>>>> >>>>>>> On 05/01/2021 15:20, Adolf Belka wrote: >>>>>>>> - Update sshfs from 2.2 to 3.7.1 >>>>>>>> - Changelog is available at https://github.com/libfuse/sshfs/releases >>>>>>>> - Build had to be changed from autotools to meson/ninja >>>>>>>> - Change in rootfiles >>>>>>>> Signed-off-by: Adolf Belka <ahb.ipfire@gmail.com> >>>>>>>> --- >>>>>>>> config/rootfiles/common/sshfs | 2 ++ >>>>>>>> lfs/sshfs | 14 ++++++-------- >>>>>>>> 2 files changed, 8 insertions(+), 8 deletions(-) >>>>>>>> diff --git a/config/rootfiles/common/sshfs b/config/rootfiles/common/sshfs >>>>>>>> index 2cafa3e24..579b938f5 100644 >>>>>>>> --- a/config/rootfiles/common/sshfs >>>>>>>> +++ b/config/rootfiles/common/sshfs >>>>>>>> @@ -1,2 +1,4 @@ >>>>>>>> usr/bin/sshfs >>>>>>>> +#usr/sbin/mount.fuse.sshfs >>>>>>>> +#usr/sbin/mount.sshfs >>>>>>>> #usr/share/man/man1/sshfs.1 >>>>>>>> diff --git a/lfs/sshfs b/lfs/sshfs >>>>>>>> index 23fbd18ca..1e7706194 100644 >>>>>>>> --- a/lfs/sshfs >>>>>>>> +++ b/lfs/sshfs >>>>>>>> @@ -24,10 +24,10 @@ >>>>>>>> include Config >>>>>>>> -VER = 2.2 >>>>>>>> +VER = 3.7.1 >>>>>>>> -THISAPP = sshfs-fuse-$(VER) >>>>>>>> -DL_FILE = $(THISAPP).tar.gz >>>>>>>> +THISAPP = sshfs-$(VER) >>>>>>>> +DL_FILE = $(THISAPP).tar.xz >>>>>>>> DL_FROM = $(URL_IPFIRE) >>>>>>>> DIR_APP = $(DIR_SRC)/$(THISAPP) >>>>>>>> TARGET = $(DIR_INFO)/$(THISAPP) >>>>>>>> @@ -40,7 +40,7 @@ objects = $(DL_FILE) >>>>>>>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE) >>>>>>>> -$(DL_FILE)_MD5 = 26e9206eb5169e87e6f95f54bc005a4f >>>>>>>> +$(DL_FILE)_MD5 = 22ac23d05ca7c56fb568627f086374d0 >>>>>>>> install : $(TARGET) >>>>>>>> @@ -72,9 +72,7 @@ $(subst %,%_MD5,$(objects)) : >>>>>>>> $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects)) >>>>>>>> @$(PREBUILD) >>>>>>>> - @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE) >>>>>>>> - cd $(DIR_APP) && ./configure --prefix=/usr >>>>>>>> - cd $(DIR_APP) && make $(MAKETUNING) >>>>>>>> - cd $(DIR_APP) && make install >>>>>>>> + @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE) >>>>>>>> + cd $(DIR_APP) && meson --prefix=/usr builddir && cd builddir && ninja && ninja install >>>>>>>> @rm -rf $(DIR_APP) >>>>>>>> @$(POSTBUILD)
Hi, > On 9 Jan 2021, at 14:55, Adolf Belka (ipfire) <ahb.ipfire@gmail.com> wrote: > > Hi, > > On 07/01/2021 14:53, Michael Tremer wrote: >> Hello, >> >>> On 7 Jan 2021, at 13:34, Adolf Belka <ahb.ipfire@gmail.com> wrote: >>> >>> Hi Michael, >>> >>> On 07/01/2021 12:25, Michael Tremer wrote: >>>> Hi, >>>> In the Git repository of fuse, there is an initscript that loads the kernel module when the system boots: >>>> https://github.com/libfuse/libfuse/blob/f54eb86e9a0b596dfeceb18277efa8f840d85919/util/init_script >>>> Maybe we want to integrate this. >>> That could be an option but the downside would be that the fuse module would then be enabled for all IPFire users, even if they are not using fuse. I think if people aren't using fuse on a firewall it is probably better to not load it automatically. >> Yes, I would agree. I assumed fuse was a package. Maybe it should be one. > > So I have had a look at this and it seems like both sshfs and fuse could be converted to addons. Fuse is only mentioned on three other addons, samba, openvmtools and borgbackup and not for any core programs. I do not understand precisely why those add-ons need fuse. Any ideas? > Fuse would need to be added as a dependency to those addons. By having that dependency does it mean that any systems with one of those addons already installed will automatically have the fuse addon installed as part of the core update or will I need a separate script to check for that. > > Should I look at doing this change now or wait till after the next core update has been released. I think we can start working on this now. I do not see any reason to wait. -Michael > Regards, > > Adolf > >>> As there have been no questions on IPFire Community about fuse not being loaded or any problems with sshfs then either no one is using sshfs and fuse or they have been able to figure it out. >>> >>> My preference would be to leave it as it is. >>> I was going to say that I could update the wiki to mention about the need to run modprobe fuse but I found that sshfs is not mentioned anywhere in the wiki (at least the search came back with zero results). >>> >>> Having found out about sshfs on IPFire, I will likely use it from time to time. >> It is quite a nice tool :) >> >>> Regards, >>> Adolf >>> >>>> -Michael >>>>> On 6 Jan 2021, at 19:21, Adolf Belka <ahb.ipfire@gmail.com> wrote: >>>>> >>>>> Hi Michael, >>>>> >>>>> I suddenly thought I should also check the old version on Core 153, so I did that and the same thing happens. The fuse module is not loaded automatically when sshfs command is run, but the error message is very helpful. >>>>> >>>>> "fuse: device not found, try 'modprobe fuse' first" >>>>> >>>>> So the new sshfs version operates the same as the old one, so I am no longer so worried about this. >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Adolf >>>>> >>>>> On 06/01/2021 19:39, Adolf Belka wrote: >>>>>> Hi, >>>>>> >>>>>> >>>>>> On 06/01/2021 16:30, Michael Tremer wrote: >>>>>>> Hi, >>>>>>> >>>>>>>> On 5 Jan 2021, at 14:28, Adolf Belka <ahb.ipfire@gmail.com> wrote: >>>>>>>> >>>>>>>> Dear all, >>>>>>>> >>>>>>>> Forgot to mention in the logs that I have also installed the built IPFire with new fuse and sshfs into my testbed system and was able to setup an sshfs mount from a remote computer into the IPFire system, so confirmed working. >>>>>>>> >>>>>>>> The only thing I had to do was run modprobe fuse as the fuse module was not loaded. Is that normal to need to do or did I miss something when I was building sshfs/fuse >>>>>>> I would expect that sshfs is doing that automatically. >>>>>> Then there may be a problem. When I ran the sshfs command I got a message that it could not find fuse and it suggested that I should run modprobe fuse, which I did, and then the same sshfs command worked. >>>>>> >>>>>> Not sure how to find out why sshfs did not have the modprobe command run automatically or how to make it do so. >>>>>> >>>>>>>> Regards, >>>>>>>> Adolf. >>>>>>>> >>>>>>>> On 05/01/2021 15:20, Adolf Belka wrote: >>>>>>>>> - Update sshfs from 2.2 to 3.7.1 >>>>>>>>> - Changelog is available at https://github.com/libfuse/sshfs/releases >>>>>>>>> - Build had to be changed from autotools to meson/ninja >>>>>>>>> - Change in rootfiles >>>>>>>>> Signed-off-by: Adolf Belka <ahb.ipfire@gmail.com> >>>>>>>>> --- >>>>>>>>> config/rootfiles/common/sshfs | 2 ++ >>>>>>>>> lfs/sshfs | 14 ++++++-------- >>>>>>>>> 2 files changed, 8 insertions(+), 8 deletions(-) >>>>>>>>> diff --git a/config/rootfiles/common/sshfs b/config/rootfiles/common/sshfs >>>>>>>>> index 2cafa3e24..579b938f5 100644 >>>>>>>>> --- a/config/rootfiles/common/sshfs >>>>>>>>> +++ b/config/rootfiles/common/sshfs >>>>>>>>> @@ -1,2 +1,4 @@ >>>>>>>>> usr/bin/sshfs >>>>>>>>> +#usr/sbin/mount.fuse.sshfs >>>>>>>>> +#usr/sbin/mount.sshfs >>>>>>>>> #usr/share/man/man1/sshfs.1 >>>>>>>>> diff --git a/lfs/sshfs b/lfs/sshfs >>>>>>>>> index 23fbd18ca..1e7706194 100644 >>>>>>>>> --- a/lfs/sshfs >>>>>>>>> +++ b/lfs/sshfs >>>>>>>>> @@ -24,10 +24,10 @@ >>>>>>>>> include Config >>>>>>>>> -VER = 2.2 >>>>>>>>> +VER = 3.7.1 >>>>>>>>> -THISAPP = sshfs-fuse-$(VER) >>>>>>>>> -DL_FILE = $(THISAPP).tar.gz >>>>>>>>> +THISAPP = sshfs-$(VER) >>>>>>>>> +DL_FILE = $(THISAPP).tar.xz >>>>>>>>> DL_FROM = $(URL_IPFIRE) >>>>>>>>> DIR_APP = $(DIR_SRC)/$(THISAPP) >>>>>>>>> TARGET = $(DIR_INFO)/$(THISAPP) >>>>>>>>> @@ -40,7 +40,7 @@ objects = $(DL_FILE) >>>>>>>>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE) >>>>>>>>> -$(DL_FILE)_MD5 = 26e9206eb5169e87e6f95f54bc005a4f >>>>>>>>> +$(DL_FILE)_MD5 = 22ac23d05ca7c56fb568627f086374d0 >>>>>>>>> install : $(TARGET) >>>>>>>>> @@ -72,9 +72,7 @@ $(subst %,%_MD5,$(objects)) : >>>>>>>>> $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects)) >>>>>>>>> @$(PREBUILD) >>>>>>>>> - @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE) >>>>>>>>> - cd $(DIR_APP) && ./configure --prefix=/usr >>>>>>>>> - cd $(DIR_APP) && make $(MAKETUNING) >>>>>>>>> - cd $(DIR_APP) && make install >>>>>>>>> + @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE) >>>>>>>>> + cd $(DIR_APP) && meson --prefix=/usr builddir && cd builddir && ninja && ninja install >>>>>>>>> @rm -rf $(DIR_APP) >>>>>>>>> @$(POSTBUILD)
Hi Michael, On 09/01/2021 15:58, Michael Tremer wrote: > Hi, > >> On 9 Jan 2021, at 14:55, Adolf Belka (ipfire) <ahb.ipfire@gmail.com> wrote: >> >> Hi, >> >> On 07/01/2021 14:53, Michael Tremer wrote: >>> Hello, >>> >>>> On 7 Jan 2021, at 13:34, Adolf Belka <ahb.ipfire@gmail.com> wrote: >>>> >>>> Hi Michael, >>>> >>>> On 07/01/2021 12:25, Michael Tremer wrote: >>>>> Hi, >>>>> In the Git repository of fuse, there is an initscript that loads the kernel module when the system boots: >>>>> https://github.com/libfuse/libfuse/blob/f54eb86e9a0b596dfeceb18277efa8f840d85919/util/init_script >>>>> Maybe we want to integrate this. >>>> That could be an option but the downside would be that the fuse module would then be enabled for all IPFire users, even if they are not using fuse. I think if people aren't using fuse on a firewall it is probably better to not load it automatically. >>> Yes, I would agree. I assumed fuse was a package. Maybe it should be one. >> So I have had a look at this and it seems like both sshfs and fuse could be converted to addons. Fuse is only mentioned on three other addons, samba, openvmtools and borgbackup and not for any core programs. > I do not understand precisely why those add-ons need fuse. Any ideas? Each of the addons rootfiles have the word fuse in at least one line that is not commented out. I had a quick look at the borgbackup website and it looks like you can have the possibility to backup to a fuse mounted filesystem. Similar with samba that you can have a fuse based system defined in some way. I am not sure about openvmtools. >> Fuse would need to be added as a dependency to those addons. By having that dependency does it mean that any systems with one of those addons already installed will automatically have the fuse addon installed as part of the core update or will I need a separate script to check for that. >> >> Should I look at doing this change now or wait till after the next core update has been released. > I think we can start working on this now. I do not see any reason to wait. Will do so. Regards, Adolf. > -Michael > >> Regards, >> >> Adolf >> >>>> As there have been no questions on IPFire Community about fuse not being loaded or any problems with sshfs then either no one is using sshfs and fuse or they have been able to figure it out. >>>> >>>> My preference would be to leave it as it is. >>>> I was going to say that I could update the wiki to mention about the need to run modprobe fuse but I found that sshfs is not mentioned anywhere in the wiki (at least the search came back with zero results). >>>> >>>> Having found out about sshfs on IPFire, I will likely use it from time to time. >>> It is quite a nice tool :) >>> >>>> Regards, >>>> Adolf >>>> >>>>> -Michael >>>>>> On 6 Jan 2021, at 19:21, Adolf Belka <ahb.ipfire@gmail.com> wrote: >>>>>> >>>>>> Hi Michael, >>>>>> >>>>>> I suddenly thought I should also check the old version on Core 153, so I did that and the same thing happens. The fuse module is not loaded automatically when sshfs command is run, but the error message is very helpful. >>>>>> >>>>>> "fuse: device not found, try 'modprobe fuse' first" >>>>>> >>>>>> So the new sshfs version operates the same as the old one, so I am no longer so worried about this. >>>>>> >>>>>> >>>>>> Regards, >>>>>> >>>>>> Adolf >>>>>> >>>>>> On 06/01/2021 19:39, Adolf Belka wrote: >>>>>>> Hi, >>>>>>> >>>>>>> >>>>>>> On 06/01/2021 16:30, Michael Tremer wrote: >>>>>>>> Hi, >>>>>>>> >>>>>>>>> On 5 Jan 2021, at 14:28, Adolf Belka <ahb.ipfire@gmail.com> wrote: >>>>>>>>> >>>>>>>>> Dear all, >>>>>>>>> >>>>>>>>> Forgot to mention in the logs that I have also installed the built IPFire with new fuse and sshfs into my testbed system and was able to setup an sshfs mount from a remote computer into the IPFire system, so confirmed working. >>>>>>>>> >>>>>>>>> The only thing I had to do was run modprobe fuse as the fuse module was not loaded. Is that normal to need to do or did I miss something when I was building sshfs/fuse >>>>>>>> I would expect that sshfs is doing that automatically. >>>>>>> Then there may be a problem. When I ran the sshfs command I got a message that it could not find fuse and it suggested that I should run modprobe fuse, which I did, and then the same sshfs command worked. >>>>>>> >>>>>>> Not sure how to find out why sshfs did not have the modprobe command run automatically or how to make it do so. >>>>>>> >>>>>>>>> Regards, >>>>>>>>> Adolf. >>>>>>>>> >>>>>>>>> On 05/01/2021 15:20, Adolf Belka wrote: >>>>>>>>>> - Update sshfs from 2.2 to 3.7.1 >>>>>>>>>> - Changelog is available at https://github.com/libfuse/sshfs/releases >>>>>>>>>> - Build had to be changed from autotools to meson/ninja >>>>>>>>>> - Change in rootfiles >>>>>>>>>> Signed-off-by: Adolf Belka <ahb.ipfire@gmail.com> >>>>>>>>>> --- >>>>>>>>>> config/rootfiles/common/sshfs | 2 ++ >>>>>>>>>> lfs/sshfs | 14 ++++++-------- >>>>>>>>>> 2 files changed, 8 insertions(+), 8 deletions(-) >>>>>>>>>> diff --git a/config/rootfiles/common/sshfs b/config/rootfiles/common/sshfs >>>>>>>>>> index 2cafa3e24..579b938f5 100644 >>>>>>>>>> --- a/config/rootfiles/common/sshfs >>>>>>>>>> +++ b/config/rootfiles/common/sshfs >>>>>>>>>> @@ -1,2 +1,4 @@ >>>>>>>>>> usr/bin/sshfs >>>>>>>>>> +#usr/sbin/mount.fuse.sshfs >>>>>>>>>> +#usr/sbin/mount.sshfs >>>>>>>>>> #usr/share/man/man1/sshfs.1 >>>>>>>>>> diff --git a/lfs/sshfs b/lfs/sshfs >>>>>>>>>> index 23fbd18ca..1e7706194 100644 >>>>>>>>>> --- a/lfs/sshfs >>>>>>>>>> +++ b/lfs/sshfs >>>>>>>>>> @@ -24,10 +24,10 @@ >>>>>>>>>> include Config >>>>>>>>>> -VER = 2.2 >>>>>>>>>> +VER = 3.7.1 >>>>>>>>>> -THISAPP = sshfs-fuse-$(VER) >>>>>>>>>> -DL_FILE = $(THISAPP).tar.gz >>>>>>>>>> +THISAPP = sshfs-$(VER) >>>>>>>>>> +DL_FILE = $(THISAPP).tar.xz >>>>>>>>>> DL_FROM = $(URL_IPFIRE) >>>>>>>>>> DIR_APP = $(DIR_SRC)/$(THISAPP) >>>>>>>>>> TARGET = $(DIR_INFO)/$(THISAPP) >>>>>>>>>> @@ -40,7 +40,7 @@ objects = $(DL_FILE) >>>>>>>>>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE) >>>>>>>>>> -$(DL_FILE)_MD5 = 26e9206eb5169e87e6f95f54bc005a4f >>>>>>>>>> +$(DL_FILE)_MD5 = 22ac23d05ca7c56fb568627f086374d0 >>>>>>>>>> install : $(TARGET) >>>>>>>>>> @@ -72,9 +72,7 @@ $(subst %,%_MD5,$(objects)) : >>>>>>>>>> $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects)) >>>>>>>>>> @$(PREBUILD) >>>>>>>>>> - @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE) >>>>>>>>>> - cd $(DIR_APP) && ./configure --prefix=/usr >>>>>>>>>> - cd $(DIR_APP) && make $(MAKETUNING) >>>>>>>>>> - cd $(DIR_APP) && make install >>>>>>>>>> + @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE) >>>>>>>>>> + cd $(DIR_APP) && meson --prefix=/usr builddir && cd builddir && ninja && ninja install >>>>>>>>>> @rm -rf $(DIR_APP) >>>>>>>>>> @$(POSTBUILD)
diff --git a/config/rootfiles/common/sshfs b/config/rootfiles/common/sshfs index 2cafa3e24..579b938f5 100644 --- a/config/rootfiles/common/sshfs +++ b/config/rootfiles/common/sshfs @@ -1,2 +1,4 @@ usr/bin/sshfs +#usr/sbin/mount.fuse.sshfs +#usr/sbin/mount.sshfs #usr/share/man/man1/sshfs.1 diff --git a/lfs/sshfs b/lfs/sshfs index 23fbd18ca..1e7706194 100644 --- a/lfs/sshfs +++ b/lfs/sshfs @@ -24,10 +24,10 @@ include Config -VER = 2.2 +VER = 3.7.1 -THISAPP = sshfs-fuse-$(VER) -DL_FILE = $(THISAPP).tar.gz +THISAPP = sshfs-$(VER) +DL_FILE = $(THISAPP).tar.xz DL_FROM = $(URL_IPFIRE) DIR_APP = $(DIR_SRC)/$(THISAPP) TARGET = $(DIR_INFO)/$(THISAPP) @@ -40,7 +40,7 @@ objects = $(DL_FILE) $(DL_FILE) = $(DL_FROM)/$(DL_FILE) -$(DL_FILE)_MD5 = 26e9206eb5169e87e6f95f54bc005a4f +$(DL_FILE)_MD5 = 22ac23d05ca7c56fb568627f086374d0 install : $(TARGET) @@ -72,9 +72,7 @@ $(subst %,%_MD5,$(objects)) : $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects)) @$(PREBUILD) - @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE) - cd $(DIR_APP) && ./configure --prefix=/usr - cd $(DIR_APP) && make $(MAKETUNING) - cd $(DIR_APP) && make install + @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE) + cd $(DIR_APP) && meson --prefix=/usr builddir && cd builddir && ninja && ninja install @rm -rf $(DIR_APP) @$(POSTBUILD)