Re: Are broken ports retested before performing scheduled removal?
On Thursday, May 14, 2020 1:24:17 AM CEST Edward Sanford Sutton, III wrote: > games/oneko was recently removed as it was marked broken due to being > unfetchable. I tried an old copy of the ports tree I had where it was > marked as such and `make fetch -DTRYBROKEN` succeeded. Was there an > error recorded for this and was it ever retested? Is this just a side > effect of having a failure and no maintainer? > If being removed as unfetchable, wouldn't a better MOVED entry be to > say it was unfetchable (for more than 6 months) instead of just broken > for more than 6 months? > Thanks for feedback I've recently asked myself the same question: multimedia/gpac-mp4box is flagged BROKEN=unfetchable DEPRECATED=Broken for more than 6 months multimedia/gpac-libgpac uses the same distfile from the same mirror and is not marked broken. I figured once a port is marked unfetchable, it will be deleted, even it is a transient failure. Of course, unless someone opens a bug report. ___ 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: Are broken ports retested before performing scheduled removal?
Am 16.05.20 um 10:44 schrieb Stefan Ehmann: > On Thursday, May 14, 2020 1:24:17 AM CEST Edward Sanford Sutton, III wrote: >> games/oneko was recently removed as it was marked broken due to being >> unfetchable. I tried an old copy of the ports tree I had where it was >> marked as such and `make fetch -DTRYBROKEN` succeeded. Was there an >> error recorded for this and was it ever retested? Is this just a side >> effect of having a failure and no maintainer? >> If being removed as unfetchable, wouldn't a better MOVED entry be to >> say it was unfetchable (for more than 6 months) instead of just broken >> for more than 6 months? >> Thanks for feedback > > I've recently asked myself the same question: > > multimedia/gpac-mp4box is flagged > BROKEN=unfetchable > DEPRECATED=Broken for more than 6 months > > multimedia/gpac-libgpac uses the same distfile from the same mirror and is not > marked broken. > > I figured once a port is marked unfetchable, it will be deleted, even it is a > transient failure. Of course, unless someone opens a bug report. I have also had to resurrect ports that had been deleted as unfetchable (and which were prerequisites of ports I was working on) and found that they were either available from the MASTER_SITE given in the port (i.e., have most probably been only temporarily unavailablet) or had been moved to Github (or some other repository) and now have better accessibility than before, after an update of the ports' master sites. IMHO, it shows disrespect to the creator or maintainer of a port, if it is marked broken and deleted, in such a case, especially since there is no guarantee that the maintainer receives a notification for ports marked broken (for any reason, often easily fixed, but noted only when the port is deleted if the maintainer has no need to update or rebuild it during the time of deprecation). Regards, STefan ___ 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 +-+ graphics/py-glfw| 1.11.0 | 1.11.1 +-+ net/grpcurl | 1.4.0 | v1.6.0 +-+ 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 Reported by:portscout! ___ 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"
Build error net/librsync (unable to find library -lpopt)
Problems building net/librsync, please advice :-) Looking forward to having duplicity installed! :) # uname -a FreeBSD core24.grimstveit.no 12.1-RELEASE-p5 FreeBSD 12.1-RELEASE-p5 3135379a043(releng/12.1) CORE24 amd64 `make` in /usr/ports/net/librsync gives me this error: [29/69] /usr/bin/cc -Drsync_EXPORTS -Isrc -I/usr/ports/net/librsync/work/librsync-2.3.0/src -I/usr/local/include -I/usr/ports/net/librsync/work/librsync-2.3.0/src/blake2 -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -Wall -std=c99 -pedantic -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -fPIC -fvisibility=hidden -MD -MT CMakeFiles/rsync.dir/src/emit.c.o -MF CMakeFiles/rsync.dir/src/emit.c.o.d -o CMakeFiles/rsync.dir/src/emit.c.o -c /usr/ports/net/librsync/work/librsync-2.3.0/src/emit.c [30/69] /usr/bin/cc -Drsync_EXPORTS -Isrc -I/usr/ports/net/librsync/work/librsync-2.3.0/src -I/usr/local/include -I/usr/ports/net/librsync/work/librsync-2.3.0/src/blake2 -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -Wall -std=c99 -pedantic -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -fPIC -fvisibility=hidden -MD -MT CMakeFiles/rsync.dir/src/fileutil.c.o -MF CMakeFiles/rsync.dir/src/fileutil.c.o.d -o CMakeFiles/rsync.dir/src/fileutil.c.o -c /usr/ports/net/librsync/work/librsync-2.3.0/src/fileutil.c [31/69] /usr/bin/cc -Drsync_EXPORTS -Isrc -I/usr/ports/net/librsync/work/librsync-2.3.0/src -I/usr/local/include -I/usr/ports/net/librsync/work/librsync-2.3.0/src/blake2 -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -Wall -std=c99 -pedantic -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -fPIC -fvisibility=hidden -MD -MT CMakeFiles/rsync.dir/src/hashtable.c.o -MF CMakeFiles/rsync.dir/src/hashtable.c.o.d -o CMakeFiles/rsync.dir/src/hashtable.c.o -c /usr/ports/net/librsync/work/librsync-2.3.0/src/hashtable.c [32/69] /usr/bin/cc -Drsync_EXPORTS -Isrc -I/usr/ports/net/librsync/work/librsync-2.3.0/src -I/usr/local/include -I/usr/ports/net/librsync/work/librsync-2.3.0/src/blake2 -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -Wall -std=c99 -pedantic -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -fPIC -fvisibility=hidden -MD -MT CMakeFiles/rsync.dir/src/hex.c.o -MF CMakeFiles/rsync.dir/src/hex.c.o.d -o CMakeFiles/rsync.dir/src/hex.c.o -c /usr/ports/net/librsync/work/librsync-2.3.0/src/hex.c [33/69] /usr/bin/cc -Drsync_EXPORTS -Isrc -I/usr/ports/net/librsync/work/librsync-2.3.0/src -I/usr/local/include -I/usr/ports/net/librsync/work/librsync-2.3.0/src/blake2 -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -Wall -std=c99 -pedantic -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -fPIC -fvisibility=hidden -MD -MT CMakeFiles/rsync.dir/src/job.c.o -MF CMakeFiles/rsync.dir/src/job.c.o.d -o CMakeFiles/rsync.dir/src/job.c.o -c /usr/ports/net/librsync/work/librsync-2.3.0/src/job.c [34/69] /usr/bin/cc -Drsync_EXPORTS -Isrc -I/usr/ports/net/librsync/work/librsync-2.3.0/src -I/usr/local/include -I/usr/ports/net/librsync/work/librsync-2.3.0/src/blake2 -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -Wall -std=c99 -pedantic -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -fPIC -fvisibility=hidden -MD -MT CMakeFiles/rsync.dir/src/mdfour.c.o -MF CMakeFiles/rsync.dir/src/mdfour.c.o.d -o CMakeFiles/rsync.dir/src/mdfour.c.o -c /usr/ports/net/librsync/work/librsync-2.3.0/src/mdfour.c [35/69] /usr/bin/cc -Drsync_EXPORTS -Isrc -I/usr/ports/net/librsync/work/librsync-2.3.0/src -I/usr/local/include -I/usr/ports/net/librsync/work/librsync-2.3.0/src/blake2 -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -Wall -std=c99 -pedantic -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -fPIC -fvisibility=hidden -MD -MT CMakeFiles/rsync.dir/src/mksum.c.o -MF CMakeFiles/rsync.dir/src/mksum.c.o.d -o CMakeFiles/rsync.dir/src/mksum.c.o -c /usr/ports/net/librsync/work/librsync-2.3.0/src/mksum.c [36/69] /usr/bin/cc -Drsync_EXPORTS -Isrc -I/usr/ports/net/librsync/work/librsync-2.3.0/src -I/usr/local/include -I/usr/ports/net/librsync/work/librsync-2.3.0/src/blake2 -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -Wall -std=c99 -pedantic -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -fPIC -fvisibility=hidden -MD -MT CMakeFiles/rsync.dir/src/msg.c.o -MF CMakeFiles/rsync.dir/src/msg.c.o.d -o CMakeFiles/rsync.dir/src/msg.c.o -c /usr/ports/net/librsync/work/librsync-2.3.0/src/msg.c [37/69] /usr/bin/cc -Drsync_EXPORTS -Isrc -I/usr/ports/net/librsync/work/librsync-2.3.0/src -I/usr/local/include -I/usr/ports/net/librsync/work/librsync-2.3.0/src/blake2 -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -Wall -std=c99 -pedantic -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -fPIC -fvisibility=hidden -MD -MT CMakeFiles/rsync.dir/src/netint.c.o -MF CMakeFiles/rsync.dir/src/netint.c.o.d -o CMakeFiles/rsync.dir/src/netint.c.o -c /usr/ports/net/librsync/work/librsync-2.3.0/src/netint.c [38/69] /usr/bin/cc -Drsync_EXPORTS -Isrc -I/usr/port
Re: net/librsync does not build
Hi, I seem to have the same problem - did you find a solution? -- Vyrdsam helsing, Jakob Breivik Grimstveit | +47 482 98 152 http://grimstveit.no/jakob tor. 23. apr. 2020 kl. 18:54 skrev Xavier Humbert : > Hi, > > net/librsync apparently can't find libpopt : > > > [root@numenor librsync]# MAKE_JOBS_UNSAFE=yes make > > ===> Building for librsync-2.3.0 > > [1/1] : && /usr/bin/cc -O2 -pipe -g -march=core2 -fstack-protector-strong > > -fno-strict-aliasing -Wall -std=c99 -pedantic -O2 -pipe -g -march=core2 > > -fstack-protector-strong -fno-strict-aliasing -fstack-protector-strong > > CMakeFiles/rdiff.dir/src/rdiff.c.o > CMakeFiles/rdiff.dir/src/isprefix.c.o > > -o rdiff -Wl,-rpath,/usr/ports/net/librsync/work/.build: > > librsync.so.2.3.0 -lpopt && : > > FAILED: rdiff > > : && /usr/bin/cc -O2 -pipe -g -march=core2 -fstack-protector-strong > > -fno-strict-aliasing -Wall -std=c99 -pedantic -O2 -pipe -g -march=core2 > > -fstack-protector-strong -fno-strict-aliasing -fstack-protector-strong > > CMakeFiles/rdiff.dir/src/rdiff.c.o > CMakeFiles/rdiff.dir/src/isprefix.c.o > > -o rdiff -Wl,-rpath,/usr/ports/net/librsync/work/.build: > > librsync.so.2.3.0 -lpopt && : > > ld: error: unable to find library -lpopt > > cc: error: linker command failed with exit code 1 (use -v to see > > invocation) > > ninja: build stopped: subcommand failed. > > *** Error code 1 > > > > Stop. > > make: stopped in /usr/ports/net/librsync > > > However : > > > [root@numenor librsync]# ll /usr/local/lib/libpopt.* > > -rw-r--r-- 1 root wheel 73960 Apr 19 02:58 /usr/local/lib/libpopt.a > > lrwxr-xr-x 1 root wheel 16 Apr 19 02:58 > > /usr/local/lib/libpopt.so@ -> libpopt.so.0.0.0 > > lrwxr-xr-x 1 root wheel 16 Apr 19 02:58 > > /usr/local/lib/libpopt.so.0@ -> libpopt.so.0.0.0 > > -rwxr-xr-x 1 root wheel 56832 Apr 19 02:58 > > /usr/local/lib/libpopt.so.0.0.0* > What is the problem ? > > Thxs > > Regards > > Xavier > > -- > Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer > > ___ > 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: Build error net/librsync (unable to find library -lpopt)
Hi! > Problems building net/librsync, please advice :-) > > Looking forward to having duplicity installed! :) Please try to use poudriere to build it. I tested it, works fine. -- p...@opsec.eu+49 171 3101372Now what ? ___ 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: Build error net/librsync (unable to find library -lpopt)
Am 16.05.20 um 16:05 schrieb Kurt Jaeger:
> Hi!
>
>> Problems building net/librsync, please advice :-)
>>
>> Looking forward to having duplicity installed! :)
> Please try to use poudriere to build it. I tested it, works fine.
>
Kurt,
That's reaching too short. I can see that it build in poudriere, but it
appears to do something differently from a live system:
> ===> Performing out-of-source build
> -/bin/mkdir -p /usr/ports.svn/net/librsync/work/.build
> +/bin/mkdir -p /wrkdirs/usr/ports/net/librsync/work/.build
> -- The C compiler identification is Clang 8.0.1
> -- Check for working C compiler: /usr/local/libexec/ccache/cc
> -- Check for working C compiler: /usr/local/libexec/ccache/cc - works
> [...]
> --- CMAKE_SYSTEM = FreeBSD-12.1-RELEASE-p5
> +-- CMAKE_SYSTEM = FreeBSD-12.1-RELEASE-p4
> +-- Found POPT: /usr/local/lib/libpopt.so
> -- Found components for POPT
> -- POPT_ROOT_DIR = /usr/local
> -- POPT_INCLUDE_DIRS = /usr/local/include
> --- POPT_LIBRARIES = popt
> +-- POPT_LIBRARIES = /usr/local/lib/libpopt.so
> -- Found BZip2: /usr/lib/libbz2.so (found version "1.0.8")
> -- Looking for BZ2_bzCompressInit
> -- Looking for BZ2_bzCompressInit - found
And the POPT_LIBRARIES=... difference is breaking the build. Adding
LDFLAGS+=-L${LOCALBASE}/lib fixes the ports build for me. Now let's go
for the root cause...
___
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"
LLVM target 'amdgpu' not enabled Was: Re: Conflict on very first port (xorg) on rpi3
Deinstalling the conflicting port made considerable progress toward a build of x11/xorg, but now make is stopping with: configure: error: LLVM target 'amdgpu' not enabled in your LLVM build. Required by radv. I've tried turning off Wayland support in graphics/mesa-dri but that didn't help. Since this is on a Raspberry Pi3B, one wouldn't really expect to find an AMD GPU, If there's a workaround please give me a hint Thanks for reading, bob prohaska ___ 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: LLVM target 'amdgpu' not enabled Was: Re: Conflict on very first port (xorg) on rpi3
On 16 May 2020, at 17:44, bob prohaska wrote: > > Deinstalling the conflicting port made considerable progress toward a build of > x11/xorg, but now make is stopping with: > > configure: error: LLVM target 'amdgpu' not enabled in your LLVM build. > Required by radv. > > I've tried turning off Wayland support in graphics/mesa-dri but that didn't > help. > > Since this is on a Raspberry Pi3B, one wouldn't really expect to find an AMD > GPU, > > If there's a workaround please give me a hint It seems to be required by the ATI/AMD Radeon drivers, and there is no option to turn these drivers off, as far as I can see. You could attempt to edit graphics/mesa-dri/Makefile, and fiddle with the ALL_DRI_DRIVERS, ALL_GALLIUM_DRIVERS and ALL_VULKAN_DRIVERS lines. But this is going to be very fragile, the best solution is really to rebuild the llvm port with AMDGPU support. -Dimitry signature.asc Description: Message signed with OpenPGP
Re: Build error net/librsync (unable to find library -lpopt)
Am 16.05.20 um 17:13 schrieb Matthias Andree:
> Am 16.05.20 um 16:05 schrieb Kurt Jaeger:
>> Hi!
>>
>>> Problems building net/librsync, please advice :-)
>>>
>>> Looking forward to having duplicity installed! :)
>> Please try to use poudriere to build it. I tested it, works fine.
>>
> Kurt,
>
> That's reaching too short. I can see that it build in poudriere, but it
> appears to do something differently from a live system:
>
>> ===> Performing out-of-source build
>> -/bin/mkdir -p /usr/ports.svn/net/librsync/work/.build
>> +/bin/mkdir -p /wrkdirs/usr/ports/net/librsync/work/.build
>> -- The C compiler identification is Clang 8.0.1
>> -- Check for working C compiler: /usr/local/libexec/ccache/cc
>> -- Check for working C compiler: /usr/local/libexec/ccache/cc - works
>> [...]
>> --- CMAKE_SYSTEM = FreeBSD-12.1-RELEASE-p5
>> +-- CMAKE_SYSTEM = FreeBSD-12.1-RELEASE-p4
>> +-- Found POPT: /usr/local/lib/libpopt.so
>> -- Found components for POPT
>> -- POPT_ROOT_DIR = /usr/local
>> -- POPT_INCLUDE_DIRS = /usr/local/include
>> --- POPT_LIBRARIES = popt
>> +-- POPT_LIBRARIES = /usr/local/lib/libpopt.so
>> -- Found BZip2: /usr/lib/libbz2.so (found version "1.0.8")
>> -- Looking for BZ2_bzCompressInit
>> -- Looking for BZ2_bzCompressInit - found
> And the POPT_LIBRARIES=... difference is breaking the build. Adding
> LDFLAGS+=-L${LOCALBASE}/lib fixes the ports build for me. Now let's go
> for the root cause...
>
> ___
> 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"
Update:
(sunpoet@ I hope you don't mind my fixing your port)
- we've had an older bug report from 2020-04-10,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245514
- Franco Fichtner had provided a similar fix as of 2020-04-29,
the maintainer (sunpoet@, on Cc:) hadn't responded since,
so I was permitted to commit; fix committed in r535475.
You can tell that you have the current version if after update
you can see a ${CHMOD} near pre-test: at the end of
net/librsync/Makefile.
- upstream bug report filed against what I believe to be the culprit,
the upstream file cmake/FindPOPT.cmake seems to be broken
in case pkgconf or pkg-config or equivalent are found
during "make configure" (i. e. while cmake is running).
HTH.
If not, please reopen and follow up on Bug 245514 above.
Regards
Matthias
___
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: LLVM target 'amdgpu' not enabled Was: Re: Conflict on very first port (xorg) on rpi3
On Sat, May 16, 2020 at 06:08:13PM +0200, Dimitry Andric wrote: > On 16 May 2020, at 17:44, bob prohaska wrote: > > > > Deinstalling the conflicting port made considerable progress toward a build > > of > > x11/xorg, but now make is stopping with: > > > > configure: error: LLVM target 'amdgpu' not enabled in your LLVM build. > > Required by radv. > > > > I've tried turning off Wayland support in graphics/mesa-dri but that didn't > > help. > > > > Since this is on a Raspberry Pi3B, one wouldn't really expect to find an > > AMD GPU, > > > > If there's a workaround please give me a hint > > It seems to be required by the ATI/AMD Radeon drivers, and there is no > option to turn these drivers off, as far as I can see. You could attempt > to edit graphics/mesa-dri/Makefile, and fiddle with the ALL_DRI_DRIVERS, > ALL_GALLIUM_DRIVERS and ALL_VULKAN_DRIVERS lines. But this is going to > be very fragile, the best solution is really to rebuild the llvm port > with AMDGPU support. > > -Dimitry > Is it known what driver the Pi3B will use? That would at least tell me what to keep, though I appreciate it might not be enough for internal consistency. Quite a few failed attempts will be faster than rebuilding llvm80 Thanks for writing! bob prohaska ___ 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"
vscode and extensions
Hi All, I've just installed at FreeBSD-12.1 vscode-1.43.1 and the MS C/C++ extension. Seems that it doesn't work. And I've noticed at ~/.vscode-oss/extensions/ms-vscode.cpptools-0.28.0 Windows binaries. Should extensions work at FreeBSD? -- WBR, bsam ___ 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: Build error net/librsync (unable to find library -lpopt)
Much appreciated, fix works great, now able to install duplicity without
any problems 😎👍🏻
lør. 16. mai 2020 kl. 18:10 skrev Matthias Andree :
> Am 16.05.20 um 17:13 schrieb Matthias Andree:
> > Am 16.05.20 um 16:05 schrieb Kurt Jaeger:
> >> Hi!
> >>
> >>> Problems building net/librsync, please advice :-)
> >>>
> >>> Looking forward to having duplicity installed! :)
> >> Please try to use poudriere to build it. I tested it, works fine.
> >>
> > Kurt,
> >
> > That's reaching too short. I can see that it build in poudriere, but it
> > appears to do something differently from a live system:
> >
> >> ===> Performing out-of-source build
> >> -/bin/mkdir -p /usr/ports.svn/net/librsync/work/.build
> >> +/bin/mkdir -p /wrkdirs/usr/ports/net/librsync/work/.build
> >> -- The C compiler identification is Clang 8.0.1
> >> -- Check for working C compiler: /usr/local/libexec/ccache/cc
> >> -- Check for working C compiler: /usr/local/libexec/ccache/cc - works
> >> [...]
> >> --- CMAKE_SYSTEM = FreeBSD-12.1-RELEASE-p5
> >> +-- CMAKE_SYSTEM = FreeBSD-12.1-RELEASE-p4
> >> +-- Found POPT: /usr/local/lib/libpopt.so
> >> -- Found components for POPT
> >> -- POPT_ROOT_DIR = /usr/local
> >> -- POPT_INCLUDE_DIRS = /usr/local/include
> >> --- POPT_LIBRARIES = popt
> >> +-- POPT_LIBRARIES = /usr/local/lib/libpopt.so
> >> -- Found BZip2: /usr/lib/libbz2.so (found version "1.0.8")
> >> -- Looking for BZ2_bzCompressInit
> >> -- Looking for BZ2_bzCompressInit - found
> > And the POPT_LIBRARIES=... difference is breaking the build. Adding
> > LDFLAGS+=-L${LOCALBASE}/lib fixes the ports build for me. Now let's go
> > for the root cause...
> >
> > ___
> > 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"
>
> Update:
>
> (sunpoet@ I hope you don't mind my fixing your port)
>
> - we've had an older bug report from 2020-04-10,
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245514
>
> - Franco Fichtner had provided a similar fix as of 2020-04-29,
> the maintainer (sunpoet@, on Cc:) hadn't responded since,
> so I was permitted to commit; fix committed in r535475.
> You can tell that you have the current version if after update
> you can see a ${CHMOD} near pre-test: at the end of
> net/librsync/Makefile.
>
> - upstream bug report filed against what I believe to be the culprit,
> the upstream file cmake/FindPOPT.cmake seems to be broken
> in case pkgconf or pkg-config or equivalent are found
> during "make configure" (i. e. while cmake is running).
>
> HTH.
>
> If not, please reopen and follow up on Bug 245514 above.
>
> Regards
> Matthias
>
>
> --
--
Jakob Breivik Grimstveit
48298152 / http://grimstveit.no/jakob
___
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: vscode and extensions
On 2020-05-16 13:32, Boris Samorodov wrote: > Hi All, > > I've just installed at FreeBSD-12.1 vscode-1.43.1 and > the MS C/C++ extension. Seems that it doesn't work. > And I've noticed at ~/.vscode-oss/extensions/ms-vscode.cpptools-0.28.0 > Windows binaries. > > Should extensions work at FreeBSD? > Bookmarks, clangd, Cmake Tools and Python extensions all work fine here. 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"
