Re: Package database problems
Hi, first - I would say forget about the directories in /var/db/pkg - when manually running a "make install" for some port I get such a directory created as well. Important is the "local.sqlite" file where everything gets stored. For your problem, dunno which package pkg refuses to install due to some conflict, but it might be worth checking /usr/ports/UPDATING - if you've installed ports - and picking out the problematic port to see what happened, if documented of course. For installing something, lurk the package manually and give: pkg add -f what_ever.txz a try. Though, backup /var/db/pkg/local.sqlite before doing and hopefully pkg will recognize the file again as being installed by some package. Since changes are high your database might still be in a problematic state if a file belongs to 2 possible packages, remove both of them and reinstall the right one. For the future it might be worth reading Debian's apt-get and dpkg documentation to see what will be implemented next. On Thu, 16 Nov 2017, Paul Schmehl wrote: --On November 16, 2017 at 9:34:05 PM +0100 Kurt Jaeger wrote: You probably have to clean it up. I would do this: - use the list of old-style packages in /var/db/pkg, together with the output of pkg info, to generate a list of packages that you need after clean up. My list looks like this, approx. 2000 entries: - [...] devel/automake devel/automake-wrapper devel/automoc4 devel/binutils devel/bison [...] - - Then build all the packages from your list via poudriere, and generate a repo of all those up2date packages. - Then (this is dangerous, if done via remote, keep a few ssh sessions running in parallel, if one fails): mkdir /usr/local/OLD cd /usr/local mv * OLD/ - Now no packages are installed - re-add all the packages, restore the config from OLD/... Ugh. I didn't setup this server to begin with. I recall, a while back, instructions for switching to pkgng. Is that what wasn't done? Yes, something like that. Should I run pkg2ng now? Would that help? Paul Schmehl, Retired As if it wasn't already obvious, my opinions are my own and not those of my employer. *** "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: py27-fail2ban-0.10.1
Hi,
a simple setup that does the job for me:
In /etc/pf.conf (bge0 is my external interface)
--- SNIP ---
int_ext="bge0"
...
table
...
block in quick on $int_ext from to any
...
--- SNIP ---
And in ${PREFIX}/fail2ban/action.d defining a new "pf" action, e.g.
pf.conf
--- SNIP ---
[Definition]
actionban = /usr/local/bin/drop_ban
actionunban = /usr/local/bin/drop_unban
actioncheck =
actionstart =
actionstop =
[Init]
--- SNIP ---
And the "drop_ban" and "drop_unban" scripts:
for ban:
--- SNIP ---
#!/bin/sh
IP=$1
/sbin/pfctl -t badhosts -T add $IP
--- SNIP ---
for unban
--- SNIP ---
#!/bin/sh
IP=$1
/sbin/pfctl -t badhosts -T del $IP
--- SNIP ---
I'm using scripts instead of directly using actionban / actionunban to do
some additional things like running a tcpdrop, having some better logging.
Once done with all this, you can use "action = pf" in your jail.conf file.
Apart this I'd highly recommend to put all this into some configuration
system (Ansible, Puppet, Cfengine etc.).
Updating the package / port will overwrite your local changes !
Have fun & good luck
On Tue, 17 Oct 2017, Alex V. Petrov wrote:
Need a working sample for the new version of the port for pf.
-
Alex.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: sysutils/tmux - strange behaviour with new version 2.4
Le 16.05.2017 à 13:53, Miroslav Lachman a écrit : > David Wolfskill wrote on 2017/05/16 13:35: >> Oddly enough, I saw the distinction you pointed out... even though I >> read mail via mutt in a tmux window :-} > > Uhm... maybe it depends on source of the text? Or locale? Hi, I've been able to re-produce the issue, though setting: set -g default-terminal "screen-256color" in your tmux.conf seemed to help. Tested both under console and inside a running urxvt. Without that line: env | grep TERM gives me just "screen", having it set the above value. Dunno if that might be related to /etc/termcap the screen line that exists (note - dunno, unsure, just a guess). ___ 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: Recent devel/libclc update breaking graphics/dri - it seems
Hi, I guess it was the way I updated. First updating libclc, it pulled llvm40 in. Then I thought - ok, so llvm40 is the game now - removing llvm39 and doing a: "portmaster -o devel/llvm40 llvm39". Afterwards graphics/dri failed updating. I rolled back to the snapshot before these tasks were executed, then running a simple "portmaster -a" and things went through. Guess by "pressing" in llvm40 as replacement for llvm39 things started to go very wrong. Kind regards On Fri, 31 Mar 2017, Walter Schwarzenfeld wrote: Now it is the question, why it happens on your system. MAKE_LLVM_VER= 39 is explicit set in the masterport (lib/libGL) and compiles with llvm39 without problems on my system (10.3amd64). For the problem with llvm40 (I don't know if it is really relevant in the moment cause of MAKE_LLVM_VER) I opened a PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218251 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Recent devel/libclc update breaking graphics/dri - it seems
Hi, yip - that did it. Thanks On Fri, 31 Mar 2017, Walter Schwarzenfeld wrote: Try Makefile: +MESA_LLVM_VER= 39 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Recent devel/libclc update breaking graphics/dri - it seems
Hi every1, it seems - hopefully not just for me (sorry) - the recent devel/libclc update breaks graphics/dri. Upon updating libclc, llvm40 gets lurked into the system and graphics/dri gets rebuilt, using llvm40 - even if 3.9 is installed - for compilation. The compile then stops with. --- SNIP --- In file included from draw/draw_llvm.c:45: ./gallivm/lp_bld_intr.h:69:20: error: unknown type name 'LLVMAttribute'; did you mean 'LLVMAttribu teRef'? LLVMAttribute attr); ^ LLVMAttributeRef /usr/local/llvm40/include/llvm-c/Types.h:116:40: note: 'LLVMAttributeRef' declared here typedef struct LLVMOpaqueAttributeRef *LLVMAttributeRef; ^ draw/draw_llvm.c:1577:10: error: implicit declaration of function 'LLVMAddAttribute' is invalid in C99 [-Werror,-Wimplicit-function-declaration] LLVMAddAttribute(LLVMGetParam(variant_func, i), --- SNIP --- Even manually upgrading libclc, deinstalling llvm40 and reinstalling llvm39, at the latest when it comes to graphics/dri llvm40 gets pulled in again and the compile run fails. My guess (guess, crytal ball, lottery) is the update of libclc breaks graphics/dri due to llvm40 dependencies. Any useful idea on how to fix this ? My second guess (again with a crystal ball playing lottery) is that mesa 13.0.6 isn't playing nice with llvm4 atm. Kind regards ___ 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 showstopper
Hi, the quick and dirty way: pkg remove xf86-video-fbdev If pkg complains about dependencies, that will be removed as well, note them and then: pkg remove -f xf86-video-fbdev then reinstall the dependencies (was here the xorg meta-port and xorg-video-drivers meta port), then give portmaster another try. Good luck On Tue, 24 Jan 2017, The Doctor wrote: Getting ===>>> The x11-drivers/xf86-video-fbdev port has been deleted: Linux only driver ===>>> Aborting update on portmaster -a . What do I need to stop this from happening? ___ 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: LibreOffice fails to start
Hi, an, even if not really nice and recommended, work-around is to move the problematic file somewhere or rename it. That worked here, though my usage might not be the usage of someone else so it still might cause some pain somewhere. Le 13.11.2016 13:48, Grzegorz Junka a écrit: > After upgrading to 5.2.3 LibreOffice no longer starts. Error shown by > the libre office launcher: > > > The following application experienced an error and needed to close: > > libreoffice --calc > > /usr/local/lib/libreoffice/program/libvclplug_gtklo.so: Undefined symbol > "__cxa_thread_atexit" > > > > Compiled with poudriere on 10.3. Is this a known issue? Some googling > suggests that an incorrect version of glibc was used. > > > My options: > > > # This file is auto-generated by 'make config'. > # Options for libreoffice-5.2.3 > _OPTIONS_READ=libreoffice-5.2.3 > _FILE_COMPLETE_OPTIONS_LIST=CUPS GNOME GTK2 GTK3 JAVA KDE4 MMEDIA PGSQL > SDK SYSTRAY TEST VERBOSE WEBDAV > OPTIONS_FILE_SET+=CUPS > OPTIONS_FILE_UNSET+=GNOME > OPTIONS_FILE_SET+=GTK2 > OPTIONS_FILE_UNSET+=GTK3 > OPTIONS_FILE_UNSET+=JAVA > OPTIONS_FILE_SET+=KDE4 > OPTIONS_FILE_UNSET+=MMEDIA > OPTIONS_FILE_UNSET+=PGSQL > OPTIONS_FILE_UNSET+=SDK > OPTIONS_FILE_UNSET+=SYSTRAY > OPTIONS_FILE_UNSET+=TEST > OPTIONS_FILE_UNSET+=VERBOSE > OPTIONS_FILE_UNSET+=WEBDAV > > Greg > > > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: emulators/virtualbox-ose-kmod build error
Am Wed, 24 Feb 2016 22:04:29 +0200 Ivan Klymenko schrieb: After update from r295867 to r295994: ... /usr/local/bin/ccache cc -O2 -pipe -march=native -fno-strict-aliasing -DRT_OS_FREEBSD -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DSUPDRV_WITH_RELEASE_LOGGER -DVBOX -DRT_WITH_VBOX -w -DVBOX_WITH_HARDENING -DVBOX_WITH_64_BITS_GUESTS -DRT_ARCH_AMD64 -march=native -Werror -D_KERNEL -DKLD_MODULE -nostdinc -Iinclude -I. -Ir0drv -I. -I/usr/src/sys -fno-common -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -Wno-error-unused-function -Wno-error-pointer-sign -Wno-error-shift-negative-value -fvectorize -fslp-vectorize -fbloc ks -fcolor-diagnostics -mno-aes -mno-avx -std=iso9899:1999 -c /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c -o memobj-r0drv-freebsd.o --- assert-r0drv-freebsd.o --- In file included from /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/assert-r0drv-freebsd.c:34: In file included from /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/the-freebsd-kernel.h:39: /usr/src/sys/sys/bus.h:659:10: fatal error: 'device_if.h' file not found #include "device_if.h" ^ --- alloc-r0drv-freebsd.o --- In file included from /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/alloc-r0drv-freebsd.c:34: In file included from /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/the-freebsd-kernel.h:39: /usr/src/sys/sys/bus.h:659:10: fatal error: 'device_if.h' file not found #include "device_if.h" ^ --- assert-r0drv-freebsd.o --- 1 error generated. --- initterm-r0drv-freebsd.o --- In file included from /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/initterm-r0drv-freebsd.c:34: In file included from /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/the-freebsd-kernel.h:39: /usr/src/sys/sys/bus.h:659:10: fatal error: 'device_if.h' file not found #include "device_if.h" ^ --- assert-r0drv-freebsd.o --- *** [assert-r0drv-freebsd.o] Error code 1 make[3]: stopped in /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv --- initterm-r0drv-freebsd.o --- 1 error generated. --- alloc-r0drv-freebsd.o --- 1 error generated. --- initterm-r0drv-freebsd.o --- *** [initterm-r0drv-freebsd.o] Error code 1 make[3]: stopped in /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv --- memobj-r0drv-freebsd.o --- In file included from /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c:36: In file included from /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/the-freebsd-kernel.h:39: /usr/src/sys/sys/bus.h:659:10: fatal error: 'device_if.h' file not found #include "device_if.h" ^ --- alloc-r0drv-freebsd.o --- *** [alloc-r0drv-freebsd.o] Error code 1 make[3]: stopped in /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv --- memobj-r0drv-freebsd.o --- 1 error generated. *** [memobj-r0drv-freebsd.o] Error code 1 make[3]: stopped in /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv 4 errors make[3]: stopped in /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src/vboxdrv *** [all] Error code 2 make[2]: stopped in /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src 1 error make[2]: stopped in /media/da0s1/obj/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.3.36/out/freebsd.amd64/release/bin/src ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error c
Re: firefox-esr 31.2.0,1 is broken
Hello, working without any problems here too (amd64 / i386 FreeBSD 10.0 and 9.3). Maybe start with the profilemanager and create a new profile - might be an addon is broken. Regards On Tue, 21 Oct 2014, Torfinn Ingolfsen wrote: It seems like firefox-esr 31.2.0,1 is broken: tingo@kg-core1$ firefox (process:85057): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed 1413913937178 addons.manager WARN Application shipped blocklist has an unexpected namespace (http://www.mozilla.org/newlayout/xml/parsererror.xml) Bus error (core dumped) tingo@kg-core1$ portversion -v firefox* [Reading data from pkg(8) ... - 992 packages found - done] firefox-esr-31.2.0,1 = up-to-date with port tingo@kg-core1$ uname -a FreeBSD kg-core1.kg4.no 8.4-STABLE FreeBSD 8.4-STABLE #1 r266590: Fri May 23 20:23:35 CEST 2014 r...@kg-core1.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 My ports tree is updated today. ___ 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"
Any users of www/mod_auth_form
Hello @all, currently being the maintainer of www/mod_auth_form I'm asking if some1 is using it. The upstream site is gone, the developer seems unavailable too so the source code isn't under active development too. I still have the source and can over-take hosting, still there won't be any security related fixes (and there may be some, or maybe not). The port isn't currently staged, which would be no problem to fix - though the module isn't compatible with Apache 2.4.x (and upwards). So if there's no active user interest, maybe it would be better to remove the port to prevent users from installing (potentially unsafe) software used for handling authentication / protection of websites. Thanks in advance ___ 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: p5-Crypt-SSleay update
Hello,
the Makefile is a bit wrong. Changing:
BUILD_DEPENDS=
p5-LWP-Protocol-https>=6.02:${PORTSDIR}/www/p5-LWP-Protocol-https \
p5-Path-Class>=0.26:${PORTSDIR}/devel/p5-Path-Class \
p5-Try-Tiny>=0.09:${PORTSDIR}/lang/p5-Try-Tiny
RUN_DEPENDS= p5-LWP-Protocol-https>=6.02:${PORTSDIR}/www/p5-LWP-Protocol-https
\
p5-Path-Class>=0.26:${PORTSDIR}/devel/p5-Path-Class
and removing the "TEST_DEPENDS" line works.
That's of course just a temporary work-around.
Regards
On Tue, 15 Jul 2014, Ajtim wrote:
Hi!
On FreeBSD 10.0-RELEASE-p7 #0: Tue Jul 8 06:37:44 UTC 2014 root@amd64-
builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
I have a problem to install (update) p5-Crypt-SSleay:
===>>> All >> p5-Crypt-SSLeay-0.64 (2/4)
===>>> Returning to dependency check for security/p5-Crypt-SSLeay
===>>> Dependency check complete for security/p5-Crypt-SSLeay
===>>> All >> p5-Crypt-SSLeay-0.64 (3/4)
===> Cleaning for p5-Crypt-SSLeay-0.72
===> License ART20 accepted by the user
===> p5-Crypt-SSLeay-0.72 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by p5-Crypt-SSLeay-0.72 for building
===> Extracting for p5-Crypt-SSLeay-0.72
=> SHA256 Checksum OK for Crypt-SSLeay-0.72.tar.gz.
===> Patching for p5-Crypt-SSLeay-0.72
===> p5-Crypt-SSLeay-0.72 depends on package: p5-LWP-Protocol-https>=6.02 -
found
===> p5-Crypt-SSLeay-0.72 depends on package: p5-Path-Class>=0.26 - found
===> p5-Crypt-SSLeay-0.72 depends on file: /usr/local/bin/perl5.16.3 - found
===> Configuring for p5-Crypt-SSLeay-0.72
Can't locate Try/Tiny.pm in @INC (@INC contains:
/usr/local/lib/perl5/5.16/BSDPAN /usr/local/lib/perl5/site_perl/5.16/mach
/usr/local/lib/perl5/site_perl/5.16 /usr/local/lib/perl5/5.16/mach
/usr/local/lib/perl5/5.16 .) at ./Makefile.PL line 9.
BEGIN failed--compilation aborted at ./Makefile.PL line 9.
*** Error code 2
Stop.
make: stopped in /usr/ports/security/p5-Crypt-SSLeay
===>>> make build failed for security/p5-Crypt-SSLeay
===>>> Aborting update
===>>> Update for security/p5-Crypt-SSLeay failed
===>>> Aborting update
===>>> The following actions were performed:
Installation of devel/p5-Module-Build (p5-Module-Build-0.4206)
Installation of devel/p5-Path-Class (p5-Path-Class-0.33)
===>>> You can restart from the point of failure with this command line:
portmaster security/p5-Crypt-SSLeay security/p5-Net-SSLeay
Thank you.
___
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: Missing perl dependency for mail/opendkim
Hello,
Perl is pulled in here, might be through a dependency of Opendkim.
Though if you install the Perl port without the USE_PERL flag
${PREFIX}/bin/perl doesn't get symlink'ed into /usr/bin.
So when PR'ing, is it possible adding a small patch that replaces
"/usr/bin/perl" with "/usr/bin/env perl" ?
I already sent a mail to the maintainer, still yet nothing happened.
Thank you
On Thu, 13 Feb 2014, Thomas Steen Rasmussen wrote:
Hello,
mail/opendkim seems to be missing a perl depencency to make the
opendkim-genkey tool work:
$ opendkim-genkey
bash: /usr/local/sbin/opendkim-genkey: /usr/bin/perl: bad interpreter: No
such file or directory
$ file /usr/local/sbin/opendkim-genkey
/usr/local/sbin/opendkim-genkey: Perl script, ASCII text executable
As you can see it also needs to have the shebang line updated
to /usr/local/bin/perl :)
This is with opendkim-2.8.3. It works as expected after
installing lang/perl with no extra modules.
I can open a PR for this if you wish, let me know.
Best regards,
Thomas Steen Rasmussen
___
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"
___
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: Request for porting "SoftEther VPN"
Hello,
seems we both "went" into the same problem. What I did:
patching both makefiles (freebsd_32bit and freebsd_64bit) to add ${PREFIX}
and use this instead of the hardcoded /usr/bin one.
Though that doesn't seem to be required because the final "cp" process can
be triggered manually without calling "make install" at all.
Then adding "-I${PREFIX}/include -I/usr/include" and "-L${PREFIX}/lib
-L/usr/lib" - under 9.1 and 9.2 the compile run fails (when using gcc)
without this and complains about missing header files / libraries.
Additionally adding a dependency for openssl from the ports because the
final linking complains about a too old openssl version.
So for the datafiles - maybe doing it like:
${PREFIX}/lib/softether
placing all binary files and the datafiles there. Then creating small
scripts in
${PREFIX}/bin
that act as wrapper.
Finally - a small "rc" script to enable starting / stopping the entire
thing.
Kind regards
On Fri, 17 Jan 2014, Big Lebowski wrote:
Hi,
I've almost the port ready, but I am just struggling with decision wether I
want to write patches for it, or not. The software is quite badly written, and
it expects a
certain data file to exist... in the same directory as the binaries. Normally,
I'd install binaries to /usr/local/bin, but in this case that'd require the
file living
in there, what's a mess I dont want to create. The solution is to either
install it in /usr/local/softether or to patch it so that the data file could
go to lib - I am
undecided yet, as the first solution is so linux'y and second requires
rewriting piece of their code.
On Fri, Jan 17, 2014 at 9:43 AM, Tommy Scheunemann wrote:
Hello @list,
I'm about to work on getting it ported, just in case so nothing gets done
twice.
On Mon, 13 Jan 2014, Гуляев Гоша wrote:
Hi friends!
It is a very interesting VPN solution, and some days ago it going
opensource!
So maybe someone will port it to FreeBSD?
Official site: http://www.softether.org/
Instructions for build on UNIX-like systems:
http://www.softether.org/5-download/src/2.unix
___
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"
___
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"
___
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: Request for porting "SoftEther VPN"
Hello @list, I'm about to work on getting it ported, just in case so nothing gets done twice. On Mon, 13 Jan 2014, Гуляев Гоша wrote: Hi friends! It is a very interesting VPN solution, and some days ago it going opensource! So maybe someone will port it to FreeBSD? Official site: http://www.softether.org/ Instructions for build on UNIX-like systems: http://www.softether.org/5-download/src/2.unix ___ 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" ___ 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"
