INDEX now builds successfully on 6.x
___ 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"
Unable to build ntp-devel
I recently updated Perl to 5.8.9 and ran the update script. There were no apparent problems. I have now tried to update the net/ntp-devel port to version 4.2.5p156 without success. Apparently, ntp-devel is looking the incorrect version of perl. The build ends with this error message: cc: /usr/local/lib/perl5/5.8.8/mach/auto/DynaLoader/DynaLoader.a: No such file or directory *** Error code 1 Stop in /usr/ports/net/ntp-devel/work/ntp-dev-4.2.5p156/ntpsnmpd. *** Error code 1 Apparently, that file does not exist. I tried check in the /usr/local/lib/perl5/5.8.9/mach/auto/DynaLoader/ directory, and the file is not there either. 1) Why is the build process looking in the wrong directory to start with? I updated Perl correctly, so it should be looking in the "5.8.9" directory. 2) How do I correct this problem. I can supply a copy of the build process upon request. It is also available here: http://seibercom.net/logs/ntp.txt -- Gerard ges...@yahoo.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"
evolution 2.24.3_1 not compiling... can anyone duplicate it before I raise a pr ??
Hi All I cant get the new evolution to compile up... just trying a simple make from within mail/evolution Mine is bugging out with; em-migrate.c: In function 'migrate_folders': em-migrate.c:2870: error: 'CAMEL_STORE_IS_MIGRATING' undeclared (first use in this function) em-migrate.c:2870: error: (Each undeclared identifier is reported only once em-migrate.c:2870: error: for each function it appears in.) gmake[4]: *** [em-migrate.lo] Error 1 gmake[4]: Leaving directory `/usr/ports/mail/evolution/work/evolution-2.24.3/mail' gmake[3]: *** [all-recursive] Error 1 gmake[3]: Leaving directory `/usr/ports/mail/evolution/work/evolution-2.24.3/mail' gmake[2]: *** [all] Error 2 rm GNOME_Evolution_Mail.server.in gmake[2]: Leaving directory `/usr/ports/mail/evolution/work/evolution-2.24.3/mail' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/mail/evolution/work/evolution-2.24.3' gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/mail/evolution. *** Error code 1 Stop in /usr/ports/mail/evolution. Anyone seeing the same. Thanks Craig B ___ 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"
portupgrade error when using -R
Hi! portupgrade gives me an error when using the -R switch on rrdtool. (using it on the port 'joe' does not seem to trigger it) [r...@foster ~]# portupgrade -Rrpv rrdtool ---> Session started at: Tue, 20 Jan 2009 13:53:16 + [Gathering depends for databases/rrdtool ... done] [Gathering depends for net-mgmt/cacti done] [Exclude up-to-date packages done] ---> Session ended at: Tue, 20 Jan 2009 13:53:33 + (consumed 00:00:17) /usr/local/lib/ruby/site_ruby/1.8/pkginfo.rb:74:in `initialize': : Not in due form: - (ArgumentError) from /usr/local/sbin/portupgrade:931:in `new' from /usr/local/sbin/portupgrade:931:in `do_upgrade' from /usr/local/sbin/portupgrade:815:in `main' from /usr/local/sbin/portupgrade:811:in `each' from /usr/local/sbin/portupgrade:811:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:785:in `initialize' from /usr/local/sbin/portupgrade:229:in `new' from /usr/local/sbin/portupgrade:229:in `main' from /usr/local/sbin/portupgrade:2208 using portupgrade-2.4.6,2. Running 'pkgdb -Fuv' and 'pkgdb -L' did not solve the problem. -- chs, ___ 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"
portupgrade error when using -R
Christer Solskogen writes: > ---> Session ended at: Tue, 20 Jan 2009 13:53:33 + (consumed 00:00:17) > /usr/local/lib/ruby/site_ruby/1.8/pkginfo.rb:74:in `initialize': : Not > in due form: - (ArgumentError) > from /usr/local/sbin/portupgrade:931:in `new' > from /usr/local/sbin/portupgrade:931:in `do_upgrade' > from /usr/local/sbin/portupgrade:815:in `main' > from /usr/local/sbin/portupgrade:811:in `each' > from /usr/local/sbin/portupgrade:811:in `main' > from /usr/local/lib/ruby/1.8/optparse.rb:785:in `initialize' > from /usr/local/sbin/portupgrade:229:in `new' > from /usr/local/sbin/portupgrade:229:in `main' > from /usr/local/sbin/portupgrade:2208 I get this occasionally, and not just on a particular port. Only specifying the base portname (i.e. "libgtop" instead of "libgtop-2.24.3" seems to increase the chances - but does not guerrantee - this will happen. Robert Huff ___ 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: PHP question
On Wed, 2009-01-14 at 15:26 -0500, Albert Thiel wrote: > I am trying to figure out how to get a working Apache 2.x server with PHP in > a safe configuration (or > as safe as possible based upon all the vulns). I do not need a database. > > What version and options is my best bet. I have tried on my own but losing > it. Nothing I have tried > works. This is the wrong list of general PHP setup instructions. PHP4 is dead. PHP5 is nearing beta1 of 5.3. Use 5.2.9 in the mean time. # cd /usr/ports/lang/php5 && make config && make install Modify your apache22 httpd.conf accordingly to activate the module. There are thousands of sites that explain the proces. Security with PHP involves writing code well, both in your application, and in the PHP engine -- as well as responsible administration: locking out insecure features in php.ini ~BAS signature.asc Description: This is a digitally signed message part
FreeBSD Port: xmlrpc-c-devel-1.11.00_2
I would like to submit the following. This patch (against trunk) allows for the shared libraries to be built and installed on a FreeBSD system. If you have any questions, please let me know. Thank you, Chad Index: config.mk.in === --- config.mk.in(revision 1615) +++ config.mk.in(working copy) @@ -232,6 +232,18 @@ NEED_WL_RPATH=yes endif +ifeq ($(findstring freebsd,$(HOST_OS)),freebsd) + SHARED_LIB_TYPE = unix + SHLIB_SUFFIX = so + MUST_BUILD_SHLIB = Y + MUST_BUILD_SHLIBLE = Y + shlibfn = $(1:%=%.$(SHLIB_SUFFIX).$(MAJ).$(MIN)) + shliblefn = $(1:%=%.$(SHLIB_SUFFIX)) + CFLAGS_SHLIB = -fpic + LDFLAGS_SHLIB = -shared -Wl,-soname,$(SONAME) $(SHLIB_CLIB) + NEED_WL_RPATH=yes +endif + ifeq ($(HOST_OS),dragonfly) SHARED_LIB_TYPE = unix MUST_BUILD_SHLIB = Y Chad J. Schroeder Software Systems Engineer Engineering & Technology Development LodgeNet Interactive Corporation 3900 West Innovation Street Sioux Falls, SD 57107-7002 Phone: 605-988-1489 Fax: 605-988-1491 chad.schroe...@lodgenet.com This e-mail and attached files contain LodgeNet confidential information intended for the exclusive use of the individual(s) to whom addressed. If you are not the intended recipient, please immediately delete this e-mail (and attached files) and treat the information as confidential. ___ 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 Port: squidGuard-1.4
Hello: I recently did a SG 1.3 to 1.4 portupgrade and it seems to have cleared out my /var/db/squidGuard dir. Does that make sense? As an aside, I would like to thank-you for maintaining this port - your work is appreciated. Rick Chisholm Sysadmin Parallel42 ___ 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: FreeBSD Port: squidGuard-1.4
Rick Chisholm wrote:
Hello:
I recently did a SG 1.3 to 1.4 portupgrade and it seems to have cleared
out my /var/db/squidGuard dir. Does that make sense?
Hi!
It does make sense. It depends on how the port was first installed.
When taking maintainership I did not modify the original logic.
Since ports are expected not to leave files behind when deinstalled,
port logic checks on first install if ${DATADIR} exists. If it does it
will NOT be created/populated and NOT included in the plist, and not
removed on deinstall.
On the contrary if it does not find such directory it will create,
populate it remove it on deinstall.
BTW, the default datadir is /var/db/squidGuard.
This logic is there to adhere to porting guidelines and make
portlint/tinderboxes happy, and also give first time users a working
software. It could be changed, but I can't just have the port create a
directory full of files and then leave them there.
One solution could be to just create the directory before
installing/upgrading the software one time, then it will be left there
untouched.
As an aside, I would like to thank-you for maintaining this port - your
work is appreciated.
Thank you a lot. I'm open to suggestions to how to make the port better.
I just have to follow porting guidelines regarding not leaving files behind.
--
Guido Falsi
___
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"
gnome-power-manager fails to build
Trying to build this port on FreeBSD 7.1 release but it fails either using just make or portupgrade, I cvsuped my ports twice in the last two days to no avail. file=`echo tr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/local/bin/msgfmt -o $file tr.po file=`echo uk | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/local/bin/msgfmt -o $file uk.po file=`echo vi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/local/bin/msgfmt -o $file vi.po file=`echo zh_CN | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/local/bin/msgfmt -o $file zh_CN.po file=`echo zh_HK | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/local/bin/msgfmt -o $file zh_HK.po file=`echo zh_TW | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/local/bin/msgfmt -o $file zh_TW.po gmake[2]: Leaving directory `/usr/ports/sysutils/gnome-power-manager/wo rk/gnome-power-manager-2.24.3/po' Making all in docs gmake[2]: Entering directory `/usr/ports/sysutils/gnome-power-manager/w ork/gnome-power-manager-2.24.3/docs' gmake[2]: Nothing to be done for `all'. gmake[2]: Leaving directory `/usr/ports/sysutils/gnome-power-manager/wo rk/gnome-power-manager-2.24.3/docs' Making all in man gmake[2]: Entering directory `/usr/ports/sysutils/gnome-power-manager/w ork/gnome-power-manager-2.24.3/man' docbook2man gnome-power-manager.sgml > gnome-power-manager.1 gmake[2]: *** [gnome-power-manager.1] Error 8 gmake[2]: Leaving directory `/usr/ports/sysutils/gnome-power-manager/wo rk/gnome-power-manager-2.24.3/man' ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.1 8830.0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=gnome-power-manager-2. 22.1_2 UPGRADE_PORT_VER=2.22.1_2 make ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! sysutils/gnome-power-manager (gnome-power-manager-2.22.1_2)(u nknown build error) Any idea what might be causing this? ___ 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: FreeBSD Port: squidGuard-1.4
Guido Falsi wrote:
> Since ports are expected not to leave files behind when deinstalled,
> port logic checks on first install if ${DATADIR} exists. If it does it
> will NOT be created/populated and NOT included in the plist, and not
> removed on deinstall.
>
> On the contrary if it does not find such directory it will create,
> populate it remove it on deinstall.
The way that this is traditionally handled is for the port to install
both file and file.sample, but only list file.sample in the plist.
Then at deinstall time there should be a script to compare file to
file.sample and remove file if it is the same. Repeat for values of
$file as needed.
It is not expected or desirable for a port to remove user-modified
files (including those files created by a daemon).
hth,
Doug
--
This .signature sanitized for your protection
___
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"
java/jboss5 - buildable
Hi ports, I saw that java/jboss5 is marked as broken and it's a little bit old version and I decided to try to build the latest version manually so I've downloaded jboss-5.0.0.GA-src.tar.gz, extracted it and just ran build/build.sh from the distribution it's built perfectly fine without any problems and without me doing anything and I was able to start the server I have the following ports installed: apache-ant-1.7.0_2 diablo-jdk-1.6.0.07.02_3 - for amd64 and my platform is: $ uname -a FreeBSD mydomain.org 8.0-CURRENT FreeBSD 8.0-CURRENT #4: Sun Jan 18 11:37:53 EET 2009 myu...@mydomain.org:/usr/obj/usr/src/sys/Ss-CURRENT amd64 I guess you could update this port I'm not very much in the ports system otherwise I could just send you a patch for this port Regards Mario ___ 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"
