Re: Port upgrade: dead in the water

On Fri, Jan 15, 2021 at 10:00 PM Greg 'groggy' Lehey wrote: > > After years I have finally got round to upgrading my main computer. > My intention is to upgrade the ports as well, but pkg doesn't want to > play nice: > > # pkg-static install -f pkg > pkg-static: Warning: Major OS version

Re: [package - main-i386-default][sysutils/env4801] Failed for env4801-0.3_1 in build

On Tue, Jan 12, 2021 at 8:20 AM Patrick M. Hausen wrote: > > Dear ports gurus, > > what am I doing wrong that makes me still receive this message every couple > of days? > > > Von: pkg-fall...@freebsd.org > > Betreff: [package - main-i386-default][sysutils/env4801] Failed for > > env4801-0.3_1

Re: java/openjdk8 failed with "Undefined symbol "regcomp@FBSD_1.6""

8 > This is actually backwards, their bash port was built against a newer libc than they have on their system. This is odd, too, because the FBSD_1.6 version of this symbol predates r367712 by quite a bit. Something hinky is going on with their base system, but libc must be rebuilt

Re: Poudriere: Installing or updating jails fail with cp/utils.c error

_AUTO_OBJ logic), I am able to install and update my jails versions > 11.4 and 12.1 on Poudriere again. > Ah, my apologies for missing this report. :-( Indeed, that should be the end of that; it will get MFC'd in ~2 days to mitigate the issue on stable/12 since I MFC'd the breaking commit bac

Re: Patch compiler warnings away?

On Thu, Oct 1, 2020 at 4:12 PM Moritz Schmitt wrote: > > Hi, > > I recently took over my first maintainership of a port and I have a > question regarding on how to deal with compiler warnings. > > The port is devel/cscope and it seems to be in a rather good shape. It > contains the newest version

Re: math/reduce: could use some help with recent current failure

e to diagnose), so I wrote (then realized it was technically backported) the patch that upstream provided in late May [0] and committed that. This works out well because that can be MFH'd, then we can circle back on the update soon-ish. Patch was committed in r547124. Thanks, Kyle Evans [0] https

Re: Ports failing with -fno-common with clang 9/gcc 9

On Mon, Jun 22, 2020 at 1:35 AM Tobias Kortkamp wrote: > > On Thu, Apr 30, 2020, at 14:56, Kyle Evans wrote: > > In any event, I would urge folks to be proactive and identify this > > stuff, reporting issues upstream and spreading awareness of the > > impending default c

Re: Ports failing with -fno-common with clang 9/gcc 9

rlier than those commits, but no active releases will build with these patches applied. Folks can feel free to tag me in -fno-common related PRs if assistance is needed for any reason. Thanks, Kyle Evans ___ freebsd-ports@freebsd.org mailing list https://l

Re: FreeBSD Port: devel/py-subversion - Python 3 flavor?

n of this after python2 gets kicked out of the ports tree. Thanks, Kyle Evans ___ 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: [devel/arduino18] Adding a new board description.

On Tue, Mar 5, 2019 at 4:49 AM Peter Jeremy wrote: > > On 2019-Mar-04 08:36:52 -0600, Kyle Evans wrote: > >I'll find some time this week to see what I can do to bring the board > >manager back. It was removed when I initially ported Arduino 1.6.x > >because

Re: [devel/arduino18] Adding a new board description.

On Mon, Mar 4, 2019 at 4:37 AM Peter Jeremy wrote: > > I'm trying to use devel/arduino18 with a non-standard board - which > requires installing a new board description. According to the board > documentation, the process is to enter the URL for the new board > description in the Preferences,

Re: qemu-arm-static under amd64: example of stuck looping atomic_cmpset_int while building graphics/poppler-qt5 [a tested fix included]

On Wed, Jan 2, 2019 at 3:38 AM Mark Millard via freebsd-ports wrote: > > On 2019-Jan-1, at 18:43, Mark Millard wrote: > > > The below showed up for poudiere-devel bulk getting stuck using one FreeBSD > > cpu while building graphics/poppler-qt5 . This is not a kevent hang-up, > > unlike > > the

