SOLVED (was Re: Ports with binary bootstrap packages and CURRENT+ino64)
On 01/24/18 19:37, Don Lewis wrote: > On 24 Jan, Anthony Jenkins via freebsd-ports wrote: >> On 01/04/18 12:15, Dmytro Bilokha wrote: >>> On Thu, Jan 04, 2018 at 03:31:46PM +0100, Jean-Sébastien Pédron wrote: On 03.01.2018 01:06, Anthony Jenkins wrote: > I'm having trouble building ports with a new Poudriere rig on a > 12.0-CURRENT (git commit 423586ee). The ports that fail are ones that > require a binary bootstrap package (e.g. lang/rust and java/openjdk8). > The executables in these bootstrap packages fail with a segfault as do > all executables build with a non-ino64 FreeBSD box. Like Jan, I'm surprised that it crashes. AFAIK, Rust builds fine in the official package building cluster, which is also running FreeBSD 12-CURRENT. I don't know what to suggest at this point, so I'll wait that you provide the information requested by Jan. >> Sorry for the reply delay - apparently I wasn't an actual member of the >> @ports mailing list, and I've had a bunch of stuff going on. >> >> I've been looking into the lang/rust problem, and it looks like the >> cargo binary is built against a pre-ino64 FreeBSD. The cargo binary >> comes from >> distfiles/rust/2017-10-12/cargo-0.22.0-x86_64-unknown-freebsd.tar.gz: >> >> [ajenkins@ajenkins-hplaptop /usr/ports/lang/rust]$ tar tvzf >> /usr/ports/distfiles/rust/2017-10-12/cargo-0.22.0-x86_64-unknown-freebsd.tar.gz >> | grep bin/cargo >> -rwxr-xr-x 0 2000 2000 14719904 Oct 9 18:21 >> cargo-0.22.0-x86_64-unknown-freebsd/cargo/bin/cargo >> >> This binary is not affected by the patch Jan referred to, AFAICT. I'm >> trying my hand at writing a wrapper for cargo that uses LD_PRELOAD to >> call a hand-rolled pre-ino64 stat() that calls the post-ino64 stat(). I >> have no idea how/why a 12-CURRENT system can build the lang/rust port - >> I have two CURRENT systems that fail to build it. Here's my OSVERSION >> variable: >> >> [ajenkins@ajenkins-hplaptop /usr/ports/lang/rust]$ make -v OSVERSION >> 1200053 >> >> This kicks in the patch, but I still have the issue. > I haven't seen this problem here. Are you running the GENERIC kernel or > a customized kernel? If the latter, does the configuration include the > COMPAT_FREEBSD* options? The bootstrap is probably compiled for an older > FreeBSD release, and if those options aren't present, then the syscall > emulation for the pre-ino64 syscall ABI probably won't be there. [ajenkins@ajenkins-hplaptop ~]$ grep COMPAT /usr/src/sys/amd64/conf/MYKERNEL options COMPAT_FREEBSD32 # Compatible with i386 binaries options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options COMPAT_FREEBSD7 # Compatible with FreeBSD7 options COMPAT_FREEBSD9 # Compatible with FreeBSD9 options COMPAT_FREEBSD10 # Compatible with FreeBSD10 Am I missing a COMPAT_FREEBSD11? I see it in the GENERIC config. I'll add that, rebuild the kernel and try again. GRRR that was it! It's building now on my laptop, I'll whip up a new kernel for my poudriere box I put together and see if that fixes this issue. Thanks for the help, sorry for the noise. Anthonuy ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
RE: py27 ports always show "new version available"
Hello. Probably, after the function validate_flavor was added (3.18_12), the result of portmaster -i cmake changed as follows. ===>>> The following actions will be taken if you choose to proceed: Re-install cmake-3.10.2 Re-install py27-sphinx-1.4.8_2,1 I think that the change from "Install textproc/py-sphinx" to "Re-install py27-sphinx-1.4.8_2,1" means that portmaster correctly recognized py27-sphinx is installed. And if portmaster avoids re-installing like other depend ports, it will be perfect. Thank you. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Ports with binary bootstrap packages and CURRENT+ino64
On 24 Jan, Anthony Jenkins via freebsd-ports wrote: > On 01/04/18 12:15, Dmytro Bilokha wrote: >> On Thu, Jan 04, 2018 at 03:31:46PM +0100, Jean-Sébastien Pédron wrote: >>> On 03.01.2018 01:06, Anthony Jenkins wrote: I'm having trouble building ports with a new Poudriere rig on a 12.0-CURRENT (git commit 423586ee). The ports that fail are ones that require a binary bootstrap package (e.g. lang/rust and java/openjdk8). The executables in these bootstrap packages fail with a segfault as do all executables build with a non-ino64 FreeBSD box. >>> >>> Like Jan, I'm surprised that it crashes. AFAIK, Rust builds fine in the >>> official package building cluster, which is also running FreeBSD >>> 12-CURRENT. >>> >>> I don't know what to suggest at this point, so I'll wait that you >>> provide the information requested by Jan. > > Sorry for the reply delay - apparently I wasn't an actual member of the > @ports mailing list, and I've had a bunch of stuff going on. > > I've been looking into the lang/rust problem, and it looks like the > cargo binary is built against a pre-ino64 FreeBSD. The cargo binary > comes from > distfiles/rust/2017-10-12/cargo-0.22.0-x86_64-unknown-freebsd.tar.gz: > > [ajenkins@ajenkins-hplaptop /usr/ports/lang/rust]$ tar tvzf > /usr/ports/distfiles/rust/2017-10-12/cargo-0.22.0-x86_64-unknown-freebsd.tar.gz > | grep bin/cargo > -rwxr-xr-x 0 2000 2000 14719904 Oct 9 18:21 > cargo-0.22.0-x86_64-unknown-freebsd/cargo/bin/cargo > > This binary is not affected by the patch Jan referred to, AFAICT. I'm > trying my hand at writing a wrapper for cargo that uses LD_PRELOAD to > call a hand-rolled pre-ino64 stat() that calls the post-ino64 stat(). I > have no idea how/why a 12-CURRENT system can build the lang/rust port - > I have two CURRENT systems that fail to build it. Here's my OSVERSION > variable: > > [ajenkins@ajenkins-hplaptop /usr/ports/lang/rust]$ make -v OSVERSION > 1200053 > > This kicks in the patch, but I still have the issue. I haven't seen this problem here. Are you running the GENERIC kernel or a customized kernel? If the latter, does the configuration include the COMPAT_FREEBSD* options? The bootstrap is probably compiled for an older FreeBSD release, and if those options aren't present, then the syscall emulation for the pre-ino64 syscall ABI probably won't be there. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Ports with binary bootstrap packages and CURRENT+ino64
On 01/04/18 12:15, Dmytro Bilokha wrote: > On Thu, Jan 04, 2018 at 03:31:46PM +0100, Jean-Sébastien Pédron wrote: >> On 03.01.2018 01:06, Anthony Jenkins wrote: >>> I'm having trouble building ports with a new Poudriere rig on a >>> 12.0-CURRENT (git commit 423586ee). The ports that fail are ones that >>> require a binary bootstrap package (e.g. lang/rust and java/openjdk8). >>> The executables in these bootstrap packages fail with a segfault as do >>> all executables build with a non-ino64 FreeBSD box. >> >> Like Jan, I'm surprised that it crashes. AFAIK, Rust builds fine in the >> official package building cluster, which is also running FreeBSD >> 12-CURRENT. >> >> I don't know what to suggest at this point, so I'll wait that you >> provide the information requested by Jan. Sorry for the reply delay - apparently I wasn't an actual member of the @ports mailing list, and I've had a bunch of stuff going on. I've been looking into the lang/rust problem, and it looks like the cargo binary is built against a pre-ino64 FreeBSD. The cargo binary comes from distfiles/rust/2017-10-12/cargo-0.22.0-x86_64-unknown-freebsd.tar.gz: [ajenkins@ajenkins-hplaptop /usr/ports/lang/rust]$ tar tvzf /usr/ports/distfiles/rust/2017-10-12/cargo-0.22.0-x86_64-unknown-freebsd.tar.gz | grep bin/cargo -rwxr-xr-x 0 2000 2000 14719904 Oct 9 18:21 cargo-0.22.0-x86_64-unknown-freebsd/cargo/bin/cargo This binary is not affected by the patch Jan referred to, AFAICT. I'm trying my hand at writing a wrapper for cargo that uses LD_PRELOAD to call a hand-rolled pre-ino64 stat() that calls the post-ino64 stat(). I have no idea how/why a 12-CURRENT system can build the lang/rust port - I have two CURRENT systems that fail to build it. Here's my OSVERSION variable: [ajenkins@ajenkins-hplaptop /usr/ports/lang/rust]$ make -v OSVERSION 1200053 This kicks in the patch, but I still have the issue. Anthony >> >> -- >> Jean-Sébastien Pédron >> > > Hi, guys! > > I have the same trouble with building java/openjdk8 with Poudriere: > > configure: Found potential Boot JDK using configure arguments > configure: Potential Boot JDK found at /usr/local/bootstrap-openjdk8 > is incorrect JDK version (Error occurred during initialization of VM); > ignoring > configure: (Your Boot JDK must be version 7 or 8) > configure: error: The path given by --with-boot-jdk does not contain a > valid Boot JDK > configure exiting with result code 1 > ===> Script "../../configure" failed unexpectedly. > > My version is 11.1-RELEASE-p4, so it is possible that the issue is not > specific for the 12.0-CURRENT. > I have an idea, that openjdk8 build process fails in a Poudriere jail, > because of not mounted fdescfs and procfs. I've tried to mount these > fs in the Poudriere jail, but failed. > ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: gifsicle-1.90
Hi! > Two issues with this port. > > * There is a new version of this upstream, gifsicle 1.91. [...] Which fixes security issues, btw! > * The default config for gifsicle is to include X11 (graphics) support. > With this option enabled, you get an additional application "/bin/gifview", [...] > I suggest that the port Makefile be modified so that OPTIONS_DEFAULT is > empty instead of containing X11. Both: Done. -- p...@opsec.eu+49 171 3101372 2 years to go ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD Port: gifsicle-1.90
Two issues with this port. * There is a new version of this upstream, gifsicle 1.91. * The default config for gifsicle is to include X11 (graphics) support. With this option enabled, you get an additional application "/bin/gifview", which simply lets you view a GIF file in X. This also pulls in a number of x11 dependencies. And, because this is the default FreeBSD config, it causes the package to be built dependent on X. libX11: 1.6.5,1 xproto: 7.0.31 libxcb: 1.12_2 libXdmcp: 1.1.2 libXau: 1.0.8_3 libpthread-stubs: 0.4 kbproto: 1.0.7 Most users DO NOT need this feature: gifsicle is primarily intended for use on servers as a means to lossless-optimize GIF images and save bandwidth. End users who need a gif viewer will almost certainly never use gifview provided by gifsicle, and instead simply use a web browser, or other image viewer. I suggest that the port Makefile be modified so that OPTIONS_DEFAULT is empty instead of containing X11. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
www/nginx patch failed
Hi, Possible, after update 3rd party modules this patch isn't needed anymore files/extra-patch-ngx_http_lua_common.h or should be actualized? [tiger@laptop]:/<2>www/nginx>make showconfig | grep -i lua LUA=on: 3rd party lua module ===> Cleaning for nginx-1.12.2_5,2 laptop# make ===> License BSD2CLAUSE accepted by the user ===> nginx-1.12.2_5,2 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by nginx-1.12.2_5,2 for building ===> Extracting for nginx-1.12.2_5,2 => SHA256 Checksum OK for nginx-1.12.2.tar.gz. => SHA256 Checksum OK for simpl-ngx_devel_kit-v0.3.0_GH0.tar.gz. => SHA256 Checksum OK for openresty-lua-nginx-module-v0.10.11_GH0.tar.gz. => SHA256 Checksum OK for openresty-set-misc-nginx-module-cda7e50_GH0.tar.gz. ===> Patching for nginx-1.12.2_5,2 ===> Applying extra patch /usr/ports/www/nginx/files/extra-patch-ngx_http_lua_common.h -- wbr, Sergey ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
