Re: tar: Error opening archive: Unrecognized archive format
I have found the cause. The recently introduced field checks are not compatible with archives created by Archive::Tar. To be true, Archive::Tar violates the ustar tar header specification. I will take a look how to solve this. Cheers, mm Quoting Mathieu Arnold : Le 01/12/2016 à 10:49, Martin Matuska a écrit : could you please be more specific? Can you tell me the port names or give links to the messages? Different Mathieu, but all the errors from here: https://lists.freebsd.org/pipermail/freebsd-perl/2016-December/date.html --Mathieu Arnold -- Martin Matuska FreeBSD committer http://blog.vx.sk ___ 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: tar: Error opening archive: Unrecognized archive format
Hi Matthew, could you please be more specific? Can you tell me the port names or give links to the messages? Thanks, mm Quoting Matthew Seaman : There seem to be a lot of pkg fallout mails all with the same error: tar: Error opening archive: Unrecognized archive format This is affecting package building on head -- mostly perl modules from what I'm seeing, but that may just be sampling bias. I suspect that something has broken with the latest MFV of libarchive code in r309299 Cheers, Matthew -- Martin Matuska FreeBSD committer http://blog.vx.sk ___ 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: cpuminer mines only on one core regardless of "--threads" option
On 2014-02-18 15:24, Andrey Chernov wrote: > On 14.01.2014 17:55, Volodymyr Kostyrko wrote: >> 14.01.2014 15:01, Alexander: >>> on Freebsd 9.2 x64 on 5 different PCs I installed net-p2p/cpuminer >>> from ports and by "pkg install" - result is the same - minerd mines >>> only on one core regardless of "--threads" option. > The patch to solve this problem attached. > Patch committed. It would be cool if cpuminer was compilable with clang, too. ___ 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: Notes on upgrades after libpcre update
I agree. On the other hand, we should also mark yet unmarked ports that directly depend on pcre. The main pain comes from glib20, ports using it are directly linked against pcre but there is no information about this and we need this documented. I am releasing devel/pcre back to ports@, who wants can take care of it. On 13.12.2012 10:56, Tijl Coosemans wrote: > On 12-12-2012 10:03, Alex Dupre wrote: >> Kevin Oberman ha scritto: >>> As many of you noticed, the update of devel/pcre bumped hte version of >>> libpcre.so which is a dependency of LOTS of things. >> This was a very poor choice, we shouldn't have bumped the version. When >> there is a bump between two minor releases (8.31 -> 8.32) a red led >> should blink in port maintainer. The port should have defined: >> >> USE_AUTOTOOLS= libtool >> USE_GNOME= ltverhack >> >> to avoid bumbing the version. In fact this is the diff in configure.ac: >> >> -m4_define(libpcre_version, [1:1:0]) >> -m4_define(libpcre16_version, [0:1:0]) >> +m4_define(libpcre_version, [3:0:2]) >> +m4_define(libpcre16_version, [2:0:2]) >> >> It says that the new shared lib is compatible with the old lib (only new >> interfaces were added), since: >> >> 1 - 0 = 3 - 2 = 1 >> 1 - 0 = 2 - 2 = 0 >> >> (from the [current:revision:age] version = current - age rule) > This should be mandatory knowledge for every ports committer. > -- Martin Matuska FreeBSD committer http://blog.vx.sk ___ 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: [patch] --disable-jit for ia64 in devel/pcre
Actually, I see no reason for having JIT in options at all, as it only
provides additional functions, there is no signifficant difference in
size and the port license doesn't change. I have simply enabled it
anywhere besides sparc64 and ia64.
On 17.9.2012 17:25, Baptiste Daroussin wrote:
> On Mon, Sep 17, 2012 at 11:12:35AM +0100, Anton Shterenlikht wrote:
>> devel/pcre fails on ia64 portscluster because defaults
>> include JIT:
>>
>> http://pointyhat.freebsd.org/errorlogs/ia64-errorlogs/e.9.20120916093935/pcre-8.31.log
>>
>> This patch fixes it. I checked
>> it on my own ia64 boxes:
>>
>> Index: Makefile
>> ===
>> --- Makefile(revision 304384)
>> +++ Makefile(working copy)
>> @@ -32,7 +32,7 @@
>>
>> .include
>>
>> -.if ${PORT_OPTIONS:MJIT} && ${ARCH} != "sparc64"
>> +.if ${PORT_OPTIONS:MJIT} && ${ARCH} != "sparc64" && ${ARCH} != "ia64"
>> CONFIGURE_ARGS+= --enable-jit
>> .else
>> CONFIGURE_ARGS+= --disable-jit
>>
>
> OPTIONS_EXCLUDE_ia64= JIT
> OTPIONS_EXCLUDE_sparc64= JIT
>
> Would be cleaner imho
>
>> This patch is helpful because
>> pcre failure on ia64 portscluster blocks an
>> estimated 5658 other ports, so would
>> be good to get it committed.
>>
>> HOwever, I wonder if it's better to
>> check for $ARCH="i386" && $ARCH="amd64",
>> now that we have ppc and arm in portscluster.
>> I guess there's no JIT support for those
>> arches either.
> In that case:
> OPTIONS_DEFINE_i386= JIT
> OPTIONS_DEFINE_amd64= JIT
>
> regards,
> Bapt
--
Martin Matuska
FreeBSD committer
http://blog.vx.sk
Actually, I see no reason for having JIT in options at all, as it only
provides additional functions, there is no signifficant difference in
size and the port license doesn't change. I have simply enabled it
anywhere besides sparc64 and ia64.
On 17.9.2012 17:25, Baptiste Daroussin wrote:
--
Martin Matuska
FreeBSD committer
http://blog.vx.sk
Enigmail
___
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: Unable to build "graphics/ImageMagick" port
Please disable the HDRI option. I will disable it by default. On 19. 6. 2012 14:09, Carmel wrote: > FreeBSD 8.3-STABLE amd64 > > I am unable to successfully build and install the ImageMagick port. It > always fails with the following notation: > > make check-TESTS check-local > ESC[0;32mPASSESC[m: tests/validate-compare.sh > ESC[0;32mPASSESC[m: tests/validate-composite.sh > ESC[0;32mPASSESC[m: tests/validate-convert.sh > ESC[0;32mPASSESC[m: tests/validate-identify.sh > ESC[0;32mPASSESC[m: tests/validate-import.sh > ESC[0;32mPASSESC[m: tests/validate-montage.sh > ESC[0;32mPASSESC[m: tests/validate-pipe.sh > ESC[0;32mPASSESC[m: tests/validate-colorspace.sh > ESC[0;32mPASSESC[m: tests/validate-stream.sh > ESC[0;32mPASSESC[m: tests/validate-formats-in-memory.sh > ESC[0;32mPASSESC[m: tests/validate-formats-on-disk.sh > ESC[0;32mPASSESC[m: Magick++/tests/exceptions.sh > ESC[0;32mPASSESC[m: Magick++/tests/appendImages.sh > ESC[0;32mPASSESC[m: Magick++/tests/attributes.sh > ESC[0;32mPASSESC[m: Magick++/tests/averageImages.sh > ESC[0;32mPASSESC[m: Magick++/tests/coalesceImages.sh > ESC[0;32mPASSESC[m: Magick++/tests/coderInfo.sh > ESC[0;32mPASSESC[m: Magick++/tests/colorHistogram.sh > ESC[0;32mPASSESC[m: Magick++/tests/color.sh > ESC[0;32mPASSESC[m: Magick++/tests/montageImages.sh > ESC[0;32mPASSESC[m: Magick++/tests/morphImages.sh > ESC[0;32mPASSESC[m: Magick++/tests/readWriteBlob.sh > ESC[0;32mPASSESC[m: Magick++/tests/readWriteImages.sh > ESC[0;31mFAILESC[m: Magick++/demo/analyze.sh > ESC[0;32mPASSESC[m: Magick++/demo/button.sh > ESC[0;32mPASSESC[m: Magick++/demo/demo.sh > ESC[0;32mPASSESC[m: Magick++/demo/flip.sh > ESC[0;32mPASSESC[m: Magick++/demo/gravity.sh > ESC[0;32mPASSESC[m: Magick++/demo/piddle.sh > ESC[0;32mPASSESC[m: Magick++/demo/shapes.sh > ESC[0;32mPASSESC[m: Magick++/demo/zoom_bessel.sh > ESC[0;32mPASSESC[m: Magick++/demo/zoom_blackman.sh > ESC[0;32mPASSESC[m: Magick++/demo/zoom_box.sh > ESC[0;32mPASSESC[m: Magick++/demo/zoom_catrom.sh > ESC[0;32mPASSESC[m: Magick++/demo/zoom_cubic.sh > ESC[0;32mPASSESC[m: Magick++/demo/zoom_gaussian.sh > ESC[0;32mPASSESC[m: Magick++/demo/zoom_hamming.sh > ESC[0;32mPASSESC[m: Magick++/demo/zoom_hanning.sh > ESC[0;32mPASSESC[m: Magick++/demo/zoom_hermite.sh > ESC[0;32mPASSESC[m: Magick++/demo/zoom_lanczos.sh > ESC[0;32mPASSESC[m: Magick++/demo/zoom_mitchell.sh > ESC[0;32mPASSESC[m: Magick++/demo/zoom_point.sh > ESC[0;32mPASSESC[m: Magick++/demo/zoom_quadratic.sh > ESC[0;32mPASSESC[m: Magick++/demo/zoom_sample.sh > ESC[0;32mPASSESC[m: Magick++/demo/zoom_scale.sh > ESC[0;32mPASSESC[m: Magick++/demo/zoom_sinc.sh > ESC[0;32mPASSESC[m: Magick++/demo/zoom_triangle.sh > ESC[0;32mPASSESC[m: wand/drawtest.sh > ESC[0;32mPASSESC[m: wand/wandtest.sh > ESC[0;31m===ESC[m > ESC[0;31m1 of 49 tests failedESC[m > ESC[0;31mSee ./test-suite.logESC[m > ESC[0;31mPlease report to http://www.imagemagick.orgESC[m > ESC[0;31m===ESC[m > *** Error code 1 > > Stop in /usr/ports/graphics/ImageMagick/work/ImageMagick-6.7.7-7. > *** Error code 1 > > I can supply the entire build log if necessary. > -- Martin Matuska FreeBSD committer http://blog.vx.sk ___ 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: make failed for graphics/ImageMagick
Thank you, I have fixed the /bin/bash in tests/validate-colorspace.sh On 16.5.2012 19:59, Leslie Jensen wrote: > > > Will you Please look into this? > > Thank you > > > > > /usr/bin/make check-TESTS check-local > PASS: tests/validate-compare.sh > PASS: tests/validate-composite.sh > PASS: tests/validate-convert.sh > PASS: tests/validate-identify.sh > PASS: tests/validate-import.sh > PASS: tests/validate-montage.sh > PASS: tests/validate-pipe.sh > FAIL: tests/validate-colorspace.sh > PASS: tests/validate-stream.sh > PASS: tests/validate-formats-in-memory.sh > PASS: tests/validate-formats-on-disk.sh > PASS: Magick++/tests/exceptions.sh > PASS: Magick++/tests/appendImages.sh > PASS: Magick++/tests/attributes.sh > PASS: Magick++/tests/averageImages.sh > PASS: Magick++/tests/coalesceImages.sh > PASS: Magick++/tests/coderInfo.sh > PASS: Magick++/tests/colorHistogram.sh > PASS: Magick++/tests/color.sh > PASS: Magick++/tests/montageImages.sh > PASS: Magick++/tests/morphImages.sh > PASS: Magick++/tests/readWriteBlob.sh > PASS: Magick++/tests/readWriteImages.sh > PASS: Magick++/demo/analyze.sh > PASS: Magick++/demo/button.sh > PASS: Magick++/demo/demo.sh > PASS: Magick++/demo/flip.sh > PASS: Magick++/demo/gravity.sh > PASS: Magick++/demo/piddle.sh > PASS: Magick++/demo/shapes.sh > PASS: Magick++/demo/zoom_bessel.sh > PASS: Magick++/demo/zoom_blackman.sh > PASS: Magick++/demo/zoom_box.sh > PASS: Magick++/demo/zoom_catrom.sh > PASS: Magick++/demo/zoom_cubic.sh > PASS: Magick++/demo/zoom_gaussian.sh > PASS: Magick++/demo/zoom_hamming.sh > PASS: Magick++/demo/zoom_hanning.sh > PASS: Magick++/demo/zoom_hermite.sh > PASS: Magick++/demo/zoom_lanczos.sh > PASS: Magick++/demo/zoom_mitchell.sh > PASS: Magick++/demo/zoom_point.sh > PASS: Magick++/demo/zoom_quadratic.sh > PASS: Magick++/demo/zoom_sample.sh > PASS: Magick++/demo/zoom_scale.sh > PASS: Magick++/demo/zoom_sinc.sh > PASS: Magick++/demo/zoom_triangle.sh > PASS: wand/drawtest.sh > PASS: wand/wandtest.sh > === > 1 of 49 tests failed > See ./test-suite.log > Please report to http://www.imagemagick.org > === > *** Error code 1 > > Stop in /usr/ports/graphics/ImageMagick/work/ImageMagick-6.7.6-9. > *** Error code 1 > > Stop in /usr/ports/graphics/ImageMagick/work/ImageMagick-6.7.6-9. > *** Error code 1 > > Stop in /usr/ports/graphics/ImageMagick/work/ImageMagick-6.7.6-9. > *** Error code 1 > > Stop in /usr/ports/graphics/ImageMagick/work/ImageMagick-6.7.6-9. > *** Error code 1 > > > > -- Martin Matuska FreeBSD committer http://blog.vx.sk ___ 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: devel/pcre
Thanks. On 14.2.2012 23:17, Doug Barton wrote: > On 02/14/2012 11:23, Patrick Lamaiziere wrote: >> Hello, >> >> Can someone add an entry in ports/UPDATING for the latest update of >> devel/pcre (8.30) ? >> >> All ports that depend on it have to be rebuilt (you have to rebuild >> all the box...). > I added a note that suggests using the -w option for portmaster which > preserves the shared libs until a better solution is found. I guessed on > the knob for portupgrade, if someone who knows better wants to correct > it that would be welcome. :) > > > Doug > -- Martin Matuska FreeBSD committer http://blog.vx.sk ___ 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: Stop in /usr/ports/multimedia/x264
Say, did you look at the port recently? :-) I have added bash as a build dependency and use it for the configure script. There are two ways I can solve this in general: 1.) add bash as a build dependency and use it for configure (I have chosen this for now, already committed) 2.) patch configure and remove/replace constructs unsupported by /bin/sh (e.g. "==" or [[ ]]) Cheers, mm On 22.12.2011 12:03, per...@pluto.rain.com wrote: > Kevin Oberman wrote: > >> I see the following errors during the configure stage: >> ===> Configuring for x264-0.119.2113 >> [[: not found > That sure looks as if the configure script needs to be run with bash. > > files/patch-configure does this: > > -#!/bin/bash > +#!/bin/sh > > which presumes that the script does not actually need bash extensions. > However, since it does seem to need those extensions, that part of the > patch should be > > -#!/bin/bash > +#!/usr/local/bin/bash > > and bash needs to be added as a build dependency. (Alternatively, the > configure script could be patched to not use the [[ bash builtin.) > > Maintainer already in Cc: list. -- Martin Matuska FreeBSD committer http://blog.vx.sk ___ 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/lighttpd failes to build
d identifier before numeric > constant > *** Error code 1 > > Stop in /usr/ports/www/lighttpd/work/lighttpd-1.4.29/src. > *** Error code 1 > > Stop in /usr/ports/www/lighttpd/work/lighttpd-1.4.29/src. > *** Error code 1 > > Stop in /usr/ports/www/lighttpd/work/lighttpd-1.4.29. > *** Error code 1 > > Stop in /usr/ports/www/lighttpd/work/lighttpd-1.4.29. > *** Error code 1 > > Stop in /usr/ports/www/lighttpd. > *** Error code 1 > > Stop in /usr/ports/www/lighttpd. > > real0m19.999s > user0m11.980s > sys 0m7.193s > [root@abc /usr/ports/www/lighttpd]# > > When I asked about this on freenode, I was instructed to e-mail ports > and the maintainer, so I am. Build with libev fixed together with update to 1.4.30. If you are using SSL, please make sure to set the following in your configuration file to prevent the BEAST attack: ssl.disable-client-renegotiation = "enable" ssl.honor-cipher-order = "enable" ssl.cipher-list = "ECDHE-RSA-AES256-SHA384:AES256-SHA256:RC4-SHA:RC4:HIGH:!MD5:!aNULL:!EDH:!AESGCM" -- Martin Matuska FreeBSD committer http://blog.vx.sk ___ 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: binutils-2.22: ld and --copy-dt-needed-entries
On 6.12.2011 17:48, Andriy Gapon wrote: > Just for your information. > It seems that ld from binutils-2.22 by default has --no-copy-dt-needed-entries > behavior, and so explicit --copy-dt-needed-entries is now needed where the > previous default behavior is relied upon. > > A short excerpt from the man page for your convenience: > >> This option also has an effect on the resolution of symbols in >> dynamic libraries. With --copy-dt-needed-entries dynamic libraries >> mentioned on the command line will be recursively searched, >> following their DT_NEEDED tags to other libraries, in order to >> resolve symbols required by the output binary. With the default >> setting however the searching of dynamic libraries that follow it >> will stop with the dynamic library itself. No DT_NEEDED links will >> be traversed to resolve symbols. What do we do with this? We can go back, patch to behave as before or to continue. Are there any serious complaints? -- Martin Matuska FreeBSD committer http://blog.vx.sk ___ 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: [CFT] mplayer / mencoder port update
I have just updated x264 to 0.110.1804 We use now original x264 versioning scheme for PORTVERSION. Dňa 17.11.2010 21:44, Thomas Zander wrote / napísal(a): > Hi, > > I have prepared a new tarball, for download at the usual location: > > http://www.rrr.de/~riggs/mplayer/m20101117.tar.bz2 > > Most notable changes: > - remove volume-per-channel patch, instead pkg-message explains the > issue and the solutions > - remove RUN_DEPENDS for live media > > @Martin: Do you have plans for an x264 update? I'd like to commit > mplayer after we have a suitable x264 port. > > Have fun > Riggs ___ 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: ImageMagick 6.5.4.10
The pre-8 FreeBSD systems do not know carg(), my tinderbox didnt discover this. It is now fixed with a patch by replacing carg(x) with atan2(cimag(x),creal(x)) ajtiM wrote / napísal(a): > Update to 6.5.4.10 on FreeBSD 7.2 > > magick/.libs/libMagickCore.so: undefined reference to `carg' > *** Error code 1 > magick/.libs/libMagickCore.so: undefined reference to `carg' > *** Error code 1 > 2 errors > *** Error code 2 > 1 error > *** Error code 1 > > Stop in /usr/ports/graphics/ImageMagick. > *** Error code 1 > > Stop in /usr/ports/graphics/ImageMagick. > > ===>>> make failed for graphics/ImageMagick > ===>>> Aborting update > > ___ 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"
Call for testing: sysutils/fusefs-kmod
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I would like to recruit more testers for prepared sysutils/fusefs-kmod update: PR: ports/114629 DIFF: http://mm.vx.sk/diffs/fusefs-kmod-0.3.9.p1.diff Thanks. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: GnuPT 2.7 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGrwzup2uLA0JhsNERAhSCAJ4nznqrdPjFPbZAuCf2LJUo6xqBdgCfWeXZ mRvT0H1LYpjFyf754dO/3NQ= =c6cw -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Testing and suggestions for new bsd.tcl.mk
Hi everybody, I am working on a new bsd.tcl.mk and I would like to ask for feedback, suggestions and bug reports. There is a new way how threads are handled, a new port called tcl-tk-wrapper may be used and the tcl and tk ports are already prepared for this change. The new file should be fully backwards compatible. What the different parts do is documented in comments. The current version can be viewed under: http://www.matuska.org/martin/cgi/viewvc.cgi/ports/Mk/bsd.tcl.mk?revision=HEAD&view=markup Patch against current ports CVS: http://www.matuska.org/martin/cgi/viewvc.cgi/ports/Mk/bsd.tcl.mk?r1=45&r2=HEAD&view=patch ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Why so many tcl's and tk's
Stephen Montgomery-Smith wrote / napísal(a): > Are the different versions of tcl and tk really not backwards > compatible with earlier versions? I can guess that there have been > heated conversations about this, but a my look at the mailing list > archives didn't give me anything. But it sure would be much nicer if > there was just a tcl and a tcl-devel port or something like that. Are > there really applications that need tcl83 but break on tcl84? > > Stephen > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "[EMAIL PROTECTED]" The various Tcl and Tk versions do have incompatible changes in the interfaces and in the command syntax. It is very much like Berkeley DB - you have several versions, too. You have to rewrite your program to support more (or newer) Tcl versions. The idea on the current implementation in the FreeBSD ports tree is to stay compatible with older tcl scripts and libraries, too. But the structure of the supporting bsd.tcl.mk is very old and does not suit the needs of current applications anymore. Another recent issue is the handling of threaded and non-threaded versions of Tcl 8.4 and 8.5. The current implementation ist just a workaround, so that applications that explicitly require a threaded Tcl build can use it. A threaded Tcl build is 100% compatible to a non-threaded Tcl. As far as I know, threaded Tcl 8.4 builds and runs on all common FreeBSD architectures. A very clean and good solution would to have a threaded Tcl only. I will test this against all libraries from the FreeBSD ports that extend Tcl to check if they work with the threaded version correctly. I am working with miwi@ on a new implementation of bsd.tcl.mk A first working version can be viewed under: http://www.matuska.org/martin/cgi/viewvc.cgi/ports/Mk/bsd.tcl.mk The final version will probably be different - the threading part might be removed completely in favour of using threaded tcl by default. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Impending update to devel/gettext
Thanks, found no other problems. Ade Lovett schrieb: > Thanks for the input. I have cleaned up the Makefile to make it as > portlint-happy as it's going to get, addressing the INSTALLS_SHLIB -> > USE_LDCONFIG change, and also removed the removal of share/locale/eo, > since that is now present in the /etc/mtree/BSD.local.dist (it wasn't > at the initial time of writing the patch). > > New version can be found here: > > http://www.lovett.com/ade/freebsd/gettext-3.diff > > MD5 (gettext-3.diff) = 58446c5fbaaf3f63c8aa65526bc71210 > > -aDe > > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Proposal: Automatic registering of UID and GID for ports
Inspired by the FreeBSD project ideas ( http://www.freebsd.org/projects/ideas/#p-ports-uid ) I have submitted a working proposal ( ports/108514) for automatic registering of UID and GID entries for ports that require this by adding ADDGROUP and ADDUSER knobs. It integrates scripts into packages. The problem is, that the current package system supports up to two install and two deinstall (PRE- and POST-) scripts per package. Without changes to pkg_install one of these scripts has to be used for this purpose. A discussion of this matter would be welcome. URL of the PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/108514 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Impending update to devel/gettext
On Jan 30, 2007, at 23:27 , Ade Lovett wrote: > In the true spirit of "oh crap, let's fix this thing properly", I now > present to you: > > http://www.lovett.com/ade/freebsd/gettext-2.diff > > MD5 (gettext-2.diff) = 97d80b61281f6bc5aa88362a970b50a3 > > This significantly reworks the original 0.16.1 update, removing the > (IMO) relatively useless OPTIONS, and makes the port NOPORTDOCS-safe > as requested in ports/106998. > > The previous diff has been removed -- if you've already downloaded > it, my apologies, please use this one instead. > > Thanks, > -aDe The new gettext port seems to be working. Compiles and installs correctly. a) To make it little more portlint-happy: Is the deprecated INSTALLS_SHLIB knob necessary? USE_LDCONFIG= yes b) My tinderbox reports this issue at the end: -- TINDERBOX LOG BEGINS -- ===> Building package for gettext-0.16.1 Creating package /tmp/packages/All/gettext-0.16.1.tbz Registering depends: libiconv-1.9.2_2. Creating bzip'd tar ball in '/tmp/packages/All/gettext-0.16.1.tbz' Deleting gettext-0.16.1 === Checking filesystem state list of files present before this port was installed but missing after it was deinstalled) ./usr/local/share/locale/eo missing ./usr/local/share/locale/eo/LC_MESSAGES missing Deleting libtool-1.5.22_3 Deleting libiconv-1.9.2_2 === Checking filesystem state after all packages deleted list of files present on clean system but missing after everything was deinstalled) ./usr/local/share/locale/eo missing ./usr/local/share/locale/eo/LC_MESSAGES missing build of /usr/ports/devel/gettext ended at Wed Jan 31 14:50:58 UTC 2007 -- TINDERBOX LOG ENDS -- This eo locale (Esperanto) is not in the charset.alias list. I am asking myself, why tinderbox reports the directory was present on the system prior to installing gettext-0.16.1 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
