[ANN] CRUX 3.2-rc3 available for testing
Greetings, CRUX 3.2-rc3 is now available for testing. rc2 was flawed and we'll forget it ever happened. http://jaeger.morpheus.net/linux/crux/files/rc/crux-3.2-rc3.iso http://jaeger.morpheus.net/linux/crux/files/rc/crux-3.2-rc3.md5 Please report any issues if you find them. Cheers, Matt
Hi all [1] The installation of this new rc was without any issue. I used the config/kernel/firmware from Slackware -current [2] [3] so no problem so far. At this moment I'm noticing that you are using dash for sh instead of bash, so trying to build x11vnc gives me this error: --- In file included from ../rfb/rfbproto.h:70:0, from ../rfb/rfb.h:44, from main.c:16: ../rfb/rfbconfig.h:9:22: warning: extra tokens at end of #ifndef directive #ifndef LIBVNCSERVER_ ^ ../rfb/rfbconfig.h:10:22: warning: ISO C99 requires whitespace after the macro name #define LIBVNCSERVER_ ^ ../rfb/rfbconfig.h:20:22: warning: extra tokens at end of #ifndef directive #ifndef LIBVNCSERVER_ ^ ... ... main.c:1060:19: fatal error: conio.h: No such file or directory compilation terminated. Makefile:345: recipe for target 'main.o' failed make[2]: *** [main.o] Error 1 make[2]: Leaving directory '/usr/ports/contrib/x11vnc/work/src/x11vnc-0.9.13/libvncserver' Makefile:312: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/usr/ports/contrib/x11vnc/work/src/x11vnc-0.9.13' Makefile:231: recipe for target 'all' failed make: *** [all] Error 2 --- After doing: root@ ~ cd /bin/; rm sh ; ln -s bash sh; cd - the installation of x11vnc ends without any issue. - Cheers [1] I hope this time it is to the mail-list ;-) [2] ftp://ftp.osuosl.org/pub/slackware/slackware64-current/source/k/ [3] I was using Slackware before, since like 10 years ago. On Fri, Oct 30, 2015 at 8:16 AM, Matt Housh <jaeger@morpheus.net> wrote:
Greetings,
CRUX 3.2-rc3 is now available for testing. rc2 was flawed and we'll forget it ever happened.
http://jaeger.morpheus.net/linux/crux/files/rc/crux-3.2-rc3.iso http://jaeger.morpheus.net/linux/crux/files/rc/crux-3.2-rc3.md5
Please report any issues if you find them.
Cheers, Matt
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
-- Antonio Hernández Blas | Oaxaca, México, Mx. https://github.com/nihilismus | https://bitbucket.org/nihilismus | https://twitter.com/nihilipster
On Wed, Nov 04, 2015 at 04:20:30AM -0600, Antonio Hernández Blas wrote:
Hi all [1]
The installation of this new rc was without any issue. I used the config/kernel/firmware from Slackware -current [2] [3] so no problem so far.
At this moment I'm noticing that you are using dash for sh instead of bash, so trying to build x11vnc gives me this error:
Thanks for the report. A proper fix would be to remove the bashism from x11vnc, but for now I'd suggest to apply the following patch to the port. Greetings Juergen --- diff --git a/x11vnc/Pkgfile b/x11vnc/Pkgfile index 8b07627..7582a69 100644 --- a/x11vnc/Pkgfile +++ b/x11vnc/Pkgfile @@ -10,6 +10,7 @@ source=(http://prdownloads.sf.net/libvncserver/$name-$version.tar.gz) build() { cd $name-$version + CONFIG_SHELL=/bin/bash \ ./configure --prefix=/usr \ --disable-nls \ --mandir=$PKG/usr/man
Hi Juergen. Thanks and confirmed, reverting sh to be dash and making the indicated modifications makes the installation of x11vnc end without any issue. On Wed, Nov 4, 2015 at 4:37 AM, Juergen Daubert <jue@jue.li> wrote:
On Wed, Nov 04, 2015 at 04:20:30AM -0600, Antonio Hernández Blas wrote:
Hi all [1]
The installation of this new rc was without any issue. I used the config/kernel/firmware from Slackware -current [2] [3] so no problem so far.
At this moment I'm noticing that you are using dash for sh instead of bash, so trying to build x11vnc gives me this error:
Thanks for the report. A proper fix would be to remove the bashism from x11vnc, but for now I'd suggest to apply the following patch to the port.
Greetings Juergen
---
diff --git a/x11vnc/Pkgfile b/x11vnc/Pkgfile index 8b07627..7582a69 100644 --- a/x11vnc/Pkgfile +++ b/x11vnc/Pkgfile @@ -10,6 +10,7 @@ source=( http://prdownloads.sf.net/libvncserver/$name-$version.tar.gz)
build() { cd $name-$version + CONFIG_SHELL=/bin/bash \ ./configure --prefix=/usr \ --disable-nls \ --mandir=$PKG/usr/man
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
-- Antonio Hernández Blas | Oaxaca, México, Mx. https://github.com/nihilismus | https://bitbucket.org/nihilismus | https://twitter.com/nihilipster
On 2015-11-04 19:37, Juergen Daubert wrote:
Thanks for the report. A proper fix would be to remove the bashism from x11vnc, but for now I'd suggest to apply the following patch to the port.
The problem is not a bashism, but a dashism. Take a look at the generated rfb/rfbconfig.h file by dash, it has non-printable characters. In dash, the output from: echo "\1" is the non-printable character that would require a leading zero in any other shell. From what I read, the posix standard is not explicit in the output of this escape sequence, so dash chooses to produce the non-printable character while the other shells produce the output that most people expect. This has been discussed in their mailing lists, and patchs have been proposed but not accepted: http://www.mail-archive.com/dash%40vger.kernel.org/msg00635.html http://www.mail-archive.com/dash%40vger.kernel.org/msg00963.html Expect trouble from using dash as /bin/sh. Regards, Alan Mizrahi
On Wed, Nov 4, 2015 at 7:34 AM, Alan Mizrahi <alan+crux@mizrahi.com.ve> wrote:
Expect trouble from using dash as /bin/sh.
Already noticed this with my own /etc/rc.d/vde2 script which uses bash arrays :-) Any benefit or reason behind the use of dash as sh? -- Antonio Hernández Blas | Oaxaca, México, Mx. https://github.com/nihilismus | https://bitbucket.org/nihilismus | https://twitter.com/nihilipster
On Fri, Nov 06, 2015 at 08:50:10PM -0600, Antonio Hernández Blas wrote:
On Wed, Nov 4, 2015 at 7:34 AM, Alan Mizrahi <[1]alan+crux@mizrahi.com.ve> wrote:
Expect trouble from using dash as /bin/sh.
It's not a issue at all. All ports from our ISO, and everything we use just works fine with dash. Currently we have only one port from opt, cppunit, that needs the CONFIG_SHELL=/bin/bash fix.
Already noticed this with my own /etc/rc.d/vde2 script which uses bash arrays :-)
Well, if you use bash arrays in a script you should use the right shebang ;)
Any benefit or reason behind the use of dash as sh?
Speed and resource usage. It's not relevant for things like rc scripts or e.g. our pkgmk, but really notable for compiling sources that uses the auto*/libtool stuff which normally calls a huge number of shells. I've made a, for sure unscientific, test with interesting results, see [1]. Memory usage of bash is around 5 times of dash. Greetings Juergen [1] http://e33e40b3f200dbd7.paste.se/
Hi Juergen. Thanks for the explanation and your tests. The only thing that I can ask at this moment is, how often are *those* packages recompiled? and it wouldn't make more sense to force the use of dash with *just* the packages that take more time/resources? In any case I'm going to be more careful with my own local ports :-) On Sat, Nov 7, 2015 at 4:27 AM, Juergen Daubert <jue@jue.li> wrote:
On Fri, Nov 06, 2015 at 08:50:10PM -0600, Antonio Hernández Blas wrote:
On Wed, Nov 4, 2015 at 7:34 AM, Alan Mizrahi <[1] alan+crux@mizrahi.com.ve> wrote:
Expect trouble from using dash as /bin/sh.
It's not a issue at all. All ports from our ISO, and everything we use just works fine with dash. Currently we have only one port from opt, cppunit, that needs the CONFIG_SHELL=/bin/bash fix.
Already noticed this with my own /etc/rc.d/vde2 script which uses bash arrays :-)
Well, if you use bash arrays in a script you should use the right shebang ;)
Any benefit or reason behind the use of dash as sh?
Speed and resource usage. It's not relevant for things like rc scripts or e.g. our pkgmk, but really notable for compiling sources that uses the auto*/libtool stuff which normally calls a huge number of shells. I've made a, for sure unscientific, test with interesting results, see [1]. Memory usage of bash is around 5 times of dash.
Greetings Juergen
[1] http://e33e40b3f200dbd7.paste.se/
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
-- Antonio Hernández Blas | Oaxaca, México, Mx. https://github.com/nihilismus | https://bitbucket.org/nihilismus | https://twitter.com/nihilipster
On Fri, Nov 13, 2015 at 09:26:03PM -0600, Antonio Hernández Blas wrote:
Hi Juergen.
Thanks for the explanation and your tests. The only thing that I can ask at this moment is, how often are *those* packages recompiled? and it wouldn't make more sense to force the use of dash with *just* the packages that take more time/resources?
Well since we are a source-based distribution, every time you upgrade something. As Juergen said, if you have bashism in your scripts - shebang it to #!/bin/bash! I have to say I'm surprised by the short memory people seems to have. A year ago everyone wanted to get rid of bash due to a few security holes and now everyone seems to love it again :-)
In any case I'm going to be more careful with my own local ports :-)
Good practice anyways :) -- Fredrik Rinnestam
Hi Fredrik. Sorry but I'm a ksh/mksh user since some years ago, so I'm not in love with bash ;-) My only concern is with a program/library, that using auto*/libtool, relies on some bashism. That is the reason to be more careful :-) One could say that bash is the standard shell in Linux, just like for some people vim is the standard editor. On Sat, Nov 14, 2015 at 7:20 AM, Fredrik Rinnestam <fredrik@rinnestam.se> wrote:
On Fri, Nov 13, 2015 at 09:26:03PM -0600, Antonio Hernández Blas wrote:
Hi Juergen.
Thanks for the explanation and your tests. The only thing that I can ask at this moment is, how often are *those* packages recompiled? and it wouldn't make more sense to force the use of dash with *just* the packages that take more time/resources?
Well since we are a source-based distribution, every time you upgrade something. As Juergen said, if you have bashism in your scripts - shebang it to #!/bin/bash!
I have to say I'm surprised by the short memory people seems to have. A year ago everyone wanted to get rid of bash due to a few security holes and now everyone seems to love it again :-)
In any case I'm going to be more careful with my own local ports :-)
Good practice anyways :)
--
Fredrik Rinnestam _______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
-- Antonio Hernández Blas | Oaxaca, México, Mx. https://github.com/nihilismus | https://bitbucket.org/nihilismus | https://twitter.com/nihilipster
Another issue i faced today, now with /usr/ports/contrib/libvpx: --- [CC] test/../md5_utils.c.o [CC] test/../nestegg/halloc/src/halloc.c.o In file included from test/../nestegg/halloc/src/halloc.c:19:0: test/../nestegg/halloc/src/align.h:33:25: error: conflicting types for 'max_align_t' typedef union max_align max_align_t; ^ In file included from test/../nestegg/halloc/src/../halloc.h:18:0, from test/../nestegg/halloc/src/halloc.c:18: /usr/lib/gcc/x86_64-unknown-linux-gnu/5.2.0/include/stddef.h:429:3: note: previous declaration of 'max_align_t' was here } max_align_t; ^ Makefile:128: recipe for target 'test/../nestegg/halloc/src/halloc.c.o' failed make[1]: *** [test/../nestegg/halloc/src/halloc.c.o] Error 1 Makefile:17: recipe for target '.DEFAULT' failed make: *** [.DEFAULT] Error 2 --- Arch Linux already has a patch [1] that works. Debian has a patch with the same modifications [2], before Arch Linux, and according to them this is already fixed in libvpx-1.4.0 [3] [1] https://aur.archlinux.org/cgit/aur.git/tree/gcc-5.2.patch?h=libvpx-1.3 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777976 [3] http://storage.googleapis.com/downloads.webmproject.org/releases/webm/libvpx... On Fri, Oct 30, 2015 at 8:16 AM, Matt Housh <jaeger@morpheus.net> wrote:
Greetings,
CRUX 3.2-rc3 is now available for testing. rc2 was flawed and we'll forget it ever happened.
http://jaeger.morpheus.net/linux/crux/files/rc/crux-3.2-rc3.iso http://jaeger.morpheus.net/linux/crux/files/rc/crux-3.2-rc3.md5
Please report any issues if you find them.
Cheers, Matt
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
-- Antonio Hernández Blas | Oaxaca, México, Mx. https://github.com/nihilismus | https://bitbucket.org/nihilismus | https://twitter.com/nihilipster
Hi. The current core/libmpfr source's server is not responding by http at this moment but you can find the tarball at: http://ftp.gnu.org/gnu/mpfr/mpfr-${version%-*}.tar.xz On Fri, Oct 30, 2015 at 8:16 AM, Matt Housh <jaeger@morpheus.net> wrote:
Greetings,
CRUX 3.2-rc3 is now available for testing. rc2 was flawed and we'll forget it ever happened.
http://jaeger.morpheus.net/linux/crux/files/rc/crux-3.2-rc3.iso http://jaeger.morpheus.net/linux/crux/files/rc/crux-3.2-rc3.md5
Please report any issues if you find them.
Cheers, Matt
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
-- Antonio Hernández Blas | Oaxaca, México, Mx. https://github.com/nihilismus | https://bitbucket.org/nihilismus | https://twitter.com/nihilipster
Ramon, sou o druid_droid no #crux do freenode se tiveres noutra sala diz...
participants (6)
-
Alan Mizrahi -
Antonio Hernández Blas -
Fredrik Rinnestam -
Juergen Daubert -
Matt Housh -
Silvino Silva