Re: FreeBSD Port: RetroArch-1.3.6_7
2017-08-24 6:49 GMT+02:00 Kevin Oberman : > Are you building with the default options? fmpeg has about as many options > as any port and they increase as new codecs, multiplexers, and such are > developed. It may be some non-standard selection that is causing your > problem. It built for me with MY options just fine. (11-stable on amd64). > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkober...@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 Yes, I usually never change any option, I use poudriere which does batch building anyway. -- Demelier David ___ 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: RetroArch-1.3.6_7
On Wed, Aug 23, 2017 at 9:38 PM, wrote: > On Wed, 2017-08-23 at 07:23 -0700, Ultima wrote: > > Are you positive ffmpeg is the issue? I just did a clean build on > > 110amd64 and 12 current and ffmpeg built just fine. Also build fairly > > recent (less than a week) on the other releases/tier 1 arch. > > Weird, I've pulled the ports source tree yesterday and it still did not > build with the same error. I'll double check. > > But for now I'll disable temporarily the ffmpeg dependency to update > the port :) > > Regards, > > -- > David > Are you building with the default options? fmpeg has about as many options as any port and they increase as new codecs, multiplexers, and such are developed. It may be some non-standard selection that is causing your problem. It built for me with MY options just fine. (11-stable on amd64). -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: RetroArch-1.3.6_7
On Wed, 2017-08-23 at 07:23 -0700, Ultima wrote: > Are you positive ffmpeg is the issue? I just did a clean build on > 110amd64 and 12 current and ffmpeg built just fine. Also build fairly > recent (less than a week) on the other releases/tier 1 arch. Weird, I've pulled the ports source tree yesterday and it still did not build with the same error. I'll double check. But for now I'll disable temporarily the ffmpeg dependency to update the port :) Regards, -- David ___ 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: Synth and circular dependencies
On 23 Aug, Thomas Mueller wrote: > But it seems more cumbersome with "make PORT_DBDIR=... showconfig" > than with "make show-options" and "make show depends-options" in > NetBSD with pkgsrc. Or maybe I'm spoiled? PORT_DBDIR= only needs to be specified if you want to point to somewhere other than the default location. Otherwise just "make showconfig" will suffice. ___ 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: Synth and circular dependencies
On 24 August 2017 at 11:12, Thomas Mueller wrote: >> > I can run "synth status ..." on desired packages to see before running if >> > the options are compatible. > >> My 2 cents worth: the port maintainers usually do a good job of >> choosing sensible default options. I would just move everything out of >> /var/db/ports/ and see what a "synth upgrade-system" comes back with. >> My LiveSystem-make.conf only contains a handful of lines where I >> disagree with the port maintainers' choices. > >> Cheers. > >> Jonathan Chen > > I could start from scratch on the options but not deleting packages already > installed. > > But it seems more cumbersome with "make PORT_DBDIR=... showconfig" than with > "make show-options" and "make show depends-options" in NetBSD with pkgsrc. > Or maybe I'm spoiled? > > Does synth look for options in /etc/make.conf, or only in > /usr/local/etc/synth/LiveSystem-make.conf ? synth doesn't look at /etc/make.conf. When it is building, it uses the options from /usr/local/etc/synth/LiveSystem-make.conf. > From "man synth" > > Port options directoryThis is the directory where all the selected >options for ports are cached. The initial >value comes from a system scan, so chances are >it has the correct value. However, if the user >would like a separate configuration area for >port options, they would create the new direc- >tory and set this value accordingly (but the >user would have to ensure the new location is >passed to the port when configuring port >options later in that case). > > Do the options have to be in /var/db/ports format, which I want to avoid at > all cost? Or is the LiveSystem-make.conf and /etc/make.conf good enough? synth will inspect the specified ports-options directory for options in /var/db/ports format. This allows new users to immediately use synth without having to configure anything. > Just to see what would happen, I don't think I need to run "synth > upgrade-system". "synth status" might be good enough. Yup, you're right. 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: Synth and circular dependencies
> > I can run "synth status ..." on desired packages to see before running if > > the options are compatible. > My 2 cents worth: the port maintainers usually do a good job of > choosing sensible default options. I would just move everything out of > /var/db/ports/ and see what a "synth upgrade-system" comes back with. > My LiveSystem-make.conf only contains a handful of lines where I > disagree with the port maintainers' choices. > Cheers. > Jonathan Chen I could start from scratch on the options but not deleting packages already installed. But it seems more cumbersome with "make PORT_DBDIR=... showconfig" than with "make show-options" and "make show depends-options" in NetBSD with pkgsrc. Or maybe I'm spoiled? Does synth look for options in /etc/make.conf, or only in /usr/local/etc/synth/LiveSystem-make.conf ? >From "man synth" Port options directoryThis is the directory where all the selected options for ports are cached. The initial value comes from a system scan, so chances are it has the correct value. However, if the user would like a separate configuration area for port options, they would create the new direc- tory and set this value accordingly (but the user would have to ensure the new location is passed to the port when configuring port options later in that case). Do the options have to be in /var/db/ports format, which I want to avoid at all cost? Or is the LiveSystem-make.conf and /etc/make.conf good enough? Just to see what would happen, I don't think I need to run "synth upgrade-system". "synth status" might be good enough. Tom ___ 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: qemu-aarch64-static
If you want to cross-compile, you need * a proper toolchain * a project that's enable to produce cross-compiled binaries On Tue, Aug 22, 2017 at 8:04 PM, Andrea Venturoli wrote: > On 08/22/17 18:03, Luca Pizzamiglio wrote: >> >> yes, the qemu emulation of other architecture means that the CPU is >> emulated by software, that's really expensive. >> You should consider around 10x slower or even more. ccache can help a >> lot in this case. > > > Thanks. > So you are confirming my poudriere is running an ARM compiler to produce ARM > code? I've played with cross-compile in the past and that's my understanding. > > What's the use of "-x" when creating a jail then? > What role does the "native cross-toolchain" play? The FreeBSD jail is built using a cross-toolchain (fast) and it contains "cross-binaries" (in case of ARM, in the jail you will have a compiler which host and target are ARM) The packages are built inside a "cross-jail" (slow) The problem is that external ports often don't support cross-compile, so instead of modify tons of ports to add cross-tollchain support, poudriere/FreeBSD exploit features offered by binmisc/qemu to build binaries in a emulated environment. The big drawback is the speed. > I understood that would mean running an AMD64 compiler to cross-build ARM > code... and thought that its timings would be comparable to native building. > Is that wrong? > > bye & Thanks > av. ___ 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: RetroArch-1.3.6_7
Err, sorry still waking up... s/ffmpeg/FreeBSD developers push changes without testing/ On Wed, Aug 23, 2017 at 7:23 AM, Ultima wrote: > Are you positive ffmpeg is the issue? I just did a clean build on 110amd64 > and 12 current and ffmpeg built just fine. Also build fairly recent (less > than a week) on the other releases/tier 1 arch. > > On Wed, Aug 23, 2017 at 5:03 AM, David Demelier > wrote: > >> 2017-07-11 10:02 GMT+02:00 bluesky : >> > Hello. The Retroarch port seems a bit out of date. Retroarch is on >> version >> > 1.6.0 now. >> >> Hi, >> >> I'm sorry I'm unable to update it at the moment because ffmpeg does >> not compile since many FreeBSD developers push changes without >> testing: >> >> https://lists.freebsd.org/pipermail/freebsd-ports/2017-July/109566.html >> >> I'll postpone that update once it has been fixed. >> >> -- >> Demelier David >> ___ >> 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-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: RetroArch-1.3.6_7
Are you positive ffmpeg is the issue? I just did a clean build on 110amd64 and 12 current and ffmpeg built just fine. Also build fairly recent (less than a week) on the other releases/tier 1 arch. On Wed, Aug 23, 2017 at 5:03 AM, David Demelier wrote: > 2017-07-11 10:02 GMT+02:00 bluesky : > > Hello. The Retroarch port seems a bit out of date. Retroarch is on > version > > 1.6.0 now. > > Hi, > > I'm sorry I'm unable to update it at the moment because ffmpeg does > not compile since many FreeBSD developers push changes without > testing: > > https://lists.freebsd.org/pipermail/freebsd-ports/2017-July/109566.html > > I'll postpone that update once it has been fixed. > > -- > Demelier David > ___ > 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-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: RetroArch-1.3.6_7
2017-07-11 10:02 GMT+02:00 bluesky : > Hello. The Retroarch port seems a bit out of date. Retroarch is on version > 1.6.0 now. Hi, I'm sorry I'm unable to update it at the moment because ffmpeg does not compile since many FreeBSD developers push changes without testing: https://lists.freebsd.org/pipermail/freebsd-ports/2017-July/109566.html I'll postpone that update once it has been fixed. -- Demelier David ___ 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 ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ devel/aws-sdk-cpp | 1.1.31 | 1.1.33 +-+ graphics/laternamagica | 0.4 | 0.5 +-+ lang/micropython| 1.5.1 | v1.9.2 +-+ multimedia/mkvalidator | 0.5.0 | 0.5.2 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ 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"