Bacula wx-console's wx version
Hi! Does anyone see a reason why Bacula's wx-console should use WX 2.4? Every time I start upgrading bacula-client, I just set USE_WX=2.8 in bacula-server's Makefile and it builds and works perfectly. I've also tried compiling it with 2.6 and there wasn't any problem with it neither. So what do you think - is the 2.4 really necessary there or would the WX-defaults suffice? -- Silver -- View this message in context: http://www.nabble.com/Bacula-wx-console%27s-wx-version-tf4625066.html#a13208310 Sent from the freebsd-ports mailing list archive at Nabble.com. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports using gcc 4.2 under FreeBSD 6.2-RELEASE
Naram Qashat wrote: I was wondering if it would be possible to test if a port would work properly with GCC 4.2 would help test for FreeBSD 7-CURRENT if I use the lang/gcc42 port while under 6.2-RELEASE. I want to test and see what does and doesn't compile, maybe to see if I could help the ports tree for 7-CURRENT before I try to move to 7-CURRENT myself. You don't need to test to see whether or not they compile, hundreds of them that do not compile are already marked BROKEN. What is needed is someone to fix them, and that you can help with using the gcc42 port. Kris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
ImageMagick - portupgrade failure -amd64 openexr issues
ImageMagick amd64 -- freebsd 6.1 === 1 of 696 tests failed Please report to http://www.imagemagick.org === *** Error code 1 Stop in /usr/ports/graphics/ImageMagick/work/ImageMagick-6.3.5. *** Error code 1 Stop in /usr/ports/graphics/ImageMagick/work/ImageMagick-6.3.5. *** Error code 1 Stop in /usr/ports/graphics/ImageMagick. *** Error code 1 Stop in /usr/ports/graphics/ImageMagick. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.77670.120 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=ImageMagick-6.3.5.10 UPGRADE_PORT_VER=6.3.5.10 make ** Fix the problem and try again. Below is an extract from the stdout: (to go directly to the failed test search for ## You will also see repeated reports such as: coderInfo: unable to close module `YCBCR': Invalid shared object handle 0x800565c00. Extracts BEGIN:--- PASS: tests/rwfile_YUV_truecolor_70x46.sh exceptions: unable to close module `xc': Invalid shared object handle 0x80052c000. PASS: Magick++/tests/exceptions.sh appendImages: unable to close module `MIFF': Invalid shared object handle 0x80052d000. PASS: Magick++/tests/appendImages.sh attributes: unable to close module `GIF': Invalid shared object handle 0x80053b200. attributes: unable to close module `xc': Invalid shared object handle 0x80053b000. PASS: Magick++/tests/attributes.sh averageImages: unable to close module `MIFF': Invalid shared object handle 0x80052d000. PASS: Magick++/tests/averageImages.sh coalesceImages: unable to close module `MIFF': Invalid shared object handle 0x80052c000. PASS: Magick++/tests/coalesceImages.sh coderInfo: unable to close module `YCBCR': Invalid shared object handle 0x800565c00. coderInfo: unable to close module `XWD': Invalid shared object handle 0x800565a00. coderInfo: unable to close module `XPM': Invalid shared object handle 0x800565800. coderInfo: unable to close module `XCF': Invalid shared object handle 0x800565600. coderInfo: unable to close module `XC': Invalid shared object handle 0x800565400. coderInfo: unable to close module `XBM': Invalid shared object handle 0x800565200. coderInfo: unable to close module `X': Invalid shared object handle 0x800565000. coderInfo: unable to close module `WPG': Invalid shared object handle 0x80055fe00. coderInfo: unable to close module `WMF': Invalid shared object handle 0x80055fa00. coderInfo: unable to close module `WBMP': Invalid shared object handle 0x80055f800. coderInfo: unable to close module `VIFF': Invalid shared object handle 0x80055f600. coderInfo: unable to close module `VID': Invalid shared object handle 0x80055f400. coderInfo: unable to close module `VICAR': Invalid shared object handle 0x80055f200. coderInfo: unable to close module `UYVY': Invalid shared object handle 0x80055f000. coderInfo: unable to close module `URL': Invalid shared object handle 0x80055ce00. coderInfo: unable to close module `UIL': Invalid shared object handle 0x80055cc00. coderInfo: unable to close module `TXT': Invalid shared object handle 0x80055ca00. coderInfo: unable to close module `TTF': Invalid shared object handle 0x80055c800. coderInfo: unable to close module `TIM': Invalid shared object handle 0x80055c600. coderInfo: unable to close module `TILE': Invalid shared object handle 0x80055c400. coderInfo: unable to close module `TIFF': Invalid shared object handle 0x80055c200. coderInfo: unable to close module `THUMBNAIL': Invalid shared object handle 0x80055c000. coderInfo: unable to close module `TGA': Invalid shared object handle 0x800558e00. coderInfo: unable to close module `SVG': Invalid shared object handle 0x800557000. coderInfo: unable to close module `SUN': Invalid shared object handle 0x800553e00. coderInfo: unable to close module `STEGANO': Invalid shared object handle 0x800553c00. coderInfo: unable to close module `SGI': Invalid shared object handle 0x800553a00. coderInfo: unable to close module `SFW': Invalid shared object handle 0x800553800. coderInfo: unable to close module `SCT': Invalid shared object handle 0x800553600. coderInfo: unable to close module `SCR': Invalid shared object handle 0x800553400. coderInfo: unable to close module `RLE': Invalid shared object handle 0x800553200. coderInfo: unable to close module `RLA': Invalid shared object handle 0x800553000. coderInfo: unable to close module `RGB': Invalid shared object handle 0x80054fe00. coderInfo: unable to close module `RAW': Invalid shared object handle 0x80054fc00. coderInfo: unable to close module `PWP': Invalid shared object handle 0x80054fa00. coderInfo: unable to close module `PSD': Invalid shared object handle 0x80054f800. coderInfo: unable to close module `PS3': Invalid shared object handle 0x80054f600. coderInfo: unable to close module `PS2': Invalid shared object handle 0x80054f400. coderInfo: unable to close module `PS': Invalid shared object handle 0x80054f200. coderInfo:
Re: ImageMagick - portupgrade failure -amd64 openexr issues
On Monday 15 October 2007 02:27:38 David Southwell wrote: ImageMagick amd64 -- freebsd 6.1 === 1 of 696 tests failed Please report to http://www.imagemagick.org === *** Error code 1 Stop in /usr/ports/graphics/ImageMagick/work/ImageMagick-6.3.5. *** Error code 1 Stop in /usr/ports/graphics/ImageMagick/work/ImageMagick-6.3.5. *** Error code 1 Stop in /usr/ports/graphics/ImageMagick. *** Error code 1 Stop in /usr/ports/graphics/ImageMagick. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.77670.120 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=ImageMagick-6.3.5.10 UPGRADE_PORT_VER=6.3.5.10 make ** Fix the problem and try again. Below is an extract from the stdout: (to go directly to the failed test search for ## You will also see repeated reports such as: coderInfo: unable to close module `YCBCR': Invalid shared object handle 0x800565c00. Extracts BEGIN:--- PASS: tests/rwfile_YUV_truecolor_70x46.sh exceptions: unable to close module `xc': Invalid shared object handle 0x80052c000. PASS: Magick++/tests/exceptions.sh appendImages: unable to close module `MIFF': Invalid shared object handle 0x80052d000. PASS: Magick++/tests/appendImages.sh attributes: unable to close module `GIF': Invalid shared object handle 0x80053b200. attributes: unable to close module `xc': Invalid shared object handle 0x80053b000. PASS: Magick++/tests/attributes.sh averageImages: unable to close module `MIFF': Invalid shared object handle 0x80052d000. PASS: Magick++/tests/averageImages.sh coalesceImages: unable to close module `MIFF': Invalid shared object handle 0x80052c000. PASS: Magick++/tests/coalesceImages.sh coderInfo: unable to close module `YCBCR': Invalid shared object handle 0x800565c00. coderInfo: unable to close module `XWD': Invalid shared object handle 0x800565a00. coderInfo: unable to close module `XPM': Invalid shared object handle 0x800565800. coderInfo: unable to close module `XCF': Invalid shared object handle 0x800565600. coderInfo: unable to close module `XC': Invalid shared object handle 0x800565400. coderInfo: unable to close module `XBM': Invalid shared object handle 0x800565200. coderInfo: unable to close module `X': Invalid shared object handle 0x800565000. coderInfo: unable to close module `WPG': Invalid shared object handle 0x80055fe00. coderInfo: unable to close module `WMF': Invalid shared object handle 0x80055fa00. coderInfo: unable to close module `WBMP': Invalid shared object handle 0x80055f800. coderInfo: unable to close module `VIFF': Invalid shared object handle 0x80055f600. coderInfo: unable to close module `VID': Invalid shared object handle 0x80055f400. coderInfo: unable to close module `VICAR': Invalid shared object handle 0x80055f200. coderInfo: unable to close module `UYVY': Invalid shared object handle 0x80055f000. coderInfo: unable to close module `URL': Invalid shared object handle 0x80055ce00. coderInfo: unable to close module `UIL': Invalid shared object handle 0x80055cc00. coderInfo: unable to close module `TXT': Invalid shared object handle 0x80055ca00. coderInfo: unable to close module `TTF': Invalid shared object handle 0x80055c800. coderInfo: unable to close module `TIM': Invalid shared object handle 0x80055c600. coderInfo: unable to close module `TILE': Invalid shared object handle 0x80055c400. coderInfo: unable to close module `TIFF': Invalid shared object handle 0x80055c200. coderInfo: unable to close module `THUMBNAIL': Invalid shared object handle 0x80055c000. coderInfo: unable to close module `TGA': Invalid shared object handle 0x800558e00. coderInfo: unable to close module `SVG': Invalid shared object handle 0x800557000. coderInfo: unable to close module `SUN': Invalid shared object handle 0x800553e00. coderInfo: unable to close module `STEGANO': Invalid shared object handle 0x800553c00. coderInfo: unable to close module `SGI': Invalid shared object handle 0x800553a00. coderInfo: unable to close module `SFW': Invalid shared object handle 0x800553800. coderInfo: unable to close module `SCT': Invalid shared object handle 0x800553600. coderInfo: unable to close module `SCR': Invalid shared object handle 0x800553400. coderInfo: unable to close module `RLE': Invalid shared object handle 0x800553200. coderInfo: unable to close module `RLA': Invalid shared object handle 0x800553000. coderInfo: unable to close module `RGB': Invalid shared object handle 0x80054fe00. coderInfo: unable to close module `RAW': Invalid shared object handle 0x80054fc00. coderInfo: unable to close module `PWP': Invalid shared object handle 0x80054fa00. coderInfo: unable to close module `PSD': Invalid shared object handle 0x80054f800. coderInfo: unable to close module `PS3': Invalid shared object handle 0x80054f600. coderInfo: unable to close module `PS2': Invalid
Current unassigned ports problem reports
___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
ImageMagick modules (Re: ImageMagick - portupgrade failure -amd64 openexr issues)
On понеділок 15 жовтень 2007, [EMAIL PROTECTED] wrote: = PASS: Magick++/tests/exceptions.sh = appendImages: unable to close module `MIFF': Invalid shared object handle = 0x80052d000. Module support remains broken, unfortunately, and is disabled by default. Please, run `make config' to disable modules and rebuild. Yours, -mi ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Undefined symbol _ZNSs20_S_empty_rep_storageE with net-p2p/mute-net
Hi all, I've just install net-p2p/mute-net without problem under FreeBSD 6.2, but when I'm trying to start it, I have this problem: [EMAIL PROTECTED] ~]$ fileSharingMUTE Running under /home/olivier/.mute-net/gui /usr/libexec/ld-elf.so.1: Undefined symbol _ZNSs20_S_empty_rep_storageE referenced from COPY relocation in ./fileSharingMUTE By searching on google, it seem that is related to gcc-3.3 How to fix this problem ? Thanks, Olivier ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ImageMagick modules (Re: ImageMagick - portupgrade failure -amd64 openexr issues)
On Monday 15 October 2007 06:07:51 Mikhail Teterin wrote: On понеділок 15 жовтень 2007, [EMAIL PROTECTED] wrote: = PASS: Magick++/tests/exceptions.sh = appendImages: unable to close module `MIFF': Invalid shared object handle = 0x80052d000. Module support remains broken, unfortunately, and is disabled by default. Please, run `make config' to disable modules and rebuild. Yours, -mi Thanks -- some questions: 1. Any idea how long Module support will remain broken? 2. does compiling with threads work properly? i.e. # make WITH_IMAGEMAGICK_THREADS=yes config # make WITH_IMAGEMAGICK_THREADS=yes I am now getting failure and warnings : ** Makefile possibly broken: graphics/ImageMagick: Makefile, line 105: warning: OpenEXR's libIlmThread may prevent PerlMagick from working Makefile, line 108: warning: DjVu requires threads and will not be supported ImageMagick-6.3.5.10_1 ** Listing the failed packages (*:skipped / !:failed) ! graphics/ImageMagick (ImageMagick-6.3.5.10) (Makefile broken) * www/gallery2 (gallery2-2.2.3) * multimedia/libxine (libxine-1.1.7_2) As you can see I have two depencies not upgrading due to ImageMagick OpenEXR version: [EMAIL PROTECTED] /usr/ports/graphics/ImageMagick]# pkg_info |grep OpenEXR OpenEXR-1.6.0 A high dynamic-range (HDR) image file format Thanks in advance david ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: I don't understand this
On Sun, 14 Oct 2007, Paul Schmehl wrote: Well, I'll tell you why *I* had trouble with it. When you run make install clean on the php?-extensions port, it *installs* the extensions. Naturally, I expected that when I ran the uninstall, it would uninstall the same ports that it installed previously. In fact, when you uninstall the php4-extensions port, it *says* it uninstalled, but it *does* nothing. It doesn't even remove the ports from the ports db - nor does it remove the files installed with each extension port. That's *not* expected behavior for a port. I had no problem correcting the problem, but I should have had to. If it's not possible to uninstall the extensions ports from php4-extensions, then it should tell you that when you try to run deinstall. For me it was a minor inconvenience. For a newbie, it could be a disaster. Easy solution -- when doing a 'make deinstall' from the php?-extensions port, simply post a message after deinstalling the meta port: WARNING: deinstallation of php?-extensions does NOT deinstall any php?-* ports install. If it is your intension to deinstall any php?-* ports installed by php?-extensions, ... insert proper way to do so here ... That protect newbies from the same mis-assumption that Paul had, teach newbies and experienced FreeBSD admins the right way and how meta-ports work in FreeBSD, and still protect the whole concept behind how meta-ports work. Beckman --- Peter Beckman Internet Guy [EMAIL PROTECTED] http://www.angryox.com/ --- ** PLEASE NOTE PurpleCow.com IS NOW AngryOx.com DO NOT USE PurpleCow.com ** ** PurpleCow.com is now owned by City Auto Credit LLC as of May 23, 2007 ** --- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ImageMagick modules (Re: ImageMagick - portupgrade failure -amd64 openexr issues)
понеділок 15 жовтень 2007 10:39 до, David Southwell Ви написали: 1. Any idea how long Module support will remain broken? This is a difficult question to answer, because it depends on the exact configurations -- some modules are just fine, but some others mess things up, when ImageMagick unloads them (via dlclose())... Jasper was a bad offender in the past, but I patched it a few weeks ago. There, probably, remain other evil-doers :( That said, you do not need module support -- there is no gain from them. Adding a third-party module (if any exists at all) remains possible even if ImageMagick's own modules are all linked in. ** Makefile possibly broken: graphics/ImageMagick: Makefile, line 105: warning: OpenEXR's libIlmThread may prevent PerlMagick from working Makefile, line 108: warning: DjVu requires threads and will not be supported ImageMagick-6.3.5.10_1 If you rebuilt the OpenEXR recently (be sure to read /usr/ports/UPDATING for details), you can ignore the OpenEXR warning. For DjVu it is, probably, best to just disable it -- it requires threads, which often make PerlMagick unusable, because perl is not threaded by default on FreeBSD. Unless you know, you need DjVu support for something, PerlMagick is, probably, more important to you than DjVu... As you can see I have two depencies not upgrading due to ImageMagick The warnings aren't supposed to trigger portupgrade's failure, but I rarely use the tool. There, likely, exists an option to cause it to try building the port regardless... Yours, -mi ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: I don't understand this
--On Monday, October 15, 2007 10:36:57 -0400 Peter Beckman [EMAIL PROTECTED] wrote: On Sun, 14 Oct 2007, Paul Schmehl wrote: Well, I'll tell you why *I* had trouble with it. When you run make install clean on the php?-extensions port, it *installs* the extensions. Naturally, I expected that when I ran the uninstall, it would uninstall the same ports that it installed previously. In fact, when you uninstall the php4-extensions port, it *says* it uninstalled, but it *does* nothing. It doesn't even remove the ports from the ports db - nor does it remove the files installed with each extension port. That's *not* expected behavior for a port. I had no problem correcting the problem, but I should have had to. If it's not possible to uninstall the extensions ports from php4-extensions, then it should tell you that when you try to run deinstall. For me it was a minor inconvenience. For a newbie, it could be a disaster. Easy solution -- when doing a 'make deinstall' from the php?-extensions port, simply post a message after deinstalling the meta port: WARNING: deinstallation of php?-extensions does NOT deinstall any php?-* ports install. If it is your intension to deinstall any php?-* ports installed by php?-extensions, ... insert proper way to do so here ... That protect newbies from the same mis-assumption that Paul had, teach newbies and experienced FreeBSD admins the right way and how meta-ports work in FreeBSD, and still protect the whole concept behind how meta-ports work. Bingo! Also, I'm wondering if it's possible to run pkg_deinstall -r in the meta port to remove all the ports that depend upon it. -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
DATADIR question
Hi!
I'm porting silvertree game (from creators of wesnoth), and I have
some issues with it's DATADIR.
The problem is that port is named silvertree, but it installs data under
${PREFIX}/share/silvertree-rpg. What do I do with DATADIR in this case?
1. Rename the port:
Not a best solution, as I'll have to introduce additional variables like
DISTNAME, which are overwise correct with their default values. Also,
this -rpg suffix may change in future.
2. Leave it as it is:
* Will install data to ${PREFIX}/share/silvertree-rpg
* Plist: share/silvertree-rpg/somefile
* portlint complaints, DATADIR is not used at all
3. Force configure to use DATADIR with adding --datadir to
CONFIGURE_ARGS
* Will install data to ${PREFIX}/share/silvertree/silvertree-rpg
* Plist: %%DATADIR%%/silvertree-rpg/somefile
4. Change DATADIR in port
* Will install data to ${PREFIX}/share/silvertree-rpg
* Plist: %%DATADIR%%/somefile
* DATADIR=${PREFIX}/share/silvertree-rpg
I think the correct way is 3 or 4, but I didn't find enough data on
DATADIR meaning: should it be user-changeable (i.e. user can install a
port without touching PREFIX but changing DATADIR), or is more like a
shortcut to sync port's Makefile and plist, so port could change it to
actual value and plist should only use %%DATADIR%%?
Seems that DATADIR user-changeable is not the case, as it's not even
passed to configure by default. So correct way is more like #4, am I
right?
--
Dmitry A. Marakasov| jabber: [EMAIL PROTECTED]
[EMAIL PROTECTED] | http://www.amdmi3.ru
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mysql51-server won't start after upgrade
On Sun, 14 Oct 2007, Jeffrey Williams wrote: I just upgraded mysql51-server with cvsup and portupgrade. Now it won't start, and the error I am getting is: [ERROR] /usr/local/libexec/mysqld: unknown variable 'innodb_log_arch_dir=/var/db/mysql/' I have been scanning the release notes, but I haven't found anything yet, that indicates that this variable has been deprecated, and it still appears in the example my.cnf files. I ran into this last week, too. I had to poke around in the InnoDB source for this (as far as I can tell this isn't documented anywhere), but apparently innodb_log_group_home_dir has superceded innodb_log_arch_dir since 4.0, so just change the latter to the former and everything works. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
[HEADSUP] last run of GNATS weekly reports was broken
When we upgraded the machine that hosts these reports, we missed some files, and the reports came out null. I am currently working on testing the corrected script. While I'm working on it, I'm going to make a few tweaks. Let me know if you see anything odd in the results. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Current unassigned ports problem reports
Current FreeBSD problem reports The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. Bugs can be in one of several states: o - open A problem report has been submitted, no sanity checking performed. a - analyzed The problem is understood and a solution is being sought. f - feedback Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution. p - patched A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open. r - repocopy The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion. s - suspended The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended. c - closed A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned. Critical problems Serious problems S Tracker Resp. Description o ports/106369vpnd caused kernel panic with ppp mode o ports/106372vpnd can't run with slip mode f ports/108077www/linux-flashplugin9 crashes linux-firefox f ports/108413net/vnc does not works. f ports/112385sysutils/lookupd on Kernel 64 f ports/112921x11-wm/Beryl not loading focus and keybinding settings f ports/113144print/ghostscript-gnu dumps core with several output d f ports/115818Executable clash between databases/grass and ruby gems f ports/115967enable chrooted net/isc-dhcp3-server on the FreeBSD 7. f ports/116378xorg 7.3 on -stable breaks math/scilab f ports/116385net/vnc using vnc.so crashes Xorg 7.3 when remote comp f ports/116586net/isc-dhcp3-server does not work when compiled with f ports/116753multimedia/MPlayer crashes after playing *.flv on 7.0- f ports/116777The math/scilab port fails in demos-signal-bode. f ports/116778security/nmap ping-scan misses some hosts f ports/116949security/vpnc: Some Cisco Concentrators refuse Connect o ports/117025multimedia/pwcbsd: Pwcbsd-1.4.0 + New USBStack not wor o ports/117119new port: emulators/dboxfe, a front-end to DosBox conf f ports/117128security/ipsec-tools racoon.sh fails with /var on mfs o ports/117144sysutils/nut : ACL with IPv6 address rejected o ports/117145[PATCH] math/dislin - update to 9.2 o ports/117194NEW PORT: security/openfwtk f ports/117196Port net/asterisk-addons 1.4.2 fails to compile 23 problems total. Non-critical problems S Tracker Resp. Description f ports/101166bittorrent-curses only works under English locales. o ports/107354net/icmpinfo: icmpinfo -vvv does not recocnize any ICM f ports/107937jailed net/isc-dhcp3-server wouldn't run with an immut f ports/111399print/ghostscript-gpl: ghostscript-gpl WITH_FT_BRIDGE f ports/111456[UPDATE] finance/pfpro updated distinfo f ports/112887net/nxserver 1.4.0_1 fails to compile after upgrading f ports/113423Update for ports net/freenx to version 0.6.0 f ports/114127net/vnc - vnc.so installed to bad location f ports/114825pam module security/pam_abl not working f ports/115304multimedia/gpac-mp4box cannot import files larger than f ports/115336port multimedia/avifile on FreeBSD 7.0 not BROKEN with f ports/115401Update port: graphics/ipe Version 6.0pre28 of Ipe that f ports/115627www/Lynx (-ssl) does not correctly test for OpenSSL f ports/116037multimedia/dvd-slideshow has been updated from 0.7.5 t f ports/116058Update: x11-themes/gtk-qt-engine to version 0.8 f ports/116120[patch] x11-toolkits/gtkdatabox2: update to 0.7.0.1 f ports/116142devel/cvsweb3 coloured side-by-side stopped working wh f ports/116226x11-wm/compiz - emerald and compiz-fusion and scim are f ports/116323net-im/jabber-users-agent bugs f ports/116327games/prboom fails to compile on amd/i386 FreeBSD7.0-C f ports/116333math/isabelle fails to build with SML/NJ; requires bas f ports/116422[patch] devel/kdbg: fix to allow a core file to be ope f ports/116454net/unison: should
Re: bin/11420 [nanobsd] Build failure on RELENG_6
The following reply was made to PR ports/11420; it has been noted by GNATS.
From: Henrik Brix Andersen [EMAIL PROTECTED]
To: M. Warner Losh [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: bin/11420 [nanobsd] Build failure on RELENG_6
Date: Tue, 16 Oct 2007 00:37:54 +0200
--ZPt4rx8FFjLCG7dd
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Jul 02, 2007 at 07:47:21AM -0600, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Henrik Brix Andersen [EMAIL PROTECTED] writes:
: On Sun, Jul 01, 2007 at 07:01:35PM -0600, M. Warner Losh wrote:
: In message: [EMAIL PROTECTED]
: Henrik Brix Andersen [EMAIL PROTECTED] writes:
: ...
: : [1]: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D114200
: =20
: This patch is incorrect.
: =20
: +.if !defined(NO_INSTALLLIB)
: =20
: should be
: =20
: +.if ${MK_INSTALLIB} !=3D no
:=20
: Oh - thanks for catching this. I guess the same change should be done
: in lib/ncurses/ncurses/Makefile, then?
=20
I belive so. I've CC'd ru@ to make sure.
Any updates on this? It would be nice to have this install problem fixed
before 7.0-RELEASE.
Regards,
Brix
--=20
Henrik Brix Andersen [EMAIL PROTECTED]
--ZPt4rx8FFjLCG7dd
Content-Type: application/pgp-signature
Content-Disposition: inline
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (FreeBSD)
Comment: GnuPG signed
iD8DBQFHE+vBv+Q4flTiePgRAnNRAJoCv66FAnzz41gRtJRO1Dxf+/3imwCgkad9
5AD37lBo8IF4kiTbwFcvR3o=
=E2ZK
-END PGP SIGNATURE-
--ZPt4rx8FFjLCG7dd--
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bin/11420 [nanobsd] Build failure on RELENG_6
On Mon, Oct 15, 2007 at 10:40:03PM +, Henrik Brix Andersen wrote: The following reply was made to PR ports/11420; it has been noted by GNATS. Sorry, this should have gone to bin/114200. Note to self: don't trust Subject: lines when hitting reply :) Regards, Brix -- Henrik Brix Andersen [EMAIL PROTECTED] pgpYdxAdSrwqZ.pgp Description: PGP signature
Change timezone on php
Timezone was changed to summer time in Brazil but the php timezonedb (port pecl-timezonedb) was not changed. I have patched this ports to run correctly. -su-2.05b# shar `find pecl-timezonedb/ -print` echo c - pecl-timezonedb/ mkdir -p pecl-timezonedb/ /dev/null 21 echo x - pecl-timezonedb/Makefile sed 's/^X//' pecl-timezonedb/Makefile 'END-of-pecl-timezonedb/Makefile' X# Ports collection makefile for: pecl-timezonedb X# Date created: 20 Oct 2006 X# Whom: Marcus Alves Grando [EMAIL PROTECTED] X# X# $FreeBSD: ports/misc/pecl-timezonedb/Makefile,v 1.4 2007/04/21 00:41:43 mnag Exp $ X# X XPORTNAME= timezonedb XDISTVERSION= 2007.8 XCATEGORIES=misc XMASTER_SITES= http://pecl.php.net/get/ XPKGNAMEPREFIX= pecl- XEXTRACT_SUFX= .tgz XDIST_SUBDIR= PECL X XMAINTAINER=[EMAIL PROTECTED] XCOMMENT= Timezone Database to be used with PHP's date and time functions X XUSE_PHP= yes XUSE_PHPEXT=yes XPHP_MODNAME= timezonedb XIGNORE_WITH_PHP=4 X XCONFIGURE_ARGS=--enable-timezonedb X X.include bsd.port.mk END-of-pecl-timezonedb/Makefile echo x - pecl-timezonedb/distinfo sed 's/^X//' pecl-timezonedb/distinfo 'END-of-pecl-timezonedb/distinfo' XMD5 (PECL/timezonedb-2007.8.tgz) = 4d4efe289a0547a164873a7d15b86424 XSHA256 (PECL/timezonedb-2007.8.tgz) = 99f3b3bfb0155ebe9f08e8f5107cbe194c3f6d60ee1ac4c40422386187fe3e2a XSIZE (PECL/timezonedb-2007.8.tgz) = 177801 END-of-pecl-timezonedb/distinfo echo x - pecl-timezonedb/pkg-descr sed 's/^X//' pecl-timezonedb/pkg-descr 'END-of-pecl-timezonedb/pkg-descr' XThis extension is a drop-in replacement for the builtin timezone database that Xcomes with PHP. You should only install this extension in case you need to get Xa later version of the timezone database then the one that ships with PHP. X XWWW: http://pecl.php.net/package/timezonedb END-of-pecl-timezonedb/pkg-descr echo x - pecl-timezonedb/patch-Makefile sed 's/^X//' pecl-timezonedb/patch-Makefile 'END-of-pecl-timezonedb/patch-Makefile' X--- Makefile.orig Mon Oct 15 20:47:03 2007 X+++ Makefile Mon Oct 15 20:39:28 2007 X@@ -6,7 +6,7 @@ X # X X PORTNAME= timezonedb X-DISTVERSION= 2007.5 X+DISTVERSION= 2007.8 X CATEGORIES= misc X MASTER_SITES= http://pecl.php.net/get/ X PKGNAMEPREFIX=pecl- END-of-pecl-timezonedb/patch-Makefile echo x - pecl-timezonedb/Makefile.orig sed 's/^X//' pecl-timezonedb/Makefile.orig 'END-of-pecl-timezonedb/Makefile.orig' X# Ports collection makefile for: pecl-timezonedb X# Date created: 20 Oct 2006 X# Whom: Marcus Alves Grando [EMAIL PROTECTED] X# X# $FreeBSD: ports/misc/pecl-timezonedb/Makefile,v 1.4 2007/04/21 00:41:43 mnag Exp $ X# X XPORTNAME= timezonedb XDISTVERSION= 2007.5 XCATEGORIES=misc XMASTER_SITES= http://pecl.php.net/get/ XPKGNAMEPREFIX= pecl- XEXTRACT_SUFX= .tgz XDIST_SUBDIR= PECL X XMAINTAINER=[EMAIL PROTECTED] XCOMMENT= Timezone Database to be used with PHP's date and time functions X XUSE_PHP= yes XUSE_PHPEXT=yes XPHP_MODNAME= timezonedb XIGNORE_WITH_PHP=4 X XCONFIGURE_ARGS=--enable-timezonedb X X.include bsd.port.mk END-of-pecl-timezonedb/Makefile.orig echo x - pecl-timezonedb/distinfo.orig sed 's/^X//' pecl-timezonedb/distinfo.orig 'END-of-pecl-timezonedb/distinfo.orig' XMD5 (PECL/timezonedb-2007.5.tgz) = 8c73725678581ba81f56b83afaa56282 XSHA256 (PECL/timezonedb-2007.5.tgz) = dd6fa6ca2193cb36dd84bcefe56b48f0d37ef25d480b45d13557d6a8c612cd9b XSIZE (PECL/timezonedb-2007.5.tgz) = 177842 END-of-pecl-timezonedb/distinfo.orig exit -- Giancarlo Rubio ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
