Re: amd64->{armv7,aarc64} cross builds of devel/llvm10 (via poudriere-devel): failed in package stage for missing libarcher* files
Fixed in r526532. Thanks for the hint that it was in OPENMP. -- Brooks On Mon, Feb 17, 2020 at 08:19:26PM -0800, Mark Millard wrote: > On 2020-Feb-17, at 09:56, Mark Millard wrote: > > > On 2020-Feb-17, at 09:53, Mark Millard wrote: > > > >> [The native arm64 build worked fine. But the cross builds > >> got . . .] > >> > >> The builds failed with: > >> > >> > Compressing man pages (compress-man) > >> ===> Installing ldconfig configuration file > >> === > >> === > >> ===> Building package for llvm10-10.0.0.r1_1 > >> pkg-static: Unable to access file > >> /wrkdirs/usr/ports/devel/llvm10/work/stageusr/local/llvm10/lib/libarcher.so:No > >> such file or directory > >> pkg-static: Unable to access file > >> /wrkdirs/usr/ports/devel/llvm10/work/stageusr/local/llvm10/lib/libarcher_static.a:No > >> such file or directory > >> *** Error code 1 > >> > >> Stop. > >> make: stopped in /usr/ports/devel/llvm10 > >> =>> Cleaning up wrkdir > >> ===> Cleaning for llvm10-10.0.0.r1_1 > >> > >> > >> head -r3577979 based system source; head -r536339 based ports tree. > >> > > > > I forgot to list: > > > > ===> The following configuration options are available for > > llvm10-10.0.0.r1_1: > > BE_AMDGPU=on: AMD GPU backend (required by mesa) > > CLANG=on: Build clang > > DOCS=on: Build and/or install documentation > > EXTRAS=on: Extra clang tools > > LIT=on: Install lit and FileCheck test tools > > LLD=on: Install lld, the LLVM linker > > LLDB=on: Install lldb, the LLVM debugger > > LLD_LINK=on: Link ld.lld as ld to clang uses it > > PYCLANG=off: Install python bindings to libclang > > > Options available for the single BACKENDS: you have to select exactly > > one of them > > BE_FREEBSD=off: Backends for FreeBSD architectures > > BE_NATIVE=on: Backend(s) for this architecture (ARM) > > BE_STANDARD=off: All non-experimental backends > > > > > llvm10-10.0.0.r2 gets the same. > > I was curious what the libarcher* files would be tied to > and found that libarcher is a tool library for an llvm > openmp tool. > > But openmp does not seem to be available for armv7 or > aarch64 so the file is not expected to be present for > installation, much like libgomp.so , liniomp5.so , > libomp.so , and libomptarget.so . Looks like a > %%OPENMP%% prefix is needed in llvm10/pkg-plist for > each of the two libarcher lines. > > === > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) > signature.asc Description: PGP signature
Committer request for textproc/sigil update
Hi, Are there any committers available to take on a textproc/sigil update: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243965 It's just PORTVERSION and distinfo changes. Cheers. -- Jonathan Chen ___ 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: Starting with poudriere
Jose Quinteiro wrote on 2020/02/19 20:35: On 2020-02-15 20:43, Dan McGrath wrote: Probably not ideal since you generally want to disable the FreeBSD repository, and use only your poudriere repo, instead. You would need to build everything you intend to install in the jail, however. While I believe that you can enable multiple repositories (FreeBSD's, and your own poudriere one), I am not sure about repo priorities, or how you would deal with conflicts with build options that pull in common ports. It is something I have been meaning to look into, sorry! Perhaps someone else here can give some advice? You can set priorities for remote package repositories in the repo's conf file. The default priority is 0, which is lowest. I plan to set up a repo with the ports I build with poudriere at a higher priority. Are there concerns with this approach? I am using 2 or 3 repositories (all built with our poudriere) for some time. It works but the problem can be if some repo has different default versions. For example one repo has PostgreSQL 9.6 as default version for all dependencies and another repo has PostgreSQL 10. Then you need to carefully choose what to install from what repo. Miroslav Lachman ___ 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: Starting with poudriere
On 2020-02-15 20:43, Dan McGrath wrote: On Sat, Feb 15, 2020 at 11:03 PM @lbutlr wrote: Let’s say I want to build and install a single port via poudrier. For the same of argument some port that has configuration options I want to change. Probably not ideal since you generally want to disable the FreeBSD repository, and use only your poudriere repo, instead. You would need to build everything you intend to install in the jail, however. While I believe that you can enable multiple repositories (FreeBSD's, and your own poudriere one), I am not sure about repo priorities, or how you would deal with conflicts with build options that pull in common ports. It is something I have been meaning to look into, sorry! Perhaps someone else here can give some advice? You can set priorities for remote package repositories in the repo's conf file. The default priority is 0, which is lowest. I plan to set up a repo with the ports I build with poudriere at a higher priority. Are there concerns with this approach? Thanks, Jose ___ 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: Notifying maintainers when their port is labeled BROKEN would make a difference
Matthew Seaman writes: > On 18/02/2020 17:20, Yuri wrote: > >> Currently maintainers aren't notified when their ports are labeled broken. >> >> Adding broken ports to "Issues that need your attention" e-mails would >> make a difference. >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243271 >> >> Who can make this change? > > If you create yourself an account at freshports.org, then you can > arrange to be notified whenever one of your ports gets modified. > > I'd recommend doing this to anyone who is maintaining ports. Sounds like a subset of what herald rules in Phabricator can do i.e., https://reviews.freebsd.org/herald/ ___ 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"
