Re: PKGSUFFIX for poudriere Help needed
Thanks that gives me a real good starting point. On Thu, Jan 9, 2020 at 8:02 AM Mathieu Arnold wrote: > On Wed, Jan 08, 2020 at 12:37:55PM -0500, Nick Wolff wrote: > > I'm trying to get zstd packages built locally with poudriere but > something > > is failing. I've set PKGSUFFIX=.tzst in my make.conf for the branch and > it > > shows up in poudriere logs > > ( /usr/local/etc/poudriere.d/ixlab-master-make.conf ) > > > > But I'm still getting txz packages. > > I've successfully used PKG_NOCOMPRESS in make.conf. and not sure what I'm > > doing wrong here. > > PKG_NOCOMPRESS is the knob used to swtich from .txz to .tar, so that it > is not compressed. > > If you want to change the compression, you probably have to do this, in > make.conf: > > PKG_SUFX= .tzst > > in poudriere.conf: > > PKG_REPO_META_FILE=/usr/local/etc/poudriere.d/meta > > And create that file with this content: > > version = 1; > packing_format = "tzst"; > > You may have to fiddle with the packing_format, I don't know what the > exact string is. > > -- > Mathieu Arnold > ___ 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"
sed failed: backup file same as original
Can anyone tell me which sense this warning has? Warning: Possible REINPLACE_CMD issues sed failed: backup file same as original:.. ___ 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: sed failed: backup file same as original
Ok, got my wires crossed. I understand it. ___ 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: Retiring GNU objdump 2.17.50
On 09/01/20 12:56, Konstantin Belousov wrote: On Thu, Jan 09, 2020 at 10:31:55AM -0500, Ed Maste wrote: We currently install and use at most three tools from GNU binutils 2.17.50, depending on target architecture: 1. as - assembler 2. ld - linker 3. objdump - diagnostic / information tool I hope to retire all use of these obsolete binutils before FreeBSD 13. Here I'd like to discuss objdump. It is a diagnostic tool that provides information about object files, binaries and libraries. It's not required as a bootstrap tool (i.e., not needed to build FreeBSD world or kernel). It is required to build a limited number of ports, and is used by some developers. I have a tracking PR for GNU objdump's retirement open in PR 229046. https://bugs.freebsd.org/229046. There are two ways we can proceed with its retirement: 1. Remove it without replacement. Ports that need objdump to build will have to depend on the binutils package/port, and users who wish to use it will have to install it. Related links for this path: Ports exp-run: https://bugs.freebsd.org/212319 Patch review: https://reviews.freebsd.org/D7338 2. Install llvm-objdump in its place (perhaps via a symlink). llvm-objdump is broadly compatible in both command-line argument parsing and output format, but there are many small differences and it's not a full drop-in replacement. Related links for this path: Patch review: https://reviews.freebsd.org/D18307 I am interested in feedback on the preferred approach. Installing llvm's objdump has the advantage that for most use cases everything will "just work", but may also introduce subtle failures. IMO no. 1 is preferrable because we do not need to track differences, nor we need to explain them. Having to install binutils port is not a high cost, and if somebody needs details about binary at the level provided by objdump, including disassembler, she would need binutils port anyway. +1 -- Renato Botelho ___ 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: Retiring GNU objdump 2.17.50
On Thu, Jan 09, 2020 at 05:56:10PM +0200, Konstantin Belousov wrote: > On Thu, Jan 09, 2020 at 10:31:55AM -0500, Ed Maste wrote: > > We currently install and use at most three tools from GNU binutils > > 2.17.50, depending on target architecture: > > > > 1. as - assembler > > 2. ld - linker > > 3. objdump - diagnostic / information tool > > > > I hope to retire all use of these obsolete binutils before FreeBSD 13. > > Here I'd like to discuss objdump. It is a diagnostic tool that > > provides information about object files, binaries and libraries. It's > > not required as a bootstrap tool (i.e., not needed to build FreeBSD > > world or kernel). It is required to build a limited number of ports, > > and is used by some developers. > > > > I have a tracking PR for GNU objdump's retirement open in PR 229046. > > https://bugs.freebsd.org/229046. > > > > There are two ways we can proceed with its retirement: > > > > 1. Remove it without replacement. Ports that need objdump to build > > will have to depend on the binutils package/port, and users who wish > > to use it will have to install it. > > > > Related links for this path: > > Ports exp-run: https://bugs.freebsd.org/212319 > > Patch review: https://reviews.freebsd.org/D7338 > > > > 2. Install llvm-objdump in its place (perhaps via a symlink). > > llvm-objdump is broadly compatible in both command-line argument > > parsing and output format, but there are many small differences and > > it's not a full drop-in replacement. > > > > Related links for this path: > > Patch review: https://reviews.freebsd.org/D18307 > > > > I am interested in feedback on the preferred approach. Installing > > llvm's objdump has the advantage that for most use cases everything > > will "just work", but may also introduce subtle failures. > > IMO no. 1 is preferrable because we do not need to track differences, nor > we need to explain them. Having to install binutils port is not a high cost, > and if somebody needs details about binary at the level provided by objdump, > including disassembler, she would need binutils port anyway. I completly agree with kib here. Best regards, Bapt signature.asc Description: PGP signature
Re: net/liveMedia: rtsp on vlc is not working with liveMedia-2019.12.30,2
> I'm using vlc to play rtsp stream of an IP-camera as follows. > > % vlc rtsp://192.168.XXX.XXX:554/11 > > It was good working with liveMedia until liveMedia-2019.12.05,2. > I did 'pkg upgrade' and liveMEdia was upgraded to 2019.12.30,2, > it could not play rtsp stream any more. > 'pkg add -f /var/cache/pkg/liveMedia-2019.12.05,2.txz' makes > to be able to play rtsp stream again. We must update vlc ports. See bug 243263. -- Masachika ISHIZUKA ___ 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"
