Re: ports/160273 and ports/160272
18.09.2011 04:36, Florian Smeets пишет: > Hi, > > now that AquaGatekeeper2 has been removed, do we still need AquaGatekeeper? > > I'm currently usure what to do with these PRs. I don't get why AquaGatekeeper2 in spite of PR fixing it: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/160273 That was mistake and it should be revived and fixed with the patch from the PR. Eugene Grosbein ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ports/160273 and ports/160272
18.09.2011 04:46, Eugene Grosbein пишет: > 18.09.2011 04:36, Florian Smeets пишет: >> Hi, >> >> now that AquaGatekeeper2 has been removed, do we still need AquaGatekeeper? >> >> I'm currently usure what to do with these PRs. > > I don't get why AquaGatekeeper2 in spite of PR fixing it: I don't get why AquaGatekeeper2 has been removed. > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/160273 > > That was mistake and it should be revived and fixed with the patch from the > PR. > > Eugene Grosbein ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: www/joomla3 port installs from GitHub, why?
20.05.2018 18:52, Per olof Ljungmark wrote: > I am curious as to why the www/joomla3 port installs from GitHub, looks > like the port is better for Joomla code development than to run a CMS. > > There are LOTS of files in the port install that is not needed to run > Joomla. > > I thought the recommended way is to fetch the latest version from > joomla.org: > > https://downloads.joomla.org/cms/joomla3/3-8-7/Joomla_3-8-7-Stable-Full_Package.zip?format=zip > > > Can someone please enlighten me here? You should ask port maintainer l...@freebsd.org (CC'd). ___ 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: www/joomla3 port installs from GitHub, why?
21.05.2018 2:02, Per olof Ljungmark wrote: >> I may look into changing it, but if you generate a patch, I'll look at it. > > Easiest way to understand what I mean is to compare the official download at > https://downloads.joomla.org/cms/joomla3/3-8-7/Joomla_3-8-7-Stable-Full_Package.zip?format=zip > (42MB unzipped) > > with the distfile from ports > joomla-joomla-cms-3.8.7_GH0.tar.gz (71MB unpacked) > > I never worked with the ports system so patching it for me would be too > much. However, if you do not have the time I may know someone here that > could do it. > > Again, I think the port in its current state is designed for people who > develop Joomla, not using it as a CMS like me. One should not compare official end-user package with source downloads because the port is supposed to build software from source and not install pre-built packages. However, you can legitimately compare official end-user packages with our package produced by the port, if you wish. ___ 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: Pause pkg install messages
On 24.05.2018 15:08, Johannes Lundberg wrote: > Hi > > The first thing me and probably many other do after install is > pkg install xxx yyy zzz > from console (meaning no scrollback buffer). > > With xorg and friends this means hundreds of packets. After install all the > pkg messages are display and most of sometimes very valuable information is > just scrolled away. > > Is there an easy way to fix* this by piping the output through less or > something to pause for each screen so that the messages just aren't > scrolled away? > > In addition to that it would be nice (if it's not already done) to store > this information in a log file somewhere so that one can revisit and see > what needs to be manually configured for each installed package. > > *by fix I mean something that does not put the burden on the user. Installation/deinstallation of packages logged by default to /var/log/messages. Syscons console has scrollback buffer by default. If vt(4) has not, that's regression after syscons and should be fixed in the vt. Also, one can have, for tcsh: alias pkg 'script -a /var/log/pkg.log pkg-static' So "pkg install xxx yyy zzz" adds fulls output to specified file. ___ 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: mail/thunderbird fails on link with latest security/nss
26.05.2018 18:18, Jonathan Chen пишет:
> Hi,
>
> With the recent update to security/nss, mail/thunderbird build
> currently fails on 11-STABLE/amd64 with:
>
> [...]
> Executing: /usr/bin/c++ -std=gnu++11 -o plugin-container
> -Qunused-arguments -D_GLIBCXX_USE_C99 -D_GLIBCXX_USE_C99_MATH_TR1
> -D_DECLARE_C99_LDB
> L_MATH -DLIBICONV_PLUG -isystem /usr/local/include -Qunused-arguments
> -Wall -Wc++11-compat -Wempty-body -Wignored-qualifiers
> -Woverloaded-vir
> tual -Wpointer-arith -Wsign-compare -Wtype-limits -Wunreachable-code
> -Wwrite-strings -Wno-invalid-offsetof -Wclass-varargs -Wloop-analysis
> -W
> c++11-compat-pedantic -Wc++14-compat -Wc++14-compat-pedantic
> -Wc++1z-compat -Wimplicit-fallthrough -Wstring-conversion
> -Wthread-safety -Wno-i
> nline-new-delete -Wno-error=deprecated-declarations
> -Wno-error=array-bounds -Wno-unknown-warning-option
> -Wno-return-type-c-linkage -O2 -pipe
> -O3 -DLIBICONV_PLUG -isystem /usr/local/include -fno-strict-aliasing
> -DLIBICONV_PLUG -isystem /usr/local/include -fno-exceptions
> -fno-strict-
> aliasing -fno-rtti -ffunction-sections -fdata-sections -fno-exceptions
> -fno-math-errno -pipe -I/usr/local/include -O2 -O3 -fno-omit-frame-poi
> nter /construction/xports/mail/thunderbird/work/.build/ipc/app/tmp4zapiQ.list
> -pthread -Wl,--as-needed -Wl,-z,noexecstack -Wl,-z,text -rdynam
> ic -Wl,-rpath-link,/construction/xports/mail/thunderbird/work/.build/dist/bin
> -Wl,-rpath-link,/usr/local/lib ../../xpcom/glue/libxpcomglue_s.
> a -pie ../../toolkit/library/libxul.so -L/usr/local/lib
> -L/usr/local/lib -lplds4 -lplc4 -lnspr4 -pthread
> /construction/xports/mail/thunderbird/work/.build/ipc/app/tmp4zapiQ.list:
> INPUT("GMPLoader.o")
> INPUT("MozillaRuntimeMain.o")
> INPUT("../../mozglue/build/SSE.o")
> INPUT("../../memory/mozalloc/Unified_cpp_memory_mozalloc0.o")
> INPUT("../../memory/build/mozjemalloc_compat.o")
> INPUT("../../memory/build/mozmemory_wrap.o")
> INPUT("../../memory/build/jemalloc_config.o")
> INPUT("../../mozglue/misc/StackWalk.o")
> INPUT("../../mozglue/misc/TimeStamp.o")
> INPUT("../../mozglue/misc/TimeStamp_posix.o")
> INPUT("../../mfbt/Compression.o")
> INPUT("../../mfbt/Decimal.o")
> INPUT("../../mfbt/Unified_cpp_mfbt0.o")
> INPUT("../../mfbt/Unified_cpp_mfbt1.o")
> INPUT("../../memory/fallible/fallible.o")
> INPUT("../../dom/media/gmp/rlz/Unified_cpp_dom_media_gmp_rlz0.o")
>
> /usr/bin/ld: warning: libssl3.so, needed by
> ../../toolkit/library/libxul.so, not found (try using -rpath or
> -rpath-link)
> /usr/bin/ld: warning: libsmime3.so, needed by
> ../../toolkit/library/libxul.so, not found (try using -rpath or
> -rpath-link)
> /usr/bin/ld: warning: libnss3.so, needed by
> ../../toolkit/library/libxul.so, not found (try using -rpath or
> -rpath-link)
> /usr/bin/ld: warning: libnssutil3.so, needed by
> ../../toolkit/library/libxul.so, not found (try using -rpath or
> -rpath-link)
> ../../toolkit/library/libxul.so: undefined reference to
> `PK11_CheckUserPassword@NSS_3.2'
> ../../toolkit/library/libxul.so: undefined reference to
> `PK11_GetAllTokens@NSS_3.2'
> [.. slew of link errors ...]
>
> I have had a quick look, and it appears that the libssl3, libsmime3,
> libnss3 and libnssutil3 are located in /usr/local/lib/nss; but this
> does not appear to be specified in the link-path. Anyone have a quick
> fix?
The port security/nss has USE_LDCONFIG=${PREFIX}/lib/nss in its Makefile,
so it should install /usr/local/libdata/ldconfig/nss with single line inside:
/usr/local/lib/nss
That should be enough for /usr/local/lib/nss to be added to
/var/run/ld-elf.so.hints at boot time.
Check your installation using "ldconfig -r"
___
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: leptonica update
03.06.2018 5:22, Walter Schwarzenfeld wrote: > Yes, I was wrong: > > The CONFLICTS_BUILD in leptonica means it would pick up the wrong > "openjpeg.h" if openjpeg15 is installed. This seems to be porting bug that should be resolved by patching the source instead of just addition of CONFLICTS_BUILD. ___ 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: make package "*** Error code 1"
08.06.2018 8:12, duckmanjbr wrote:
> do-install:
> ${MKDIR} ${STAGEDIR}${PREFIX}/pkg
> ${MKDIR} ${STAGEDIR}${PREFIX}/bin/localrepo
> ${MKDIR} ${STAGEDIR}/etc/inc/priv
> ${MKDIR} ${STAGEDIR}${DATADIR}
> ${INSTALL_DATA} -m 0644 ${FILESDIR}${PREFIX}/pkg/localrepo.xml \
> ${STAGEDIR}${PREFIX}/pkg
> ${INSTALL_DATA} ${FILESDIR}${PREFIX}/pkg/localrepo.inc \
> ${STAGEDIR}${PREFIX}/pkg
> ${INSTALL_DATA} ${FILESDIR}${PREFIX}/bin/localrepo/localrepo.conf \
> ${STAGEDIR}${PREFIX}/bin/localrepo
> ${INSTALL_DATA} ${FILESDIR}/etc/inc/priv/localrepo.priv.inc \
> ${STAGEDIR}/etc/inc/priv
> ${INSTALL_DATA} ${FILESDIR}${DATADIR}/info.xml \
> ${STAGEDIR}${DATADIR}/info.xml
> @${REINPLACE_CMD} -i '' -e "s|%%PKGVERSION%%|${PKGVERSION}|" \
>
> .include
Here is obvious bug: the line with REINPLACE_CMD has continuation backslash
without any continuation text and without file name to process. Fix it.
___
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: make package "*** Error code 1"
08.06.2018 16:58, Matthew Seaman wrote:
>>> @${REINPLACE_CMD} -i '' -e "s|%%PKGVERSION%%|${PKGVERSION}|" \
>>>
>>> .include
>>
>> Here is obvious bug: the line with REINPLACE_CMD has continuation backslash
>> without any continuation text and without file name to process. Fix it.
>
> Actually, since the next line is a blank line, that's going to be pretty
> harmless.
No. A filename is still missing.
___
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: make package "*** Error code 1"
08.06.2018 20:12, duckmanjbr wrote: > 1st off, thanks everyone for helping me out! There was indeed a missing > filename and I believe I’ve remedied that. I’m moving along but now getting > a "missing property prefix” error. Am I missing a log file or something to > help trouble shoot these errors? I’d like to piece it together to a working > state before I offer it as a pull request to pfSense/FreeBSD-ports. > > build_error: > root@:~/pfSense-pkg-localrepo # make package > ===> License APACHE20 accepted by the user > ===> pfSense-pkg-LocalRepo-0.1_1 depends on file: /usr/local/sbin/pkg - > found > ===> Fetching all distfiles required by pfSense-pkg-LocalRepo-0.1_1 for > building > ===> Extracting for pfSense-pkg-LocalRepo-0.1_1 > /bin/mkdir -p /root/pfSense-pkg-localrepo/work/pfSense-pkg-LocalRepo-0.1 > ===> Patching for pfSense-pkg-LocalRepo-0.1_1 > ===> Configuring for pfSense-pkg-LocalRepo-0.1_1 > ===> Staging for pfSense-pkg-LocalRepo-0.1_1 > ===> Generating temporary packing list > /bin/mkdir -p /root/pfSense-pkg-localrepo/work/stage/usr/local/pkg > /bin/mkdir -p /root/pfSense-pkg-localrepo/work/stage/usr/local/bin/localrepo > /bin/mkdir -p /root/pfSense-pkg-localrepo/work/stage/etc/inc/priv > /bin/mkdir -p > /root/pfSense-pkg-localrepo/work/stage/share/pfSense-pkg-LocalRepo > install -m 0644 -m 0644 > /root/pfSense-pkg-localrepo/files/usr/local/pkg/localrepo.xml > /root/pfSense-pkg-localrepo/work/stage/usr/local/pkg > install -m 0644 > /root/pfSense-pkg-localrepo/files/usr/local/pkg/localrepo.inc > /root/pfSense-pkg-localrepo/work/stage/usr/local/pkg > install -m 0644 > /root/pfSense-pkg-localrepo/files/usr/local/bin/localrepo/localrepo.conf > /root/pfSense-pkg-localrepo/work/stage/usr/local/bin/localrepo > install -m 0644 > /root/pfSense-pkg-localrepo/files/etc/inc/priv/localrepo.priv.inc > /root/pfSense-pkg-localrepo/work/stage/etc/inc/priv > install -m 0644 > /root/pfSense-pkg-localrepo/files/usr/local/share/pfSense-pkg-LocalRepo/info.xml > /root/pfSense-pkg-localrepo/work/stage/share/pfSense-pkg-LocalRepo > > Compressing man pages (compress-man) > ===> Building package for pfSense-pkg-LocalRepo-0.1_1 > [: =: unexpected operator > pkg-static: Invalid package: object has missing property prefix > pkg-static: the package is not valid > *** Error code 1 I guess, your files/pkg-install.in file may have bugs. And this seems to be very pfSence-specific, you probably get more attention asking pfSense people. ___ 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/qt5-core (qt5-core-5.9.4_2) (uninstall error)
27.06.2018 9:46, Janos Dohanics wrote: > # ls -al /usr/local/lib/qt5/libQt5Core* > -rw-r--r-- 1 root wheel 1040 May 5 21:58 > /usr/local/lib/qt5/libQt5Core.prl > lrwxr-xr-x 1 root wheel 19 May 5 21:58 > /usr/local/lib/qt5/libQt5Core.so -> libQt5Core.so.5.9.4 > lrwxr-xr-x 1 root wheel 19 May 5 21:58 > /usr/local/lib/qt5/libQt5Core.so.5 -> libQt5Core.so.5.9.4 > -rwxr-xr-x 1 root wheel 5028000 May 5 21:58 > /usr/local/lib/qt5/libQt5Core.so.5.9.4 > > How can I fix this? Just remove symlinks and re-do the procedure. ___ 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: What the port license should be when software is "free for non-commercial use" with "click-to-accept" or clickwrap license?
03.07.2018 5:52, Yuri wrote: > One software package has the custom license text that users need to > click-to-accept in order to install it. > > Does 'pkg' support such license? Can it show the user the license text and > ask the user to click "Agree" before installing the package? It does. See mail/dcc-dccd for example. ___ 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: What the port license should be when software is "free for non-commercial use" with "click-to-accept" or clickwrap license?
03.07.2018 6:17, Yuri wrote: >> It does. See mail/dcc-dccd for example. > But it doesn't ask to "agree" during 'pkg install dcc-dccd'. Yes. Meantime, you have several choices: 1) Mark the port NO_PACKAGE and/or no-pkg-mirror to force users use a port that 1a) builds software from source, or 1b) installs pre-build binaries bundled with distfiles (just like cvsup binary port did earlier); 2) Prepare and submit a patch for pkg itself to support this feature. It should be not hard to do. ___ 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: Passenger not working any more after Base System upgrade: can you reproduce?
On 02.07.2018 03:19, José Pérez via freebsd-ports wrote: [skip] Have you actually read the log? > Further error details in log: > [ pid=57456, timestamp=1530359790 ] Process aborted! signo=SIGABRT(6), > reason=#65543, si_addr=0x0, randomSeed=1530359790 > [ pid=57456 ] Crash log dumped to > /var/tmp/passenger-crash-log.1530359790 [skip] > *** ERROR: cannot execute lsof: No such file or directory (errno=2) Make sure your lsof binary is present (installed by port or package) and your application has correct search path for it. ___ 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: Passenger not working any more after Base System upgrade: can you reproduce?
On 02.07.2018 03:19, José Pérez via freebsd-ports wrote: > Hi, > after a Base System upgrade Passenger fails on > startup with this error: > nginx: [alert] Unable to start the Phusion Passenger watchdog: it seems > to have been killed with signal SIGABRT during startup (-1: Unknown > error) > > Can please someone try and reproduce and/or > suggest a workaround/fix? > > How to reproduce: > - stable 11.2 > - install nginx or apache (same problem with >both) > - install (almost) any passenger version (I >could reproduce with 5.2.1, 5.3.2 (current >in ports) and 5.3.3 (latest)) > > What you get: > # service nginx start > Performing sanity check on nginx configuration: > nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is > ok > nginx: configuration file /usr/local/etc/nginx/nginx.conf test is > successful > Starting nginx. > nginx: [alert] Unable to start the Phusion Passenger watchdog: it seems > to have been killed wit > > Further error details in log: > [ pid=57456, timestamp=1530359790 ] Process aborted! signo=SIGABRT(6), > reason=#65543, si_addr=0x0, randomSeed=1530359790 Have your tried to google this? Search for "reason=" "65543" gives https://github.com/phusion/passenger/issues/987 as second link that mentiones very similar problem pointing to some C++ compiler incompatibility and FreeBSD 11.2 got new clang version 6.0.0, so that may be a culprit. You should try to deinstall all dependent ports including nginx and the application itself and rebuild them all from scratch to eliminate possible C++ mangling/runtime problems. ___ 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: What the port license should be when software is "free for non-commercial use" with "click-to-accept" or clickwrap license?
03.07.2018 14:06, Mathieu Arnold wrote: >>> But it doesn't ask to "agree" during 'pkg install dcc-dccd'. >> >> Yes. Meantime, you have several choices: >> >> 1) Mark the port NO_PACKAGE and/or no-pkg-mirror to force users use a port >> that > > It is not no-pkg-mirror, in this case, it is no-auto-accept. According to https://www.freebsd.org/doc/en/books/porters-handbook/licenses.html > no-pkg-mirror > Free redistribution of package is prohibited. Equivalent to setting > NO_PACKAGE. > The package will not be distributed from the FreeBSD package CDN > https://pkg.freebsd.org/. This is exactly what I'm talking about: preventing usage of a package because pkg(8) does not honor "no-auto-accept" 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: What the port license should be when software is "free for non-commercial use" with "click-to-accept" or clickwrap license?
05.07.2018 18:01, Marko Cupać wrote: > What would be the benefit of users' clicks for owners of such software? > What would owners of such software lose if they didn't require clicks? > > What would be the benefit for pkg owners for investing time and effort > into supporting such feature? How would FreeBSD project and its users > benefit from it? https://en.wikipedia.org/wiki/End-user_license_agreement#Shrink-wrap_and_click-wrap_licenses ___ 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: building openjdk without alsa dependency
31.07.2018 7:29, blubee blubeeme пишет: > I would like to build openjdk7 without the asound lib, I already > removed ALSA from my kernel so the build fails but I am not writing > Java applications that needs sound. > > I made a few changes to just not build the ALSA parts and the port > builds properly. > > I had to edit the patch-bsd and created a new patch to remove building > ALSA sound parts. > > Would it be possible to have the java team add a knob to the USE_JAVA > in bsd.java.mk so that I can use this version with other ports? > > patch-jdk_make_common_Sanity.gmk : https://pastebin.com/cXej8LES > patch-bsd : > https://pastebin.com/E9xHTkKH Please do not use pastebin but https://bugs.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: Virtual Printer Port?
On 29.07.2018 03:28, Dan Mahoney (Gushi) wrote: > Hey all, > > This may be off topic, but does anyone know a port or configuration for > FreeBSD that can listen on a serial port and spit out a PDF? I have a > piece of hardware (a hospital-grade pulse oximeter) that's able to talk to > an *original* HP Thinkjet with a serial port and produce graphical charts. > Like, the best 1993 has to offer. > > I'd rather simply hook up a BSD box via a serial port and translate those > control codes into a PDF (or TIFF/PNG/postscript document). The control > codes are pretty well documented, since you need them to make printer > drivers, but this is the reverse use. > > Is there anything in ports that can do this? Is there a better mailing > list to be asking on? They say, HP Thinkjet used PCL1 as incoming printing language. Basically, you need to *reverse* PCL1-render of original "document" back to a file containg original data. This is similar to disassembly of machine code back to program text and/or data. I highly doubt you'll find ready-to-use "decompiler" for PCL1 and you may need to write such software yourself. Or you can just toss received PCL1 to any modern PCL-compatible multi-functional device to print it and scan resulting sheet back to PDF file :-) PCL versions should be backward compatible. ___ 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: Delete a port
04.08.2018 21:03, Romain Tartière wrote:
> On Sat, Aug 04, 2018 at 12:28:41PM +0200, Matthias Fechner wrote:
>> ./rmport: svnlog: not found
>>
>> Anyone an idea what is wrong?
>
> Never used this script, but I guess you are hitting line 390:
>
> | $EDITOR svnlog
>
> Any chance $EDITOR is not set?
It seems, rmport script needs a patch:
Index: Tools/scripts/rmport
===
--- Tools/scripts/rmport(revision 476322)
+++ Tools/scripts/rmport(working copy)
@@ -39,6 +39,7 @@
# MAINTAINER= cr...@freebsd.org
#
+EDITOR=${EDITOR:-vi}
PORTSDIR=${PORTSDIR:-/usr/ports}
INDEX=${PORTSDIR}/`make -C ${PORTSDIR} -V INDEXFILE`
signature.asc
Description: OpenPGP digital signature
Re: Delete a port
05.08.2018 0:42, Eitan Adler wrote: >> Feel free to commit, but please use the absolute path to vi? > > Why? Would't one want to respect the user's preference when it comes > to an editor? This preference is implicit when it comes to PATH. This is traditional overcautiousness against user's possibly insecure PATH having current directory that can lead to running malignant /tmp/vi in multiuser environment. Eugene ___ 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 11.2] net-snmpd incomplete mac addresses
05.10.2018 18:33, Patrick Lamaiziere wrote: > Hello, > > freebsd 11.2/amd64 release > net-snmp-5.7.3_18 > > net-snmpd returns incomplete MAC addresses in IF-MIB::ifPhysAddress, > the first octet is always "0". > > $ snmpwalk -v 2c -c "xxx" localhost 1.3.6.1.2.1.2.2.1.6 > IF-MIB::ifPhysAddress.1 = STRING: 0:36:9f:93:7d:f8 > IF-MIB::ifPhysAddress.2 = STRING: 0:36:9f:93:7d:fa > IF-MIB::ifPhysAddress.3 = STRING: 0:f4:bb:ef:c8:e4 > ... > > $ ifconfig | grep ether > ether a0:36:9f:93:7d:f8 > ether a0:36:9f:93:7d:fa > ether ec:f4:bb:ef:c8:e4 > > tcpdump confirms that the problem is in net-snmpd (and not the client). > > Also when using the MIB IP-MIB::ipNetToMediaPhysAddress the MAC > addresses are correct. > > $ snmpwalk -v2c -c '***r***' localhost IP-MIB::ipNetToMediaPhysAddress | grep > a0:36:9f:93:7d:f8 > IP-MIB::ipNetToMediaPhysAddress.13.10.10.1.118 = STRING: a0:36:9f:93:7d:f8 > > I've checked net-snmpd 5.7.3 under linux and the mac addresses are > correct. (So it's specific to FreeBSD.) > > Any clue ? We have bsnmpd in the base system. Does it exhibit same problem? ___ 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"
ssl=base
Hi!
As maintainer of the net/mpd5 port, I wonder why our ports/Mk/Uses/ssl.mk
prevents building this port using FreeBSD 12 and base system libssl
when libressl is installed?
While building with ssl=base, the port itself does not include headers
from ${LOCALBASE}/include and it does not include ${LOCALBASE}/lib to search
path for linking stage.
I see no way to override noted (wrong) check-depends restriction, and that's
not good.
___
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: ssl=base
25.11.2018 18:46, Mathieu Arnold wrote:
>> As maintainer of the net/mpd5 port, I wonder why our ports/Mk/Uses/ssl.mk
>> prevents building this port using FreeBSD 12 and base system libssl
>> when libressl is installed?
>>
>> While building with ssl=base, the port itself does not include headers
>> from ${LOCALBASE}/include and it does not include ${LOCALBASE}/lib to search
>> path for linking stage.
>>
>> I see no way to override noted (wrong) check-depends restriction, and that's
>> not good.
>
> Because you either use OpenSSL from the base system, or you install an
> *SSL variant from ports and use it. You cannot mix half of the stuff
> from the base system and half of the stuff from a port version of *SSL.
Why can't you use LibreSSL port for some ports and base libssl for other ports?
That is, net/mpd5 links with base system libfetch that depends on base libssl,
so it is example of port that cannot be built with LibreSSL.
___
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: ssl=base
25.11.2018 18:57, Franco Fichtner wrote: >> Why can't you use LibreSSL port for some ports and base libssl for other >> ports? >> That is, net/mpd5 links with base system libfetch that depends on base >> libssl, >> so it is example of port that cannot be built with LibreSSL. > > FWIW, since 2015 we've had no build or operational issue with mpd5 for > LibreSSL > from ports. Fixed in r485853. ___ 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: packages and base jails
27.11.2018 3:24, Michael W. Lucas wrote:
>
> Hi,
>
> I'm writing a book on jails and am looking for BCP. I'd like to
> present either "This is the approved solution and should work" or
> "these are the gotchas with any of these, choose your pain."
>
> Folks want base jails to include packages, but also want to install
> additional packages--which won't happen if /usr/local is mounted
> read-only in the base jail. Trawling around the Net I see a couple
> options. Both involve the primary jail using a different package
> repo. The overlay jail uses the standard package repo.
>
> 1) primary jail uses a repo with PREFIX=/usr/pkg or /opt. Works in my
> simple use cases once I set ldconfig directories in rc.conf, but I'm
> told programs like pkgconfig can go sideways.
>
> 2) base jail repo uses with PREFIX=/. Utterly violates separation of
> base and pkg, but everything should find everything out of the
> box. Again, seems to work in my wimpy use cases.
>
> Is there an option that should work? Or is a matter of choosing
> between horrors?
Not sure I understand the problem which I don't have using sysutils/ezjail
that uses base jail situated in /usr/local/j/basejail in my case.
For each distinct jail instance, it null-mounts it read-only
to /usr/local/j/${JAILNAME}/basejail and /usr/local/j/${JAILNAME} it jail's
root.
Inside this root, /bin is symlink to /basejail/bin, and /boot, /libexec, /rescue
and /sbin are similar symlinks, so are
/usr/{bin|include|lib|lib32|libdata|libexec|ports|sbin|share}
all symlinks to corresponding directories inside ro-mounted /basejail/usr/...
But not /usr/local nor /usr/{src|obj}, if that matters. So each jail have its
own
set of packages or even ports if I choose to null-mount host's /usr/ports
readonly
to /usr/local/j/${JAILNAME}/basejail/usr/ports and write to jail's
/etc/make.conf:
WRKDIRPREFIX= /var/ports
DISTDIR=/var/ports/distfiles
PACKAGES= /var/ports/packages
INDEXDIR= /var/ports
That works just fine for me.
___
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: packages and base jails
27.11.2018 6:42, Eugene Grosbein wrote:
> But not /usr/local nor /usr/{src|obj}, if that matters. So each jail have its
> own
> set of packages or even ports if I choose to null-mount host's /usr/ports
> readonly
> to /usr/local/j/${JAILNAME}/basejail/usr/ports
In fact, to /usr/local/j/${JAILNAME}/usr/ports directly.
> and write to jail's /etc/make.conf:
>
> WRKDIRPREFIX= /var/ports
> DISTDIR=/var/ports/distfiles
> PACKAGES= /var/ports/packages
> INDEXDIR= /var/ports
>
> That works just fine for me.
___
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: Deregister a port?
04.02.2019 19:14, Luciano Mannucci wrote: > > Is there a way to deregister a port without touching port's files? > > The only way I see is build my own version without install, run > pkg delete end then make install on the source tree I'm managing > myself. > > This leaves me without the package functionality while installing, > wich is not desirable on production server. > > Any ideas? Use "make -DDISABLE_CONFLICTS" just like portupgrade does. If this is not enough, please be more precise describing your problem and do not forget to show build error log that you get without pkg delete. Also read pkg-install(8) and pkg.conf(5) manual pages and consider copying existing PKG_DBDIR to alternative directory like /opt/db/pkg and using it by means of env PKG_DBDIR=/opt/db/pkg make -C /path/to/yourownport ___ 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: pkg check erroneously reports missing lib
05.02.2019 2:50, Xavier пишет: > This is mediatomb from ports, on FreeBSD 12-STABLE : > > > [root@numenor ~]# portupgrade -vf spidermonkey17 mediatomb > [...compile...compile...compile...] > > [root@numenor ~]# pkg check -Bd mediatomb > Checking mediatomb: 100% > mediatomb is missing a required shared library: libjs.so > > [root@numenor ~]# ldd /usr/local/bin/mediatomb |grep libjs > libjs.so => /usr/local/lib/libjs.so (0x800e8b000) > > And mediatomb works like a charm > > Any idea ? Perhaps, there is something wrong with your installation of lang/spidermonkey17 that installs libjs.so. What does "pkg which /usr/local/lib/libjs.so" tell? ___ 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 LibreSSL with only one or a subset of all installed ports
07.02.2019 1:58, Kevin Oberman wrote: > I'm not saying that it can't be done, but you have to know all of the > linkages and be very sure that there are no conflicts. Sometimes libmap.conf(5) helps. ___ 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: FreeCAD 0.17 && /lib//libgcc_s.so.1
17.02.2019 8:02, Russell L. Carter wrote: > Greetings, > > Restarting the FreeCAD 0.17 discussion on a different tangent. > > As I mentioned before I am building (for now) outside of the ports > tree FreeCAD-git + Coin-hg + QT5 + med-4.0.0. I want to particularly > thank very much all the porting work that has been done so far, I > wouldn't have been able to get as far as I have without it. > > french/med (french?) requires fortran, and for ports gfortran is > apparently the only option. gfortran depends on libgcc_s.so.1, which > is FreeBSD's (only?) version of dll hell. > > Transcribed output from the FreeCAD Testing Framework GUI test all: > > First run of TestApp.All: Run: 212 Failures: 1 Errors: 20 > > which isn't bad at all I suspect. However one of the failures is > > /lib/libgcc_s.so.1 version GCC_4.8.0 required by > /usr/local/lib/gcc8/libgfortran.so.5 not found > > This is probably fatal to practical use of FreeCAD on FreeBSD. I was > able to open most of my previous models, created on debian-testing, > but some were fail. > > 2 threads, no happy ending: > > https://lists.freebsd.org/pipermail/freebsd-ports/2018-May/113336.html > https://lists.freebsd.org/pipermail/freebsd-python/2016-January/009672.html > > Question to experienced porters, how is this best practice solved? I've just did "pkg install gcc8" using my FreeBSD 11.2/amd64 system and got this: # ldd /usr/local/lib/gcc8/libgfortran.so.5 /usr/local/lib/gcc8/libgfortran.so.5: libquadmath.so.0 => /usr/local/lib/gcc8/libquadmath.so.0 (0x80146e000) libz.so.6 => /lib/libz.so.6 (0x8016ad000) libm.so.5 => /lib/libm.so.5 (0x8018c5000) libgcc_s.so.1 => /usr/local/lib/gcc8/libgcc_s.so.1 (0x801af3000) libc.so.7 => /lib/libc.so.7 (0x800823000) So, /usr/local/lib/gcc8/libgfortran.so.5 does not depend on /lib/libgcc_s.so.1 but on /usr/local/lib/gcc8/libgcc_s.so.1 in normal case. I assume something is broken in your installation. Try removing gcc8 and reinstalling it using package. ___ 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: FreeCAD 0.17 && /lib//libgcc_s.so.1
17.02.2019 8:35, Russell L. Carter wrote: >>> Transcribed output from the FreeCAD Testing Framework GUI test all: >>> >>> First run of TestApp.All: Run: 212 Failures: 1 Errors: 20 >>> >>> which isn't bad at all I suspect. However one of the failures is >>> >>> /lib/libgcc_s.so.1 version GCC_4.8.0 required by >>> /usr/local/lib/gcc8/libgfortran.so.5 not found Where did you get this from, exactly? ___ 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: FreeCAD 0.17 && /lib//libgcc_s.so.1
17.02.2019 8:58, Russell L. Carter wrote: > On 2/16/19 6:44 PM, Eugene Grosbein wrote: >> 17.02.2019 8:35, Russell L. Carter wrote: >> >>>>> Transcribed output from the FreeCAD Testing Framework GUI test all: >>>>> >>>>> First run of TestApp.All: Run: 212 Failures: 1 Errors: 20 >>>>> >>>>> which isn't bad at all I suspect. However one of the failures is >>>>> >>>>> /lib/libgcc_s.so.1 version GCC_4.8.0 required by >>>>> /usr/local/lib/gcc8/libgfortran.so.5 not found >> >> Where did you get this from, exactly? >> > > I apologize, I am unsure what you are asking about with respect to the > "this". The output I am showing is literally typed in from the error > display box that happens when I run FreeCAD-git, ie, current git > FreeCAD, in an outside the ports tree bleeding edge version, including > the dependencies, that I am working on. I detailed this in the > original message. I would be delighted to share all my scripts and > patches that got me this far. > > Anyway there is a FreeCAD Test workbench, with an "all" option, right > at the top, and that's where I'm starting on the bug triage. > > Now I got to cook dinner but I will be back at it tomorrow. Something > of an obsession. Plus I have a deck to design. It would be cheaper > to have someone else do this, but shouldn't FreeCAD do it on FreeBSD? Maybe you should use libmap.conf(5) to work around the problem. "ktrace -i" and kdump would be handy to discover exact name of the binary or library for /etc/libmap.conf if FreeCAD-git happens to be not binary but some wrapping script for real binary. ___ 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: FreeCAD 0.17 && /lib//libgcc_s.so.1
17.02.2019 12:11, Steve Kargl wrot: >> # ldd /usr/local/lib/gcc8/libgfortran.so.5 >> /usr/local/lib/gcc8/libgfortran.so.5: >> libquadmath.so.0 => /usr/local/lib/gcc8/libquadmath.so.0 >> (0x80146e000) >> libz.so.6 => /lib/libz.so.6 (0x8016ad000) >> libm.so.5 => /lib/libm.so.5 (0x8018c5000) >> libgcc_s.so.1 => /usr/local/lib/gcc8/libgcc_s.so.1 (0x801af3000) >> libc.so.7 => /lib/libc.so.7 (0x800823000) >> >> So, /usr/local/lib/gcc8/libgfortran.so.5 does not depend on >> /lib/libgcc_s.so.1 >> but on /usr/local/lib/gcc8/libgcc_s.so.1 in normal case. >> >> I assume something is broken in your installation. Try removing gcc8 and >> reinstalling >> it using package. > > There is a problem with the order of libgcc_s.so.1 > in the cache created by ldconfig. rtld will use > the first one it finds. If it fails, it fails. It > does not look to see if there is a second entry. If binary needs specific version of libgcc_s.so.1 installed with gcc8 port/package, then building system must use specific rpath, so rtld would not use "the first one it finds". ___ 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: FreeCAD 0.17 && /lib//libgcc_s.so.1
17.02.2019 13:19, Steve Kargl wrote: > For whatever reason, there are situations where the rpath > isn't set in the library. Read the rtld manpage. You're > hitting #5 in the list. Our package building system sets rpath for dependants of gcc8, so Fortran libraries (and others) do have rpath for its runtime. Setting rpath for resulting binary should solve the problem. ___ 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: FreeCAD 0.17 && /lib//libgcc_s.so.1
17.02.2019 12:56, Steve Kargl wrote:
> On Sun, Feb 17, 2019 at 12:37:36PM +0700, Eugene Grosbein wrote:
>> 17.02.2019 12:11, Steve Kargl wrot:
>>
>>>
>>> There is a problem with the order of libgcc_s.so.1
>>> in the cache created by ldconfig. rtld will use
>>> the first one it finds. If it fails, it fails. It
>>> does not look to see if there is a second entry.
>>
>> If binary needs specific version of libgcc_s.so.1 installed
>> with gcc8 port/package, then building system must use specific
>> rpath, so rtld would not use "the first one it finds".
>
> This is a well-known problem with libgcc_s.so.1 and gfortran.
> You can state whatever you believe should happen, but it does
> not seem to work that. You have a few options:
> 1) Add -static to your options;
> 2) Use LD_LIBRARY_PATH, LD_RUN_PATH to point to
>/usr/local/lib/gcc8;
> 3) Add -Wl,-rpath=/usr/local/lib/gcc8 to FFLAGS in /etc/make.conf
>(check syntax for this one);
> 4) bump the major library version number for /lib/libgcc.so.1
>to 2;
> 5) fix rtld to not fail on the first found library in the cache.
>Iterated over all entries and only fail if the library isn't found;
> 6) rename /lib/libgcc_s.so.1 to /lib/libllvm_s.so.1 and teach
>llvm/clang/rtld to not misappropriate a well-known GCC library
>name.
>
When a port from our Ports Collection needs specific version of GCC and its
runtime libraries,
it utilizes "USE_GCC=8" and bsd.gcc.mk adds this to make everybody happy:
CFLAGS+=-Wl,-rpath=${_GCC_RUNTIME}
CXXFLAGS+= -Wl,-rpath=${_GCC_RUNTIME}
LDFLAGS+= -Wl,-rpath=${_GCC_RUNTIME} -L${_GCC_RUNTIME}
This is your 3) case and this is what I have meant.
When someone builds a binary having same requirements but without
writing port/using bsd.gcc.mk, same needs to be done
and everything should just work. Or better create a port.
___
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: FreeCAD 0.17 && /lib//libgcc_s.so.1
17.02.2019 22:15, Diane Bruce wrote: > Basically all we need is a pre-loader script for interpreters > that run into this such as python. (I suspect there have to be other > interpreters that run into this.) Perhaps something like > python2_gfortran or the like, all it has to do is PRELOAD or modify > the library path so we get the 'right' libgcc_s.so. We already have libmap.conf(5). It should be possible to work around the problem creating /usr/local/etc/libmap.d/python.conf with contents: [python2.7] libgcc_s.so.1 /usr/local/lib/gcc8/libgcc_s.so.1 [python3.4] libgcc_s.so.1 /usr/local/lib/gcc8/libgcc_s.so.1 ___ 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: FreeCAD 0.17 && /lib//libgcc_s.so.1
17.02.2019 22:41, Diane Bruce wrote:
>> Setting rpath for resulting binary should solve the problem.
>
> No no no no no. Not for an interpreter. The interpreter doesn't 'know'
> you are about to load a binary module that needs libgcc_s and until
> it loads something that uses gfortran it doesn't matter
> which libgcc_s so it picks the 'wrong' one.
>
> As my wiki page article says:
> We can rename our libgcc (Yes other complications but...)
>
> We can fix our system libgcc to have the missing functions/data that
> current libgcc has then bump our version
>
> We can use a specific port which PRELOADs the gfortran libgcc_s.so
> e.g. python2_gfortran8 or whatever. (What a mess and it's ugly but
> it would work)
>
> Individual python ports could be modified to do the PRELOAD with
> a tiny sh script e.g. opencad could envoke a small sh script
> that then starts the python interpreter. This would mean exposing the
> PATH from Mk/USES/fortan.mk
>
> e.g. we currently do this:
>
> FFLAGS+=-Wl,-rpath=${LOCALBASE}/lib/gcc${_GCC_VER}
> FCFLAGS+= -Wl,-rpath=${LOCALBASE}/lib/gcc${_GCC_VER}
> LDFLAGS+= -Wl,-rpath=${LOCALBASE}/lib/gcc${_GCC_VER} \
>
> We'd need FRPATH=${LOCALBASE}/lib/gcc${_GCC_VER}
> exposed
>
> blah. I finally just looked at openscad it's a binary not a python script
> As Steve sez it's missing the -Wl,-rpath stuff then
If all involved binaries and libraries in a chain starting from the interpreter
and including libraries have mappings for libgcc_s.so to right file,
the problem should be solved. And libmap.conf(5) should do the job.
___
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: FreeCAD 0.17 && /lib//libgcc_s.so.1
17.02.2019 22:46, Diane Bruce wrote: >> We already have libmap.conf(5). It should be possible to work around the >> problem >> creating /usr/local/etc/libmap.d/python.conf with contents: >> >> [python2.7] >> libgcc_s.so.1 /usr/local/lib/gcc8/libgcc_s.so.1 >> >> [python3.4] >> libgcc_s.so.1 /usr/local/lib/gcc8/libgcc_s.so.1 >> > > Sure but I'm guessing not all python ports *need* gfortran hence > we shouldn't force all python coded ports to use the gfortran libgcc_s.so libmap.conf(5) manual page documents how to restrict such mappings per-directory. One can create symlink for the interpreter and restrict the mapping for symlink only. > Moreover, the libmap would have to be updated everytime gfortran got > updated Not quite: libgcc_s.so.1 needs mapping for interpreter only as our port building system already creates libgfortran.so with right rpath for libgcc_s.so.1: # ldd /usr/local/lib/gcc8/libgfortran.so.5 /usr/local/lib/gcc8/libgfortran.so.5: libquadmath.so.0 => /usr/local/lib/gcc8/libquadmath.so.0 (0x80146e000) libz.so.6 => /lib/libz.so.6 (0x8016ad000) libm.so.5 => /lib/libm.so.5 (0x8018c5000) libgcc_s.so.1 => /usr/local/lib/gcc8/libgcc_s.so.1 (0x801af3000) libc.so.7 => /lib/libc.so.7 (0x800823000) ___ 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: loose dependency
14.03.2019 11:40, Hiroki Sato wrote:
> Koichiro Iwao wrote
> in <20190314031726.aaspgwdcuithh...@icepick.vmeta.jp>:
>
> me> Hi,
> me>
> me> If a port have runtime dependency on bin/convert command of ImageMagick
> me> but whichever ImageMagick{6,7}{,-nox11} are OK, how port Makefile should
> me> be written?
> me>
> me> ImageMagick6 and 7 conflicts each other. I want to respect user's
> me> choice which ImageMagick to use.
>
> There is no easy solution to solve it completely because currently
> package dependency is solved in a strict manner including package
> names and version numbers, not only existence of specific files.
> Creating multiple ports which depend on each software or using
> FLAVORS to make it easier is a way to provide packages with every
> possible combinations of dependency and let one to choose.
OTOH, one still may create a port depending on existence of specific file
and fetching another port automatically in case of file absence.
It works just fine for those using ports as primary source, not packages.
And yes, if one uses packages, it is forced to live with "default" versions
including dependencies or build its own pkg repo.
___
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: lang/go14 doesn't build without COMPAT11 in FREEBSD 12
24.03.2019 1:38, Lucas Nali de Magalhães wrote: > I found a few bugs since I started rebuilding my system. > Most of them are related with the lack of handling of CPUTYPE=native > make.conf tunable. Use CPUTYPE?=native instead of CPUTYPE=native. ___ 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: rc script problems
01.04.2019 3:55, Jim Trigg wrote:
> How do I write an rc script to preserve the pid of a child process? The
> "port" I'm working with (technically a commercial package) has a startup
> script that launches a java process. I had written a simple rc wrapper around
> the script but have found it doesn't support stop because the pid captured is
> the script's pid rather than the java process's pid.
Use something like this for startup script "portname.in" for Java-based long
running service:
#!/bin/sh
#
# $FreeBSD$
#
# PROVIDE: portname
# REQUIRE: LOGIN
# KEYWORD: shutdown
#
# Add the following line to /etc/rc.conf to enable `portname':
#
# portname_enable="YES"
. /etc/rc.subr
command_interpreter="."
command="%%PREFIX%%/bin/java"
command_args="-jar portname.jar"
name="%%PORTNAME%%"
rcvar="${name}_enable"
start_cmd="start_cmd"
stop_cmd="stop_cmd"
pidfile="/var/run/${name}.pid"
required_files="%%DATADIR%%/portname.jar"
portname_chdir="%%DATADIR%%"
eval `JAVAVM_DRYRUN=yes ${command} | fgrep JAVAVM_COMMAND`
procname=${JAVAVM_COMMAND}
start_cmd()
{
check_startmsgs && echo "Starting ${name}."
cd ${portname_chdir}
daemon -u %%USERS%% -f -p ${pidfile} ${command} ${command_args} start
}
stop_cmd()
{
check_startmsgs && echo "Stopping ${name}."
rc_pid=$(check_pidfile $pidfile $procname)
pkill -F ${pidfile}
wait_for_pids $rc_pid
}
load_rc_config ${name}
: ${portname_enable="NO"}
run_rc_command "$1"
#EOF
That is, use daemon(8) utility that can act as superviser for java process:
start it with needed arguments, write its pid to pidfile etc.
___
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: irc/ngircd: typo in Makefile
16.04.2019 2:09, Serpent7776 wrote: > Hello, > > I've just stumbled upon a possible typo in Makefile: > > DEBUG_CONFIGURE_EBABLE=¦¦ debug > > Shouldn't this be ENABLE instead of EBABLE? > Fixed in r499085, 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"
OpenSSL engines directory path
Hi!
FreeBSD 12+ has OpenSSL version that supports loading additional "engines"
(shared libraries).
Default path for engines in FreeBSD is /usr/lib/engines currently.
The path for security/openssl111 port (needed for FreeBSD 11) is
${LOCALBASE}/lib/engines-1.1
Please consider updating ports/Mk/Uses/ssl.conf with something like
OPENSSLENGINES
that should equal to ${OPENSSLLIB}/engines when SSL_DEFAULT is "base"
and for openssl111 it should be ${OPENSSLLIB}/engines-1.1
This would help porting engines.
___
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: OpenSSL engines directory path
24.04.2019 12:24, Eugene Grosbein wrote:
> Hi!
>
> FreeBSD 12+ has OpenSSL version that supports loading additional "engines"
> (shared libraries).
> Default path for engines in FreeBSD is /usr/lib/engines currently.
> The path for security/openssl111 port (needed for FreeBSD 11) is
> ${LOCALBASE}/lib/engines-1.1
>
> Please consider updating ports/Mk/Uses/ssl.conf with something like
> OPENSSLENGINES
> that should equal to ${OPENSSLLIB}/engines when SSL_DEFAULT is "base"
> and for openssl111 it should be ${OPENSSLLIB}/engines-1.1
>
> This would help porting engines.
Ports should install files inside ${LOCALBASE}, so we really need some variable
that should expand to /usr/local/lib/engines-1.1 when SSL_DEFAULT is
"openssl111" for FreeBSD 11
or when SSL_DEFAULT is either "base" or "openssl111" for FreeBSD 12+
___
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"
openssl111/gnutls issue in the ftp/wget
Hi! Is it a bug in the port ftp/wget or in the ports infrastructure (bsd.sanity.mk, ssl.mk) that ftp/wget fails to build for users of FreeBSD11 having openssl111 installed and DEFAULT_VERSIONS+=ssl=openssl111 ? Error messages are: > /!\ wget-1.20.3: Makefile errors /!\ > > The following options helpers are incorrectly set after bsd.port.options.mk > and are ineffective: OPENSSL_LDFLAGS > > *** Error code 1 ___ 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: How to handle go dependencies
22.06.2019 16:58, Matthias Fechner wrote:
> Dear all,
>
> I just prepare the gitlab-ce upgrade to version 12.0.0.
> But I have some problem with a package that uses go to compile.
>
> The new version of devel/gitaly has changed the way the package is defined.
> They removed now all files from the vendor/ folder and add dependencies
> in a `go.mod` file.
>
> If I now build the port it tries to fetch the files while no network
> access is allowed.
>
> What is the correct way to getting these dependencies fetched and
> correctly included into the work-source in the fetch step using go?
That's not easy question. You may find it useful to check out
existing port sysutils/fusefs-webdavfs that successfully deals
with several dependencies located at Github (pborman/getopt and bazil/fuse).
Tricky part is in the post-patch: target of port's Makefile
that creates ${GETOPT_WRKSRCDIR} and ${FUSE_WRKSRCDIR} directories
and symlinks real paths for extracted dependencies into needed names
under ${GETOPT_WRKSRCDIR} and ${FUSE_WRKSRCDIR}.
Another dependency "golang.org/x/net/context" was integrated into golang itself
as "context" since go-1.7 so the port uses REINPLACE_CMD to patch the name in
source files.
___
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: How to handle go dependencies
07.07.2019 5:10, Dmitri Goutnik via freebsd-ports wrote:
> Which can be fixed by just copying the linux version (this probably needs to
> be upstreamed):
>
> post-patch:
> ${REINPLACE_CMD} -e "s|%%PREFIX%%|${PREFIX}|"
> ${WRKSRC}/config.toml.example
> ${MV} ${WRKSRC}/config.toml.example ${WRKSRC}/config.toml.sample
> + ${CP} ${WRKSRC}/internal/helper/fstype/detect_linux.go
> ${WRKSRC}/internal/helper/fstype/detect_freebsd.go
Making a symlink instead of copy should be faster and produce less I/O.
___
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: fast aarch64 computer for creating a port?
On 20.08.2019 14:44, Ronald Klop wrote: > Hello, > > I'm trying to create a port for Mongodb 4.2. To aarch64 and amd64. > Especially my RPI3 for aarch64 takes about 2 days to compile this. Does the > FreeBSD community have a fast aarch64 machine I could use to do test work? > Maybe some access to a jail could be provided. When I was working with very slow MIPS32 hardware, I used qemu-user-static port that allows you to use fast amd64 machine to build ports for MIPS32 as if it was real MIPS32 box but quicker. Very handy. You just start it as you would start plain chroot command and voila. mipsworld="/usr/obj/nanobsd.mips/_.w" mount -t devfs devfs $mipsworld/dev mount -t nullfs /usr/ports $mipsworld/usr/ports chroot $mipsworld /usr/local/bin/qemu-mips-static /bin/sh -E Give it a try. ___ 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: git submodule
29.08.2019 12:55, Cy Schubert wrote: > 2) Have the port download two tarballs from github. But, how, elegantly? Take a look at sysutils/fusefs-webdavfs for example. ___ 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: Is IPV6 option still necessary?
On 07.10.2019 13:18, Yasuhiro KIMURA wrote: > On October 10, 2012 IPV6 option of all ports was enabled by > default. Commit message said "We are in 2012, it is time to activate > IPV6 options by default everywhere". > > And now we are in 2019. IPv6 is more widely used than 2012. So I > wonder if IPV6 option is still necessary. > > If you use official packages then you always use IPv6-enabled > binaries. And even if you build packages by yourself you still use > IPv6-enabled ones unless you disable IPV6 option. So I think at most > only a few people uses IPv6-disabled packages. > > Are there anybody who still disables IPV6 option for some serious > reason such as working around IPv6-related problem? If there aren't > then I think it's time to remove IPV6 option from ports framework. Think about embedded systems designed for internal use mostly/only (limited or no global connectivity) with very constrained space for a code. Ability to reduce code bloat is good thing. ___ 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: Omg upgrade wants to install MySQL
02.11.2019 20:48, @lbutlr wrote: > I have mariadb101 (client and server) installed, but when looking at what pkg > update will do, one of the things it will do is install MySQL. Is there > something I need to do to tell it to use MariaDB instead? > > Since I am here, it also wants to install a bunch of X11 packages, but I > neither want nor have any desktop environment installed, so similar question, > how can I tell pkg to run in “don’t enable GUIs” mode? Your choices are: - you may use default package repository and then you must use default package builting options and flavours, e.g. MySQL and not MariaDB, packages built with X11 options enabled etc.; - or you may use non-default packages (f.e. MariaDB instead of MySQL) and then you either build and use your own package repository containing packages built with your preferences; - or you just build some packages using ports while using default package repository for distinct packages and don't use "pkg upgdate". I prefer third option. Sometimes it is handy to "pkg lock" packages you installed from ports buiklt with non-default options, too. ___ 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: Omg upgrade wants to install MySQL
03.11.2019 9:20, @lbutlr wrote: > On 02 Nov 2019, at 19:35, Eugene Grosbein wrote: >> I prefer third option. Sometimes it is handy to "pkg lock" packages you >> installed from ports buiklt with non-default options, too. > > If I could tell which pkg install is going to install MySQL and libX stuff I > would lock those, but I Dion’t see anyway to check that. You need to lock MariaDB. > And it does seem odd that pkg is still assuming MySQL and desktop FreeBSD. > I know of many 120 FreeBSD servers and not one has a GUI desktop. > I mean, I am sure they exist, but they must be a pretty tiny sliver. First, it is NOT pkg assuming anything. Package repository has packages built from ports with their *default* options and pkg merely uses them. Second, support of X headers/formats/libraries does not assume "desktop" FreeBSD and does not install any graphical environment but generally only some small headers or libs, not even libX11 not to mention heavy window managers or desktop environment. ___ 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: Omg upgrade wants to install MySQL
On 03.11.2019 21:03, @lbutlr wrote: >>> On 02 Nov 2019, at 19:35, Eugene Grosbein wrote: >>>> I prefer third option. Sometimes it is handy to "pkg lock" packages you >>>> installed from ports buiklt with non-default options, too. >>> >>> If I could tell which pkg install is going to install MySQL and libX stuff >>> I would lock those, but I Dion’t see anyway to check that. >> >> You need to lock MariaDB. > > MariaDB *is* locked. Both client and server. Pkg update was still going to > install MySQL. pkg has no choice, as official package repo contains packages built with MySQL dependency only. >>> And it does seem odd that pkg is still assuming MySQL and desktop FreeBSD. >>> I know of many 120 FreeBSD servers and not one has a GUI desktop. >>> I mean, I am sure they exist, but they must be a pretty tiny sliver. >> >> First, it is NOT pkg assuming anything. Package repository has packages >> built from ports with their *default* options >> and pkg merely uses them. > > Fine. Ports assuming MySQL. Yes. You still may change defaults and rebuild those ports yourself. Same with X11 support. ___ 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: net-snmp crash
19.11.2019 4:22, Michael W. Lucas wrote: > Hi, > > I can reliably crash net-snmp with an snmpset. Worth a formal bug > report? > > $ uname -a > FreeBSD freebsdtest 12.0-RELEASE-p10 FreeBSD 12.0-RELEASE-p10 GENERIC amd64 > > $ pkg info net-snmp > net-snmp-5.7.3_20,1 > Name : net-snmp > Version: 5.7.3_20,1 > Installed on : Wed Oct 9 15:22:24 2019 EDT > ... > > Detail: > > $ sysctl net.inet.ip.forwarding > net.inet.ip.forwarding: 0 > > $ snmpget freebsd IP-MIB::ipForwarding.0 > IP-MIB::ipForwarding.0 = INTEGER: notForwarding(2) > > $ snmpset freebsd IP-MIB::ipForwarding.0 i 1 > Timeout: No Response from freebsd > > Yep, the agent is dead: > > $ pgrep snmpd > $ > > The sysctl change took place, however: > > $ sysctl net.inet.ip.forwarding > net.inet.ip.forwarding: 1 > > I can restart the agent and reverse the change, but snmpd crashes > again. > > So: worth a bug report, or no? Yes, and this should be easy to debug and fix provided net-snmpd port built WITH_DEBUG=yes to include debugging symbols and coredumps enabled. signature.asc Description: OpenPGP digital signature
Re: replacement of security/ipsec-tools
On 03.01.2020 05:06, Michael Grimm wrote: > I am running ipsec-tools to implement a VPN tunnel (esp) between two hosts > for years now. > > But this statement on http://ipsec-tools.sourceforge.net makes me think about > an alternative: > The development of ipsec-tools has been ABANDONED. > ipsec-tools has security issues, and you should not use it. Please > switch to a secure alternative! > > Could you provide me with links where I could find more details about the > above mentioned 'security issues'? Our port of ipsec-tools has fixes for all known security issues (f.e. CVE-2016-10396), so you may safely continue using it provided you have latest port/package. ___ 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 with "DEBUG" symbols
16.01.2020 23:31, Carmel NY пишет: > Hypothetically, suppose I wanted to build my entire ports system with > "debug" symbols; would putting: > > WITH_DEBUG_PORTS=* > > in the "make.conf" file work? > > Asking for a friend. This should work for /etc/make.conf: WITH_DEBUG=yes ___ 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: cereal: fails to build on pure 64 bit systems
25.01.2020 17:38, Hinnerk van Bruinehsen wrote: > Hello, > > the newly introduced build for cereal fails to build on my system, > because I don't have 32 bit compatibility stuff enabled. > > The failure is caused by the default settings of enabling portability > testing. I have attached a patch that fixes this for me by disabling the > portability tests. > > I also disabled -WError for the build, because it caused a build failure > (because of unused CFLAGS for the build, -pie in my case). > Since this is a non default setting, I guess that the last change is > debatable, but while I am a big fan of -WError during development, I > think it's not that great for packaging/distribution. I've committed cereal. I'll look at this. ___ 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: cereal: fails to build on pure 64 bit systems
25.01.2020 17:38, Hinnerk van Bruinehsen wrote: > Hello, > > the newly introduced build for cereal fails to build on my system, > because I don't have 32 bit compatibility stuff enabled. > > The failure is caused by the default settings of enabling portability > testing. I have attached a patch that fixes this for me by disabling the > portability tests. > > I also disabled -WError for the build, because it caused a build failure > (because of unused CFLAGS for the build, -pie in my case). > Since this is a non default setting, I guess that the last change is > debatable, but while I am a big fan of -WError during development, I > think it's not that great for packaging/distribution. Thanks! Fixed in r524136. ___ 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: Good CLI BitTorrent client?
04.03.2020 21:12, @lbutlr wrote: > Sice people are talking about GUI botttorrent clients, are there decent ones > that are CLI? There is "transmission" acting like a daemon. You may manage it using CLI, or GUI, or web interface with any browser. ___ 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: users of xorg, in particular on FreeBSD 11.3
21.03.2020 6:41, Niclas Zeising wrote: > [ This is cross-posted across several mailing lists for maximum visibility. > Please respect reply-to and keep replies to x...@freebsd.org . Thank you! ] > > In order to improve support when using evdev to manage input devices, in > particular keyboards, we have switched the default in x11/libxkbcommon to the > evdev instead of the legacy ruleset. This was done in ports r528813 . > > On FreeBSD 11.3, the default configuration still requires the legacy ruleset. > > If you are using FreeBSD 11.3, or if you are using xf86-input-keyboard on > FreeBSD 12 or later, you need to change the ruleset used by x11/libxkbcommon. > > If you have issues with your keyboard, most notably arrow keys, and if > /var/log/Xorg.*.log shows that the "kbd" or "keyboard" driver is being used, > you need to switch to legacy rules by setting the environment variable > XKB_DEFAULT_RULES to xorg. > > The easiest way to accomplish this is by adding it to your shell startup file. > > As an example, for users of [t]csh, put > setenv XKB_DEFAULT_RULES xorg > in ~/.login > > For users of bourne type shells (sh, bash, ksh, zsh, ...) instead put > export XKB_DEFAULT_RULES=xorg > in ~/.profile Please consider improving x11/libxkbcommon so that it uses -Ddefault-rules=xorg if OSVERSION notes 11.x at build time, so there would be no breakage for us building xorg from ports. ___ 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: lsof marked ignored
21.03.2020 4:30, @lbutlr wrote: > On 20 Mar 2020, at 14:10, Robert Huff wrote: >> Adam Weinberger writes: >> ===>>> Currently installed version: lsof-4.93.2_9,8 ===>>> Port directory: /usr/ports/sysutils/lsof ===>>> This port is marked IGNORE ===>>> requires kernel sources >>> >>> That error should only occur if system sources are missing from >>> /usr/src. Check that they're still there, and if not then check them >>> out from svn. >> >> (Last time I checked ) >> Not only does it require kernel sources, but those sources need >> to match the running kernel. > > Why was this changed (I did not install the source and my /usr/src/ directory > is empty and has been since I moved to 12.1) Nothing changed really. lsof needs the whole file sys/fs/pseudofs/pseudofs.h for struct pfs_node and all other parts (types etc.) it uses from same file and it needs the definition of struct lock_owner from sys/kern/kern_lock.c. It tastes some other files in sys/ to enable -DHAS_LOCKF_ENTRY -DHAS_PAUSE_SBT -DHAS_CDEV2PRIV -DHASFUSEFS -DHAS_ZFS but does not really needs their contents, so these flags could be enabled unconditionally by the port. So if we could "export" pseudofs.h and struct lock_owner to /usr/include, then lsof could be built without need of kernel sources. ___ 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: openssl problem after 11 -> 12
14.04.2020 16:58, Per olof Ljungmark wrote: > I am at loss right now on how I could teach the FBSD-12 system to use the > older ciphers, it still works fine from 11. Easiest way would be untar'ing FreeBSD 11 base.txz into chroot area and copy your script there, too. Then use chroot to pkg install perl5 to be able run the script inside chroot. ___ 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: Bind 9.16 port error still lingers
03.05.2020 1:13, Per olof Ljungmark wrote:
> On 2020-05-02 19:29, The Doctor via freebsd-ports wrote:
>> On Sat, May 02, 2020 at 06:53:18PM +0200, Christoph Moench-Tegeder wrote:
>>> ## The Doctor via freebsd-ports (freebsd-ports@freebsd.org):
> [snip]
>
>> //Use with the following in named.conf, adjusting the allow list as needed:
>> key "rndc-key" {
>>algorithm hmac-md5;
>> secret "7ZbGK94NdSa2WACxx72W1w==";
>
> I suggest you change this ^ rather quickly, especially if it is a public
> name server.
This is a key for local (over 127.0.0.1) connections for rndc,
it can be abused by local users only, or if there is remotely expoitable
vulnerability
for running shell code. Still, should not be published so easily but no direct
harm
when system has no untrusted local users.
___
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: Bind 9.16 port error still lingers
03.05.2020 0:29, The Doctor via freebsd-ports wrote: > Then let's look at the file: [skip] Quickest way to unbreak your server: take default named.conf from the installation of version 9.16 and add your changes to it manually but keep default paths within lines "pid-file" and alike. That is, keep changes to default file as small as 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: accel-ppp
19.06.2020 0:09, The Doctor via freebsd-ports wrote: > Would anyone like to help me port this application? > > Very Linux based but coould be BSD convertible. > > > It would make a good addition to the net ports. We already have net/mpd5 in ports for this task. ___ 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: accel-ppp
19.06.2020 0:35, Kurt Jaeger wrote: > Which project is better maintained ? > > mpd5 had it's latest release in 2016, but commits until recently. > accel-ppp had it's latest release in August 2019 and also commits > until recently. mav@ and myself commit to upstream repo as needed, and there is another one person. I maintain the port also. ___ 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: accel-ppp
19.06.2020 0:34, The Doctor via freebsd-ports wrote: > Wonder if my mpd5.conf is configured properly? It depends on your goals as mpd5 is versatile. It has extensive logging and documentaion. ___ 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: Makefile practice
11.07.2020 1:23, Harry Newton wrote: > I look after a port that has a poor Makefile [the one supplied with the > distribution, not the FreeBSD port Makefile]. The principal problem is > where it installs things. > > To get the port to do the right thing, I could either: heavily patch the > supplied Makefile or: move files around in the stage tree. > > Could someone give me a steer about recommended practice ? It's up to porter. I tend to keep things simple: if moving files around in the stage tree is simplier, do it with post-install target of the port. We have large number of examples in the ports tree of post-install usage. If it is simplier with small correction of software's Makefile or Makefile.in correcting DESTDIR, do it with a patch or post-patch target of the port. ___ 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: Portmaster and less
01.08.2020 3:24, @lbutlr wrote: > When postmaster displays the package messages after installing, it calls > less, which forces you to hit 'q' to exit, and when you quit less, it clear > the buffer on the screen and returns you to the display of the compile > process. > > Is there anyway to change this behavior so that less is called with -E / > --QUIT-AT_EOF? Yes: export MORE="-E" or export LESS="-E" Our "more" command is another name (link) for "less" modifying its behaviour. ___ 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: [HEADS UP] Planned deprecation of portsnap
06.08.2020 6:02, Tatsuki Makino wrote : > Is there any command other than "rm -rf /usr/ports ; portsnap extract" > that can be easily repaired? svnlite revert -R /usr/ports ___ 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: [HEADS UP] Planned deprecation of portsnap
06.08.2020 13:23, Doug Hardie wrote: >> On 5 August 2020, at 21:30, Eugene Grosbein wrote: >> >> 06.08.2020 6:02, Tatsuki Makino wrote >> : >>> Is there any command other than "rm -rf /usr/ports ; portsnap extract" >>> that can be easily repaired? >> >> svnlite revert -R /usr/ports > > > master# svnlite revert -R /usr/ports > svn: E155007: '/usr/ports' is not a working copy > master# > master# rm -rf /usr/ports/* > master# svnlite revert -R /usr/ports > svn: E155007: '/usr/ports' is not a working copy If portsnap's deprecated, one uses "svnlite checkout" to replace portsnap's data with data of Subversion, then "svnlite revert" would work. ___ 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: [HEADS UP] Planned deprecation of portsnap
07.08.2020 18:10, Ashish SHUKLA wrote: > Is there a similar seed file for subversion snapshot, that one can > download, extract, and "svn up" ? > > I was trying to "svn co" the ports tree, and it keeps dying in the > middle of checkout every few minutes. ftp://ftp.freebsd.org/pub/FreeBSD/development/subversion/ Last updated Feb 26 2020, though. Still usable for update to current state. ___ 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: How to make 'named' rc script invokded earlier at boot time
30.04.2021 14:30, Yasuhiro Kimura wrote: > I installed dns/bind916 on my home server and configured it so it > worked as both authoritative and recursor. Then I added > 'nameserver 127.0.0.1' to /etc/resolv.conf and everything worked fine. > > But after updating OS from 12.2-RELEASE to 13.0-RELEASE I noticed > execution of some rc scripts fails at boot time because of DNS lookup > error. And I also found these scripts are executed earlier than > 'named'. > > Now let me use 'ntpdate' as an example. named sometimes *requires* correct time to be set before it is started, so you should either use some IP addressess for NTP bootstrapping at boot time, or put NTP server hostname to /etc/hosts with its IP, so it resolves before named fires. ___ 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: looking for port origin for executable
05.05.2021 0:28, Piotr Smyrak wrote: >> Would some kind soul please tell me which port installs the >> executable "g-ir-scanner"? I was purging unused ports and seem to >> have done this one by mistake. > > When I hit a wall like this, this is my usual way to get around without > any additional tools: > > $ find /usr/ports -name pkg-plist | xargs grep -l bin/g-ir-scanner Or just: locale g-ir-scanner Which is much faster as it uses indexed /var/db/locate.database ___ 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: Making a port to use OpenSSL of ports collection on FreeBSD 11.x
06.05.2021 10:49, Dima Panov wrote: > Chris, your suggestion leads to dll hell due to mix-links between ssl > libraries :( > At least, your setup easily face up situation where one lib will be built > with “port openss” and consumers still get a “base openssl”. > DEFAULT_VERSION here is set to avoid a such situation — the whole ports > collection should be linked with ONE ssl/crypto library. I disagree. There is no reason for "leaf" ports to depend on ports version of openssl and this is impossible in come cases. For example, net/mpd5 port that links with base libfetch that links with base openssl. So, net/mpd5 must NOT be linked with ports openssl and frankly, it needs not. Global inflexible knob for whole ports tree is bad thing. ___ 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: pkg 1.3.8 requested but not available?
On 23.09.2014 16:09, Baptiste Daroussin wrote: >> Just a thought here - why (like .rpm and .deb - and the reason I hate >> them so much) are you making the package manager version a dependency of >> a package? I can understand if there are new features that you may need >> to use a later version to get those features, but making a package >> dependent on the package manager rather than displaying a warning that a >> feature is missing is the brain dead way that plagues upgrades for >> redhat and debian. Of course if your intent is to make FreeBSD into >> another Linux distro just with a different kernel, continue. >> > > There are new feature, that is why, the required version will be only bumped > when there will be new features used by the ports tree, not on every pkg bump Please, please do document what new features resulted in MINIMAL_PKG_VERSION bump. And please, delay bumping of MINIMAL_PKG_VERSION until packages of pkg itself are available from the repo. Eugene Grosbein ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Pass options to dependency
Hi! How can a port (its Makefile) pass a build option to BUILD_DEPENDS? For example, devel/ragel has: DOCS_USE= TEX=latex:build DOCS_BUILD_DEPENDS= fig2dev:print/transfig And "make -C /usr/ports/devel/ragel all-depends-list" shows HUGE list of its dependencies completely unneded for a port that just needs to use BUILD_DEPENDS=ragel:devel/ragel The reason is that bsd.options.mk includes PORT_OPTIONS+= DOCS unless user option NOPORTDOCS is set. Is it possible to specify something like OPTIONS_EXCLUDE=DOCS for BUILD_DEPENDS entity? Eugene Grosbein ___ 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: Pass options to dependency
05.06.2017 18:51, Matthew Seaman пишет: > On 05/06/2017 10:56, Eugene Grosbein wrote: >> How can a port (its Makefile) pass a build option to BUILD_DEPENDS? >> For example, devel/ragel has: >> >> DOCS_USE= TEX=latex:build >> DOCS_BUILD_DEPENDS= fig2dev:print/transfig >> >> And "make -C /usr/ports/devel/ragel all-depends-list" shows HUGE >> list of its dependencies completely unneded for a port that just >> needs to use BUILD_DEPENDS=ragel:devel/ragel >> >> The reason is that bsd.options.mk includes PORT_OPTIONS+= DOCS >> unless user option NOPORTDOCS is set. >> >> Is it possible to specify something like OPTIONS_EXCLUDE=DOCS >> for BUILD_DEPENDS entity? >> > > Generally what you would do is create a slave port of the dependency > with the options settings you require. Doing this to turn off the DOCS > option would be unprecedented though. > > I believe the consensus nowadays is that DOCS should control installing > documentation that takes little or no effort to generate. If you need > to install a huge dependency tree in order to generate documentation, > then that should be controlled using a different option. Whether to > have that option default to either ON or OFF is at the discretion of the > maintainer. > > So my advice here is open a PR to get devel/ragel modified, and in the > mean time try and ignore all those unwanted dependencies while you work > on your own port. It would be more useful to have general way to build a dependency with needed set of options or at least introduce NODEPDOCS similar to NOPORTDOCS, wouldn't it? Eugene Grosbein signature.asc Description: OpenPGP digital signature
Re: How to stop ports recompiling gcc, llvm, etc.?
13.06.2017 22:25, Rastko P пишет: > I have some experience with FreeBSD. I don't mind building ports. You > know sometimes it's necessary (most FreeBSD software is ported, and > needs to be configured) > > > But I cannot find in the documentation how to prevent a port > re-compiling different versions of GCC or other such monsters, when I > already compiled them. Port build process won't rebuild a compiler if it is already built and installed. You'll get no definite answer until you supply details such as port you need in first place and at least the beginning of its building log. ___ 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: Best practice to tail a log and start it as service using rc.d scripts
03.07.2017 23:20, Matthias Fechner пишет: > Dear all, > > I just in the process to test mailtrain (https://mailtrain.org/) and if > it is working I would like to create a port for FreeBSD. > > That mailtrain can handle bounce message with postfix together it is > necessary to tail the postfix log and pass it to mailtrain, using a > command like this: > tail -F -n +0 /var/log/maillog | nc localhost 5699 - > > Is there a best practice approach on how to do this on FreeBSD? > I would require now a startup script in /usr/local/etc/rc.d to start > this kind of tail or is there a better mechanism in FreeBSD available? > If not, does anyone have some kind of template/example on how to start a > program like tail as daemon so FreeBSD can stop/restart it with the > service command? For logs written using standard syslog service, there is much effective way. 1. The syslogd daemon can run a subprocess and duplicate log stream to its standard input. For example, write to its config: mail.* "|exec nc localhost 5699 -" See man syslog.conf for details. You can even pipe not full log but some part of it, f.e. `mail.notice' instead of `mail.*' for important event only (no debug lines, no informational mesages). 2. And you need not modify system /etc/syslog.conf but create file named like /usr/local/etc/syslog.d/mailtrain.conf with that single line. Then use `service syslogd reload' to apply additional configuration and syslogd will run your "addon" when corresponding logs is updated. For deinstallation/deactivation procedure just remone mailtrain.conf and use `service syslogd reload' 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"
Re: Best practice to tail a log and start it as service using rc.d scripts
05.07.2017 1:02, Matthias Fechner wrote: > Am 03.07.2017 um 20:21 schrieb Eugene Grosbein: >> For logs written using standard syslog service, there is much >> effective way. >> 1. The syslogd daemon can run a subprocess and duplicate log stream to its >> standard input. For example, write to its config: >> >> mail.* "|exec nc localhost 5699 -" >> >> See man syslog.conf for details. You can even pipe not full log >> but some part of it, f.e. `mail.notice' instead of `mail.*' >> for important event only (no debug lines, no informational mesages). > thanks for this, I will test that more in detail. > I correctly have the problem if the mailtrain app is stopped, it closes > the network socket which causes nc to terminate. > This is not what I would like to have, but maybe syslog is restarting nc > in this case? This is documented in the syslog.conf(5) manual page I mentioned previously: The command will only be started once data arrives that should be piped to it. If it exited later, it will be restarted as necessary. > If not syslog is maybe not the right solution, but I will test this first. > >> 2. And you need not modify system /etc/syslog.conf but create file >> named like /usr/local/etc/syslog.d/mailtrain.conf with that single line. >> Then use `service syslogd reload' to apply additional configuration >> and syslogd will run your "addon" when corresponding logs is updated. > > are you sure about this? > I cannot find that described in any man page, /etc/defaults/rc.conf neither. > I tested it but it is not working. > Just added a file: /usr/local/etc/syslog.d/mailtrain.conf with content: > mail.* /var/log/maillog.err > > I touched the /var/log/maillog.err and reloaded syslogd. > But nothing appears in that file. I should have mentioned before that this depends on FreeBSD version. This feature presents in FreeBSD 11 and newer and was merged to 10-STABLE but for some reason was removed from 10-STABLE several days ago by request of jhb@. ___ 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: Writing a port make deinstall
12.07.2017 9:38, blubee blubeeme wrote: > How do I properly write this Makefile so deinstall works as expected? Just add these files to pkg-plist and they are removed automatically. ___ 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: getbdf-1.02
25.07.2017 10:35, jb wrote: > hi BSD, > > Where the fuck is this thing ? I am so sick of Free ! Open Source ! > "packages" that don't have the source. > > I dont want ports, I don't want packages, I don't want apt yumget or any > other hand-holding crap, suckmydick-letmeinstallthis, I want the source. > > But it's nowhere to be found. Your website is worthless shit. > > Guess I am old-fashioned :( Learn to search the web, newbee: http://www.gnu-darwin.org/distfiles/getbdf.tar.Z ___ 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: Help needed by first-timer porter
04.08.2017 12:43, Manish Jain пишет:
> The question is, at this stage, where do I get the default
> stage-definitions file from. If I specify stage-definitions among the
> package's listing, it will go into one of the standard directories,
> which is not what I want.
Please re-read Porter's Handbook:
https://www.freebsd.org/doc/en/books/porters-handbook/book.html
It says a port must install all its files under ${PREFIX} only (/usr/local by
default).
There is DATADIR for such shared files (expanded to PREFIX/share/PORTNAME).
You should install it there using INSTALL_DATA macro and use %%DATADIR%% in the
pkg-plist,
so it gets to /usr/local/share/mkdesktop/ assuming you name your port
"mkdesktop".
___
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: Help needed by first-timer porter
04.08.2017 20:34, Manish Jain wrote:
> There is a hiccup, which I am fairly certain a few others would have
> experienced too. So I look to resolve the situation of MASTER_SITES,
> which it appears is mandatory.
It is not. If your port has few little source files, you can create files/
subdirectory,
put files there, refer them like ${FILESDIR}/source.sh in port's Makefile and
use:
MASTER_SITES= # none
For example, we have net/tcpmssd, math/octave-forge-base and even
ports-mgmt/portlint itself
being this kind of ports.
___
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: standard locations for port files
31.08.2017 22:07, Ernie Luzar wrote: > Lets say I have a product that I want to port to Freebsd. > > Were is the standard location for the log file and PID file. > > Would it be in > /usr/local/etc/product/product.log > /usr/local/etc/product/product.pid > > or > > /var/log/product.log > /var/run/product.pid FreeBSD cleans /var/run at boot time, so /var/run/product.pid is guaranteed to not exist when "product" is first started that time. On the other hand, /usr/local/etc/product/product.pid can (and will) exist after unclean system reboot and it can contain a PID of already running another process, so that simple check for double-start would fail. So, use /var/run for PID files to be safe. ___ 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: Kibana53 - Not suitable node version available?
On 13.09.2017 16:29, Mark Clarke wrote: > Hi all, > > I posted a comment on a bug report regarding kibana53 failure to start > by default on 11.0 and 11.1. I installed Kibana53 with pkg. From the bug > report it looks like node 8.2 or higher is required. The maintainer > asked me to post here instead to follow up. Miroslav pointed out in his > comment that it will work with node-8.3.0 but I cannot find this in > port nor in pkg. I have upgaded my ports tree via svn and all I have is > node, and node010. Node is version 8.1 which is not compatible. How do I > get more recent node versions in my ports tree or in pkg? www/node was upgraded from 8.3.0 to 8.4.0 almost a month ago. You could remove your ports tree and fetch it again from official mirror as your source is obviously stale. ___ 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: FireFox memory usage
On 15.09.2017 18:35, Andrea Venturoli wrote: > Hello. > > I'm on 10.3/amd64 with firefox-esr 52.3.0. > > Since a few days my 4GiB desktop is crawling due to swap usage and > looking at top, I see FireFox using almost 7GiB of RAM (SIZE column), > 2.5 of which are "RES". > > I don't think this is normal, since I'm not doing anything fancy (i.e. > running webapps or opening tenth of windows/tabs). > > I've been using FF for several years and, while I recognize it's > constantly getting slower, more bloated and more resource hungry, I find > it hard to believe such a sudden rise in memory usage might be normal. > > One suspect I have is some kind of memory leak, since closing FF and > reopening the same sites I had opened before will drop the RAM usage to > under 1GiB. > > I'm lost at what to look at... I don't even know if it's an upstream or > FreeBSD problem. > > I start by asking if anyone else is seeing this and/or if anything in > the way it is ported or in its dependencies could be the cause of this. It leaks like female animal under Windows, too. This depends heavily on your set of addons, though. For example, NoScript addon may provoke Javascript code of sites to leak memory constantly retrying to get their garbage. In such case, close/reopen a tab may help for some period of 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: slrn from ports segfaults when running
On 15.09.2017 20:00, tech-lists wrote: > Hello ports@ > > slrn as compiled from ports will segfault after a short time when > reading a newsgroup. The fix is to deinstall the port, grab the source > via git from git://git.jedsoft.org/git/slrn.git and compile it > yourself and install. > > If someone can tell me how to diagnose a segfault, I'm happy to help > provide more diagnostics. First, try to rebuild port using "make WITH_DEBUG=yes" and run non-stripped binary from stage/ subdirectory of port building ares. Then get corefile and use gdb to get backtrace. ___ 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: FireFox memory usage
On 15.09.2017 20:24, Andrea Venturoli wrote: >> This depends heavily on your set of addons, though. > > I just have AdBlockPlus and DownThemAll (which I hadn't used today, though). Try to run it for some time with all addons disabled and if this helps, enable addons one-by-one restarting FF fully 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: slrn from ports segfaults when running
On 15.09.2017 20:57, tech-lists wrote: > On Fri, Sep 15, 2017 at 08:07:54PM +0700, Eugene Grosbein wrote: > >> First, try to rebuild port using "make WITH_DEBUG=yes" and run non-stripped >> binary >>from stage/ subdirectory of port building ares. Then get corefile and >> use gdb to get backtrace. > > I had to run make install because running it from the staging > directory gives this error: > > slrn 1.0.3 > Unable to locate slrn.sl on load path > Configuration error: Unable to load startup file > The hardcoded load path is set to: /usr/local/share/slrn/slang > You make need to set the SLRN_SLANG_DIR environment variable. > slrn fatal error: > Error initializing S-Lang interpreter. > > so, ran make install: This installs slrn.sl to right place. You can still run debugging binary or just manually copy it to /usr/local/bin/ ___ 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: slrn from ports segfaults when running
15.09.2017 21:56, tech-lists пишет: > On Fri, Sep 15, 2017 at 09:12:57PM +0700, Eugene Grosbein wrote: >> On 15.09.2017 20:57, tech-lists wrote: >>> On Fri, Sep 15, 2017 at 08:07:54PM +0700, Eugene Grosbein wrote: >>> >>>> First, try to rebuild port using "make WITH_DEBUG=yes" and run >>>> non-stripped binary >>>> from stage/ subdirectory of port building ares. Then get corefile and >>>> use gdb to get backtrace. >>> >>> I had to run make install because running it from the staging >>> directory gives this error: >>> >>> slrn 1.0.3 >>> Unable to locate slrn.sl on load path >>> Configuration error: Unable to load startup file >>> The hardcoded load path is set to: /usr/local/share/slrn/slang >>> You make need to set the SLRN_SLANG_DIR environment variable. >>> slrn fatal error: >>> Error initializing S-Lang interpreter. >>> >>> so, ran make install: >> >> This installs slrn.sl to right place. You can still run debugging binary >> or just manually copy it to /usr/local/bin/ > > OK, did that (and set the NNTPSERVER env var, coredump happened on > selecting a newsgroup. It happens if there's a lot of articles in the > newsgroup. > > This GDB was configured as "amd64-marcel-freebsd". > (gdb) core slrn.core > Core was generated by ./slrn -f /root/.jnewsrc --create'. > Program terminated with signal 11, Segmentation fault. > #0 0x000801a92421 in ?? () > (gdb) bt > #0 0x000801a92421 in ?? () > #1 0x7fffdc10 in ?? () > #2 0x0008026014b7 in ?? () > #3 0x7fffdbc0 in ?? () > #4 0x in ?? () This does not seem to be debugging version. Perhaps, stage/ directory already contains stripped binary. Use 'file slrn' to be sure. Run unstripped slrn binary from building directory instead then. And may be, this port does not respect WITH_DEBUG=yes knob. ___ 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: slrn from ports segfaults when running
On Sat, Sep 16, 2017 at 12:24:18AM +0100, tech-lists wrote: > slrn freezes when the process is attached, so ran bt from gdb: No, just use "gdb /path//to/slrn /path/to/corefile" It should report segmentation fault and you could obtain backtrace. ___ 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: slrn from ports segfaults when running
16.09.2017 8:46, tech-lists wrote: > # gdb ./slrn ./slrn.core > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and > you are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for > details. > This GDB was configured as "amd64-marcel-freebsd"... > Core was generated by ./slrn'. > Program terminated with signal 11, Segmentation fault. > Reading symbols from /usr/local/lib/libslang.so.2...done. > Loaded symbols for /usr/local/lib/libslang.so.2 > Reading symbols from /usr/local/lib/libuu.so.3...done. > Loaded symbols for /usr/local/lib/libuu.so.3 > Reading symbols from /usr/local/lib/libssl.so.43...done. > Loaded symbols for /usr/local/lib/libssl.so.43 > Reading symbols from /usr/local/lib/libcrypto.so.41...done. > Loaded symbols for /usr/local/lib/libcrypto.so.41 > Reading symbols from /usr/local/lib/libintl.so.8...done. > Loaded symbols for /usr/local/lib/libintl.so.8 > Reading symbols from /lib/libncurses.so.8...Reading symbols from > /usr/lib/debug//lib/libncurses.so.8.debug...done. > done. > Loaded symbols for /lib/libncurses.so.8 > Reading symbols from /lib/libc.so.7...Reading symbols from > /usr/lib/debug//lib/libc.so.7.debug...done. > done. > Loaded symbols for /lib/libc.so.7 > Reading symbols from /lib/libm.so.5...Reading symbols from > /usr/lib/debug//lib/libm.so.5.debug...done. > done. > Loaded symbols for /lib/libm.so.5 > Reading symbols from /usr/lib/i18n/libiconv_std.so.4...Reading symbols > from /usr/lib/debug//usr/lib/i18n/libiconv_std.so.4.debug...done. > done. > Loaded symbols for /usr/lib/i18n/libiconv_std.so.4 > Reading symbols from /usr/lib/i18n/libmapper_serial.so.4...Reading > symbols from > /usr/lib/debug//usr/lib/i18n/libmapper_serial.so.4.debug...done. > done. > Loaded symbols for /usr/lib/i18n/libmapper_serial.so.4 > Reading symbols from /usr/lib/i18n/libmapper_none.so.4...Reading > symbols from > /usr/lib/debug//usr/lib/i18n/libmapper_none.so.4.debug...done. > done. > Loaded symbols for /usr/lib/i18n/libmapper_none.so.4 > Reading symbols from /usr/lib/i18n/libmapper_646.so.4...Reading > symbols from > /usr/lib/debug//usr/lib/i18n/libmapper_646.so.4.debug...done. > done. > Loaded symbols for /usr/lib/i18n/libmapper_646.so.4 > Reading symbols from /libexec/ld-elf.so.1...Reading symbols from > /usr/lib/debug//libexec/ld-elf.so.1.debug...done. > done. > Loaded symbols for /libexec/ld-elf.so.1 > #0 _citrus_NONE_stdenc_mbtocs (ce=,csid= optimized out>, idx=0x7fffe870, s=0x7fffe868,n= optimized out>, ps=0x0, nresult=0x7fffe860, > hooks=0x0) >at /storage/usr/src/lib/libc/iconv/citrus_none.c:96 >96*idx = (_index_t)(unsigned char)*(*s)++; >(gdb) > backtrace: > > (gdb) bt > #0 _citrus_NONE_stdenc_mbtocs (ce=,csid= optimized out>, idx=0x7fffe870, s=0x7fffe868,n= optimized out>, ps=0x0, nresult=0x7fffe860, > hooks=0x0) >at /storage/usr/src/lib/libc/iconv/citrus_none.c:96 You could try to remove --with-non-gnu-iconv from port's Makefile and rebuild slrn. Any way, you better fill a PR attaching this debugging output you already collected. ___ 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: EXTRA_PATCHES considered harmful?
24.09.2017 4:39, Julian Elischer wrote:
> currently if you set EXTRA_PATCHES and the port you are making decides to
> build a second port as a dependency, EXTRA_PATCHES is passed to the second
> port which them obiously fails to patch it.
>
> e.g. cd /usr/ports/emulators/open-vm-tools-nox11; Make
> EXTRA_PATCHES=/foo/bar/patch1
>
> will fail when it tries to apply the patch files to each dependency.
>
> AM I doing something wrong here?
Obviously, one should not use EXTRA_PATCHES in command line,
rather define an option for distinct port's Makefile and
turn option on/off in command line instead.
For example, converters/iconv's Makefile has:
OPTIONS_DEFINE= CCSUTIL
CCSUTIL_EXTRA_PATCHES_OFF= ${FILESDIR}/extra-patch-ccs_Makefile
And you can run "make WITH_CCSUTIL=yes"
___
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: portmaster, portupgrade, etc
> Why compile ports directly on a box that is so hardware constrained that it > will take multiple hours to do, when a "pkg update; pkg upgrade" takes only > a few minutes? I tried really hard to run small virtual machine (1GB RAM, 25G disk) hosted at Hetzner without using ports and can say it's impossible. Pre-built packages from official repo are just too heavy and bloat the system with unneeded run-time dependencies not to mention impossibility to apply hot-fix in form of a patch. And running own repository is just not an option for such system. portupgrade (or analog) plus ZFS compressed svn-updates ports tree is lightest option in practice: zfs_load="YES" vfs.zfs.arc_max="40M" vfs.zfs.vdev.cache.size="8M" vfs.zfs.prefetch_disable="1" vfs.zfs.vdev.trim_on_init="0" vfs.zfs.compressed_arc_enabled="1" You can even run UFS-based system with /usr/ports mounted occasionally and zfs.ko/opensolaris.ko unloaded when not needed to free memory. ___ 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: portmaster, portupgrade, etc
On 05.10.2017 04:22, Steve Kargl wrote: > I did not state that the "environment is constrained by poudriere". > The environment is contrained due to resource limits. If you > only have 1 Gb of memory and 5-10 GB diskspace, then using poudriere > with zfs and jails is a nonstarter. Yes, I'm aware that zfs is not > required. Can't find info on whether jails can be avoided. Having > say lang/llvm40 installed in /usr/local and in a jail would consumes > 2.6 GB. That's 1 port! In fact, a jail is not needed too. Just perform installworld to a /path, then mount -t devfs devfs /path/dev; mount -t nullfs /usr/ports /path/usr/ports and you are ready to build with chroot /path make -C /usr/ports/net/quagga package". Perhaps, you'll also need to setup /path/etc/resolv.conf unless you have caching DNS server running locally, so fetch(1) could download distfiles. ___ 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: portmaster, portupgrade, etc
On 05.10.2017 08:14, Adam Weinberger wrote: > Poudriere wants to be everything to everybody First poudriere will have to learn how to run without noticeable overhead compared to "just build from ports" before it could became "everything to everybody" and it needs to became part of base system for that purpose. ___ 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: Firefox became much slower
On 01.11.2017 18:53, Baho Utot wrote: >> My personal suggestion is to use noscript, most sites work quite fine >> without javascript and even more sites work fine by allowing only a few >> origins, but blocking dozens of third party scripts. +1 > Noscript results in sites not working, ever try youtube You did not try to configure it, did you? ___ 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"
