iperf checksums?
When trying to install iperf: ===>>> Waiting on fetch & checksum for benchmarks/iperf <<<=== fetch: https://freefr.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz: size mismatch: expected 370518, actual 373268 => Attempting to fetch https://jaist.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz fetch: https://jaist.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz: size mismatch: expected 370518, actual 373268 => Attempting to fetch https://nchc.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz fetch: https://nchc.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz: size mismatch: expected 370518, actual 373268 => Attempting to fetch https://netcologne.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz fetch: https://netcologne.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz: size mismatch: expected 370518, actual 373268 => Attempting to fetch https://netix.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz fetch: https://netix.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz: size mismatch: expected 370518, actual 373268 => Attempting to fetch https://superb-dca2.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz Over and over with identical numbers on slightly differ source forge servers. -- "Woof bloody woof." ___ 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: iperf checksums?
Hi The metadata are out of sync, just do a # pkg update -f On 11/10/20 11:37 AM, @lbutlr wrote: When trying to install iperf: ===>>> Waiting on fetch & checksum for benchmarks/iperf <<<=== fetch: https://freefr.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz: size mismatch: expected 370518, actual 373268 => Attempting to fetch https://jaist.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz fetch: https://jaist.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz: size mismatch: expected 370518, actual 373268 => Attempting to fetch https://nchc.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz fetch: https://nchc.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz: size mismatch: expected 370518, actual 373268 => Attempting to fetch https://netcologne.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz fetch: https://netcologne.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz: size mismatch: expected 370518, actual 373268 => Attempting to fetch https://netix.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz fetch: https://netix.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz: size mismatch: expected 370518, actual 373268 => Attempting to fetch https://superb-dca2.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz Over and over with identical numbers on slightly differ source forge servers. ___ 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: iperf checksums?
@lbutlr wrote: When trying to install iperf: ===>>> Waiting on fetch & checksum for benchmarks/iperf <<<=== fetch: https://freefr.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz: size mismatch: expected 370518, actual 373268 => Attempting to fetch https://jaist.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz fetch: https://jaist.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz: size mismatch: expected 370518, actual 373268 => Attempting to fetch https://nchc.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz fetch: https://nchc.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz: size mismatch: expected 370518, actual 373268 => Attempting to fetch https://netcologne.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz fetch: https://netcologne.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz: size mismatch: expected 370518, actual 373268 => Attempting to fetch https://netix.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz fetch: https://netix.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz: size mismatch: expected 370518, actual 373268 => Attempting to fetch https://superb-dca2.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz Over and over with identical numbers on slightly differ source forge servers. Looking at the commit log, it's not the first time distfile is being silently rerolled: commit 0fa0c820d6f179cf280a663437687f6fe1d4ab87 Author: Sunpoet Po-Chuan Hsieh Date: Sun Oct 4 14:12:56 2020 + Update distinfo: upstream rerolled the tarball - Bump PORTREVISION for package change Diff: https://people.FreeBSD.org/~sunpoet/iperf-2.0.14a.diff Looks like they did it again. ___ 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"
STOP rust!
Hi all! With latest ports tree librsvg2-rust-2.50.0 is required to some ports. It want replace librsvg2-2.40.21. I do not want build ugly rust during hours to build small lib in less than minute. Same with polkit & spidermonkey. https://gitlab.freedesktop.org/polkit/polkit/-/merge_requests/35 I remove polkit where it is possible. ___ 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: STOP rust!
Rozhuk Ivan wrote: Hi all! With latest ports tree librsvg2-rust-2.50.0 is required to some ports. It want replace librsvg2-2.40.21. I do not want build ugly rust during hours to build small lib in less than minute. You might want to send your complaints to librsvg authors, or fork the before-the-rust version and maintain it; ports list really seems to be a wrong target for this discussion. Same with polkit & spidermonkey. https://gitlab.freedesktop.org/polkit/polkit/-/merge_requests/35 I remove polkit where it is possible. ___ 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: STOP rust!
Rozhuk Ivan wrote: On Tue, 10 Nov 2020 20:01:55 +0300 Yuri Pankov wrote: Actually, it started quite some time ago, and it was 2.41 that introduced the rust dependency: https://mail.gnome.org/archives/desktop-devel-list/2017-January/msg1.html This does not explain why I should waste my time and money to compile ugly rust. You should ask librsvg developers then as I said in the first reply. P.S. please reply to the list, not to me directly, I'm not interested in unicast discussion and adding the list address back every time. ___ 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: STOP rust!
On Tue, 10 Nov 2020 16:38:26 +0300 Yuri Pankov wrote: > > With latest ports tree librsvg2-rust-2.50.0 is required to some > > ports. It want replace librsvg2-2.40.21. > > > > I do not want build ugly rust during hours to build small lib in > > less than minute. > > You might want to send your complaints to librsvg authors, or fork > the before-the-rust version and maintain it; ports list really seems > to be a wrong target for this discussion. > This done not by librsvg authors. https://reviews.freebsd.org/D18878 And "# Use librsvg2-rust where lang/rust is available" means that it is not required for all other arch. ___ 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: STOP rust!
On Tue, 10 Nov 2020 19:44:58 +0300 Yuri Pankov wrote: > >>> With latest ports tree librsvg2-rust-2.50.0 is required to some > >>> ports. It want replace librsvg2-2.40.21. > >>> > >>> I do not want build ugly rust during hours to build small lib in > >>> less than minute. > >> > >> You might want to send your complaints to librsvg authors, or fork > >> the before-the-rust version and maintain it; ports list really > >> seems to be a wrong target for this discussion. > >> > > > > This done not by librsvg authors. > > https://reviews.freebsd.org/D18878 > > > > And "# Use librsvg2-rust where lang/rust is available" means that > > it is not required for all other arch. > > It is done in the latest version of librsvg, namely 2.50, and > starting from that version rust is required to build (not to run > though, AFAIK). The arches on which FreeBSD doesn't have working rust > yet are to keep older version (2.40) for the moment, but that is only > temporary workaround as you might understand. I do not care that 2.50 > 2.40, I care only that it requires heavy dep. > BTW, `pkg install rust` should solve the "build ugly rust during > hours" problem for you. I use portmaster and do not want do some actions by hand, and pkg install may reinstall some of my apps. ___ 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: STOP rust!
On Tue, 10 Nov 2020 20:01:55 +0300 Yuri Pankov wrote: > Actually, it started quite some time ago, and it was 2.41 that > introduced the rust dependency: > > https://mail.gnome.org/archives/desktop-devel-list/2017-January/msg1.html This does not explain why I should waste my time and money to compile ugly rust. ___ 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"
Using gcc as a build dependency only
I have a port that, for reasons I won't go into, I build with gcc. It all works fine with USE_GCC= yes - no problem. The issue is that it's a build dependency and a run dependency. So anyone wanting to use it has to install gcc, and is discouraged because (a) it's big and (b) it drags in other stuff. Presumably this is because it needs the gcc runtime, but I'm not sure. And I can't see a runtime package that parallels the compiler. Can anyone comment on this? And please don't say 'convert to clang' because that isn't possible, at least not yet. ___ 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: Using gcc as a build dependency only
On 11/11/2020 7:55 am, Bob Eager wrote:
> I have a port that, for reasons I won't go into, I build with gcc.
>
> It all works fine with USE_GCC= yes - no problem.
>
> The issue is that it's a build dependency and a run dependency. So
> anyone wanting to use it has to install gcc, and is discouraged because
> (a) it's big and (b) it drags in other stuff.
>
> Presumably this is because it needs the gcc runtime, but I'm not sure.
> And I can't see a runtime package that parallels the compiler.
>
> Can anyone comment on this? And please don't say 'convert to clang'
> because that isn't possible, at least not yet.
> ___
> 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"
>
Hi Bob, I have faced the same dilemma. The process I use is to:
Install (tar) only the gcc files needed, usually
libstdc++.s*
libgcc_s*
You might need to consider the other tools that gcc uses (like
math/{gmp,mpc,mpfr}
and then add to /usr/ports/Mk/local.mk, I append:
RUN_DEPENDS:=${RUN_DEPENDS:Ngcc*}
BUILD_DEPENDS:=${BUILD_DEPENDS:Ngcc*}
I also have, but I'm unsure if this is still required
LIB_DEPENDS:=${LIB_DEPENDS:Ngcc*}
I hope someone has a better way?
Regards.
PS All my build, install, update processes are automated; so you'll need
something to track gcc (and friends) updates.
___
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: Using gcc as a build dependency only
On 11/11/2020 7:55 am, Bob Eager wrote: I have a port that, for reasons I won't go into, I build with gcc. It all works fine with USE_GCC= yes - no problem. The issue is that it's a build dependency and a run dependency. So anyone wanting to use it has to install gcc, and is discouraged because (a) it's big and (b) it drags in other stuff. Presumably this is because it needs the gcc runtime, but I'm not sure. And I can't see a runtime package that parallels the compiler. Can anyone comment on this? And please don't say 'convert to clang' because that isn't possible, at least not yet. This is being tracked in: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211154 ___ 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"