Re: Upgrade of security/openssl111 fails to install

On Wed, Nov 21, 2018 at 9:53 AM wrote: > > Hello, > > After upgrading my packages with poudriere, the updated version > (1.1.1.a) is not installed by pkg(8). Apparently, because of the > versioning, it's seen as a downgrade: > > root@teresa:~ # pkg upgrade > Updating poudriere-php56-openssl111

Re: qemu-arm-static: bsd-user/arm/target_syscall.h: #define TARGET_HW_MACHINE_ARCH "armv6" // what of armv7?

On Mon, Nov 12, 2018 at 10:41 PM Mark Millard wrote: > > 11.x: > o 11.2-STABLE armv6 BANANAPI > o 11.2-STABLE armv6 BEAGLEBONE > o 11.2-STABLE armv6 CUBIEBOARD > o 11.2-STABLE armv6 CUBIEBOARD2 > o 11.2-STABLE armv6 CUBOX-HUMMINGBOARD > o 11.2-STABLE armv6 RPI-B > o 11.2-STABLE armv6 RPI2 > o

Re: FYI: ports head -r484783 poudriere-devel with qemu-arm-static: sometimes hangs between a cc (wait) and its child ld (uwait)

h > time so far.] > > The following is just an FYI for the other > qemu-arm-static tied problem that I regularly run into. > I do not have much useful information so far. It is > not clear how I'd get such information. > Hi, Just so we're clear- in what kind of time frame did you start obser

Re: ports -r484565 : qemu-arm-static fails with: (start < end): backtrace included; start+len arithmetic overflow (abi_ulong wrap) for TARGET_FREEBSD_NR_mmap use

n > $8 = 0x236d000 > (gdb) print start+len > $9 = 37146624 > > And there is end's value again. > Hi, This should be fixed as of ports r484702; please do try this and let us know how it goes. Thanks, Kyle Evans ___ 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 -r484565 : qemu-arm-static fails with: (start < end): backtrace included; start+len arithmetic overflow (abi_ulong wrap) for TARGET_FREEBSD_NR_mmap use

On Sun, Nov 11, 2018 at 5:24 AM Mark Millard wrote: > > I attached with gdb in order to stop at the assert and look around. > > > > The following is a backtrace with notes and prints mixed in: > > (gdb) bt > #0 thr_kill () at thr_kill.S:3 > #1 0x6028a21f in __raise (s=6) at

Re: ports -r484565 : qemu-arm-static fails with: (start < end), function page_set_flags, file . . . accel/tcg/translate-all.c, line 2077

On Sat, Nov 10, 2018 at 4:30 PM Mark Millard wrote: > > On 2018-Nov-10, at 12:28, Kyle Evans wrote: > > > On Sat, Nov 10, 2018 at 11:38 AM Mark Millard via freebsd-ports > > wrote: > >> > >> Having actually installed the reverted code fist ( -r438807 ),

Recent patch(1) update

the beginning/end of a file. The fix was applied in base r326084; please test port updates with an updated patch(1) to avoid build failures on -HEAD. A sweep of the ports tree was done by portmgr@ to correct current cases of these candidate patches. Thanks, Kyle Evans

Re: Crashing chromium/iridium

For reference: there's been some escalation of this by asmodai@ (I think -- don't quote me on this): https://bugs.chromium.org/p/chromium/issues/detail? id=729534 -- asmodai@ was requesting some help in further debugging, but unfortunately does not seem to have received any help in that regard.

Re: [RFC] less patches: control the PATH

On Oct 6, 2017 8:24 AM, "Guido Falsi" wrote: On 10/06/2017 15:11, Baptiste Daroussin wrote: > Hi all, > > Here is a patch to add a new feature I am willing to get for a while: > https://reviews.freebsd.org/D12603 > A user can control which binary will be found in the PATH of

Re: Some github projects aren't fetchable using commit hash

On Sep 4, 2017 00:29, "Shane Ambler" wrote: For a port the distinfo will detect a hash and size difference of the tarball and fail. Yeah, but in the more general sense from a GitHub consumer point of view, I may not notice immediately and if the build process hasn't

