Re: [ImageMagick] build problem
On Thu 2008-12-11 05:27:40 UTC-0800, David Wolfskill (da...@catwhisker.org) wrote: > On Thu, Dec 11, 2008 at 11:48:07AM +0100, regisr wrote: > > When building ImageMagick-6.4.7-5 on FreeBSD 6.4 I have a build error: > > > > /usr/obj/home/ports/graphics/ImageMagick/work/ImageMagick-6.4.7-5/tests/.libs/co > > nstitute -storagetype > > double /usr/obj/home/ports/graphics/ImageMagick/work/Image > > Magick-6.4.7-5/tests/input_truecolor.miff cmy Constitute check failed: > > 6615/0.0587497/0.843137 FAIL: tests/constitute_double_cmy.sh > > For what it's worth, I did not encounter this. Me neither. > Running on: > > > FreeBSD g1-35.catwhisker.org 6.4-STABLE FreeBSD 6.4-STABLE #659: Thu > Dec 11 05:01:52 PST 2008 > r...@g1-35.catwhisker.org:/common/S1/obj/usr/src/sys/CANARY i386 $ uname -a FreeBSD blizzard.phoenix 6.4-RELEASE FreeBSD 6.4-RELEASE #0: Wed Nov 26 11:43:51 UTC 2008 r...@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 $ pwd /usr/ports/graphics/ImageMagick $ cd /usr/ports/graphics/ImageMagick $ make showconfig ===> The following configuration options are available for ImageMagick-nox11-6.4.7.5: X11=off "X11 support" IMAGEMAGICK_TESTS=on "Run bundled self-tests after build" IMAGEMAGICK_OPENMP=off "OpenMP for SMP (needs threads)" IMAGEMAGICK_PERL=off "Perl support" IMAGEMAGICK_MODULES=off "Modules support (broken)" IMAGEMAGICK_BZLIB=on "Bzlib support" IMAGEMAGICK_16BIT_PIXEL=on "16bit pixel support" IMAGEMAGICK_DJVU=off "DJVU format support (needs threads)" IMAGEMAGICK_LCMS=off "LCMS support" IMAGEMAGICK_HDRI=off "High Dynamic Range Images (HDRI)" IMAGEMAGICK_TTF=off "Freetype support" IMAGEMAGICK_FONTCONFIG=off "Fontconfig support" IMAGEMAGICK_JPEG=on "JPG format support" IMAGEMAGICK_OPENEXR=off "OpenEXR support (needs threads)" IMAGEMAGICK_PNG=on "PNG format support" IMAGEMAGICK_TIFF=on "TIFF format support" IMAGEMAGICK_FPX=off "FPX format support" IMAGEMAGICK_JBIG=off "JBIG format support" IMAGEMAGICK_JPEG2000=off "JPEG2000 format support" IMAGEMAGICK_DOT=off "GraphViz dot graphs support" IMAGEMAGICK_WMF=off "WMF format support" IMAGEMAGICK_SVG=off "SVG format support" IMAGEMAGICK_PDF=off "PDF format support" IMAGEMAGICK_GSLIB=off "libgs (Postscript SHLIB) support" ===> Use 'make config' to modify these settings ___ 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: [PROPOSAL] Ports using SCM repositories as source instead of distfiles
* Ashish Shukla आशीष शुक्ल (wahjava...@gmail.com) wrote:
> Yes, that is why I mentioned having a variable which enables this
> behaviour, by default it is disabled. I mean ports which are okay
> with providing static plists are fine, but ports which aren't
> predictable with what files are going to installed can go with this
> dynamic plist support, where ports infrastructure will only help in
> generating a plist from an already setup directory tree
> (/var/tmp/${portname}), now it is maintainer's responsibility to make
> sure that all files will be installed in /var/tmp/${portname} which
> {s,}he can do by either using 'make install DESTDIR=/var/tmp/${portname}'
> or something similar if supported by port's upstream or {s,}he has to
> add installation commands in ports Makefile rather than going with
> upstream's way of installing things.
I really don't see any point in supporting this only in individual
ports. If you can do something, you expect (and should be able)
to do it with any and all ports.
> > See
> > http://lists.freebsd.org/pipermail/freebsd-ports/2006-August/034745.html
> > those are some real examples of complexity and resulting confusion,
> > from first variant of DESTDIR support in ports. Now, when we have
> > one DESTDIR implementation, adding another will likely make some heads
> > explode, just think of variable naming.
>
> The DESTDIR issue in above link refers to the DESTDIR support[1] present in
> FreeBSD Ports system, and the one which I'm talking about has nothing to
> do with that.
Yes, I just meant that that'll bring too much confusion.
> > I'll remind that what we are talking about is automatic plist generation,
> > and I think that this can be done without any hacks like installing a
> > port into intermediate directory before real installation just by
> > logging all writes to the filesystem.
>
> Yes that intermediate directory is what DESTDIR is. And if you're
> capable of logging all writes in the DESTDIR, then its cool, but
No. If there's DESTDIR, you don't need to log writes to it, as you
can just use `find` to see what's there after installation as in
quote below. The idea is that if we log all writes to the fulesystem
during port installation, we don't need intermediate directory at
all.
> remember you're also talking about installing port in an intermediate
> directory. After the port gets installed in intermediate directory, the
> plist can be generated with your filesystem writes logger component or a
> well tested version of following simply command line:
>
> % find /var/tmp/${PORTNAME} -type f |sed -e \
> "s[/var/tmp/${PORTNAME}${PREFIX}/[[g" > plist.tmp
--
Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D
amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru
___
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: Proposal: mechanism for local patches
* N.J. Mann (n...@njm.me.uk) wrote: > > I suppose that check was done to help to detect patching failures, so it > > may be removed. > > I've just been trying out your patch and I think from an organisational > point of view it is very good. What I mean by this is that with the > patch I am now able to keep my local patches completely separate from > the official, FreeBSD patches. No more backing up the whole of > /usr/ports just in case I have a private patch in there somewhere. Now > I just need to backup /usr/ports.localpatchdir (which is what I called > the directory LOCAPATCHDIR points to). Nice to hear that it's useful :) > However, please consider putting back in the test for *.orig and *~ > files. That way one can be actively be hacking on a patch without > having to keep deleting editor backup files, which you may not wish to > delete anyway, before attempting another build. In my case I see no > need to skip *.rej and *,v files, but others may have a need for them. Done, patch updated. Btw, as someone who uses it, what do you think about the fact that local patches are applied after FreeBSD ones? (see my doubts up the thread). > I hope some form of your patch gets into the tree once 7.1 ships. Will try to make it in after the release. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru ___ 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: [PROPOSAL] Ports using SCM repositories as source instead of distfiles
* Jeremy Messenger (me...@cox.net) wrote: >> So if I understand correctly, you're proposing to only use dynamic >> plist generation for the ports that support it without modification, >> i.e. autotools-based? >> >> My opinion is that we should support the feature for all ports, or don't >> support it at all. Only getting rid of ~5k pkg-plists is not a huge >> accomplishment considering the mess it causes and I doubt it's worth >> the work on adding the feature to port.mk and then rebuilding and >> testing all affected ports. Being able to forget about pkg-plists >> once and forever however would be a huge accomplishment and if that's >> possible it should be done sooner or later. > > I object on get rid of pkg-plist. I depend on pkg-plist too much. I think > it's important for us to keep on track where the files/directories are. It's useful for me too sometimes, but it's already not 100% reliable, as some ports still generate it dynamically, some use PLIST_FILES, some use PLIST_SUB so it's not apparent under which path and/or name the file mentioned in plist is actually installed. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru ___ 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: portupgrade and freebsd-update: A better way?
On Thu, 11 Dec 2008, Garrett Cooper wrote: On Thu, Dec 11, 2008 at 7:13 PM, Peter Beckman wrote: You get a few production servers with 200+ ports installed, and upgrading could take several days and lots of headaches and a lot of babysitting. Is there a better way? Does portsnap or portmanager or portupgrade keep track? What have I missed? 7.x and 6.2 aren't ABI compatible, so unfortunately no, you have to babysit a bit. Is there some sort of chart that shows binary application compatibility between FreeBSD versions? That'd be handy. It took me a bit to find out that GENERIC now included SMP, but several google searches have led me to no good data. I found this: http://people.freebsd.org/~deischen/symver/library_versioning.txt But `cat /usr/src/lib/libc/Versions.def` got me no real data. I did also find this: http://wiki.freebsd.org/VendorInformation "No compatibility for API and ABI is guaranteed from one to the next major release, though an effort is made to make the upgrade process and source code changes as untroubled as possible." Is it safe to assume ABI compatibility between minor releases (6.1 -> 6.2) and must recompile everything between major releases (6.3 -> 7.0)? Beckman --- Peter Beckman Internet Guy beck...@angryox.com http://www.angryox.com/ --- ___ 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"
SDS Newsletter
Your email client cannot read this email. To view it online, please go here: http://www.newsletterserve.com/display.php?M=237786&C=b4213c1f912b09c8bff11f75dffc0df3&S=1080&L=200&N=1003 To stop receiving these emails:http://www.newsletterserve.com/unsubscribe.php?M=237786&C=b4213c1f912b09c8bff11f75dffc0df3&L=200&N=1080 ___ 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: portupgrade and freebsd-update: A better way?
On Thu, 11 Dec 2008, Garrett Cooper wrote: On Thu, Dec 11, 2008 at 7:13 PM, Peter Beckman wrote: You get a few production servers with 200+ ports installed, and upgrading could take several days and lots of headaches and a lot of babysitting. Is there a better way? Does portsnap or portmanager or portupgrade keep track? What have I missed? 7.x and 6.2 aren't ABI compatible, so unfortunately no, you have to babysit a bit. Is there some sort of chart that shows binary application compatibility between FreeBSD versions? That'd be handy. It took me a bit to find out that GENERIC now included SMP, but several google searches have led me to no good data. I found this: http://people.freebsd.org/~deischen/symver/library_versioning.txt But `cat /usr/src/lib/libc/Versions.def` got me no real data. I did also find this: http://wiki.freebsd.org/VendorInformation "No compatibility for API and ABI is guaranteed from one to the next major release, though an effort is made to make the upgrade process and source code changes as untroubled as possible." Is it safe to assume ABI compatibility between minor releases (6.1 -> 6.2) and must recompile everything between major releases (6.3 -> 7.0)? Beckman --- Peter Beckman Internet Guy beck...@angryox.com http://www.angryox.com/ --- ___ 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: [PROPOSAL] Ports using SCM repositories as source instead of distfiles
Dmitry Marakasov writes: [...] > No. If there's DESTDIR, you don't need to log writes to it, as you > can just use `find` to see what's there after installation as in > quote below. The idea is that if we log all writes to the fulesystem > during port installation, we don't need intermediate directory at > all. Okay, so if we go with your approach, then can you tell me how do you plan to go about logging writes to filesystem with your .so which you're planning to preload as you mentioned in one of your mails in this thread ? Thanks -- Ashish Shukla pgpW8euXD6Ke4.pgp Description: PGP signature pgp4RIYNwuC00.pgp Description: PGP signature
Problems with php5 upgrade
I recently portupgraded a box and now I'm having problems with two ports that fail to upgrade; devel/php5-spl and security/php5-filter. Both of them fail because they can't find the pcre header file. According to UPDATING, pcre is now distributed as part of the core install of php5 I've deleted php5-pcre and run pkgdb -F but I'm still having problems with those two ports. I followed the instructions in UPDATING for the pecl has and json ports, and those worked fine. For some reason these two ports can't find that header file. Will deinstalling and reinstalling php6 fix the problem? Is there another way to fix it? -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** Check the headers before clicking on Reply. ___ 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: Problems with php5 upgrade
Paul Schmehl wrote: Will deinstalling and reinstalling php6 fix the problem? Yes. -- Alex Dupre ___ 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: Problems with php5 upgrade
--On Friday, December 12, 2008 15:04:52 -0600 Alex Dupre wrote: Paul Schmehl wrote: Will deinstalling and reinstalling php6 fix the problem? Yes. Thanks, Alex. That fixed the problem. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** Check the headers before clicking on Reply. ___ 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"
Passive Income - Up to $37,500.00
Passive Income - Up to $37,500.00 This is not a joke! Open this site now and look how easy you can get cash only within 5 hours. If you not trust, do not enter to our site. But once you open our site, you'll know how easy to make home income. Only within 5 hours. 5 HOURS TO BE RICH - [1]ENTER NOW!!! References 1. http://5ivehourspayment.com/ ___ 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: portupgrade and freebsd-update: A better way?
Peter Beckman writes: > Is it safe to assume ABI compatibility between minor releases (6.1 -> 6.2) > and must recompile everything between major releases (6.3 -> 7.0)? That's the intended approach, but read the release notes and updating instructions rather than assuming anything. ___ 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"