Re: Some github projects aren't fetchable using commit hash

On Sep 1, 2017 20:03, "Shane Ambler" wrote: Respond to github support that an abbreviated hash with multiple matches will fail. Under that condition, it may be desirable to respond with the newest of the matches rather than a not found error. To be honest, the failing

Re: JAVA_VERSION???

On Fri, Jun 16, 2017 at 12:50 PM, Steve Kargl < s...@troutmask.apl.washington.edu> wrote: > > Kyle, > > Thanks. That patch fixes the problem with the spurious error > message. > > Excellent, I'll file a PR with this patch. You're using bsdgrep and

Re: JAVA_VERSION???

Yes, it appears to be a grep issue. In Mk/bsd.java.mk, I removed > the @ in line 227 to see what the test did. I then try to reproduce > just the part with grep (without the -q option) at a Bourne shell > prompt. > > # echo "1.7+" > 1.7+ >

Re: Licence practice for dependencies - making use of more restrictive licences optional

On Tue, Apr 25, 2017 at 11:07 PM, Dewayne Geraghty < dewaynegerag...@gmail.com> wrote: > The recent change to > https://svnweb.freebsd.org/ports/head/dns/opendnssec13/ > Makefile?view=markup=439426 which uses BSD3Clause, while gnugrep > uses GPLv3+; reminded me of a customer's requirement to

Re: recent change to vim defaults?

et nohl" if the new highlighted of search matches irritates as well. Thanks, Kyle Evans ___ 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: HEADSUP: FLAVORS (initial version) and subpackages proposals

On Mon, Dec 19, 2016 at 2:45 AM, Matthew Seaman wrote: > Why can't you have both flavoured and unflavoured variants of the same > port -- eg. devel/example as well as devel/example/foo and > devel/example/bar ? It seems like it would make sense to allow devel/example to be a

Re: private ports and pkgs versioning

On Tue, Oct 18, 2016 at 9:14 AM, Mark Linimon wrote: > On Tue, Oct 18, 2016 at 02:52:34PM +0100, Matthew Seaman wrote: >> Hmmm... looks like this is handled in the 30 or so lines starting at >> line 1179 of bsd.port.mk > > Wouldn't the patch to ports/Makefile just be the

Re: qa.sh stripped warning

Hi, On Wed, Oct 12, 2016 at 10:35 AM, Mathieu Arnold wrote: > The warning will never be turned into errors. Maybe add a comment to the > makefile saying that files must not be stripped. Maybe a bit like go > ports do it, something like: > > STRIP= # Elf firmwares, do not strip

qa.sh stripped warning

that there's a chance these warnings could eventually turn into errors, and I don't want this to be the case if it's not something that should be stripped. Thanks, Kyle Evans ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo

Re: Help wanted for new port: linking error in FreeCAD

On Thu, Aug 11, 2016 at 11:50 AM, Pedro Giffuni <p...@freebsd.org> wrote: > > > On 08/11/16 10:43, Kyle Evans wrote: >> >> On Thu, Aug 11, 2016 at 10:25 AM, Pedro Giffuni <p...@freebsd.org> wrote: >>> >>> Hello guys; >>> >>>

Re: Help wanted for new port: linking error in FreeCAD

org" Looks like a missing declared dependency of libCoin.so from graphics/Coin, which will likely/hopefully solve the problem -- graphics/Coin does include some pkgconfig magic. Thanks, Kyle Evans ___ freebsd-ports@freebsd.org mailing list https:/

Re: Asterisk port

On Thu, Jun 23, 2016 at 3:34 PM, Paul Pathiakis wrote: > Hi, > > The port for Asterisk software PBX is woefully out of date. The current > version is 2.x and the latest in ports/pkgs is 1.8. Version 1.8 is > DEPRECATED. > > Thank you! > > Paul Pathiakis In

Re: [CFT] net-im/ejabberd to 16.02

Hello! The updated port includes a ZLIB flag that seems to be used for inclusion/exclusion of the ezlib.* files, but ejabberd still attempts to load ezlib.app and fails to do so with the default setup. Am I missing something important here? Thanks, Kyle Evans -- --Kyle Evans