Re: [ANNOUNCE] mod_perl-2.0.4
Philip M. Gollucci wrote: Philippe M. Chiasson wrote: | Philip M. Gollucci wrote: | Philippe M. Chiasson wrote: | | | http://tinderbox-i386.p6m7g8.net/tb/errors/8.0-FreeBSD/mod_perl2-2.0.4,3.log | | | FWIW, also on 7.0 | http://tinderbox-i386.p6m7g8.net/tb/errors/7.0-FreeBSD/mod_perl2-2.0.4,3.log | | | What's in xs/modperl_xs_typedefs.h:67 ? (it's generated, so I can | easily | | tell) | | ~From the 8-current tree: | http://p6m7g8.com/modperl_xs_typedefs.h | | I don't have a FreeBSD machine handy, so, Philip, is there any chance you | could try and figure out a little more about what's going on? You do now, account info in offlist e-mail. | | Something is tripping up the compiler, so maybe | apache/include/apr_thread_rwlock.h has something funky in there (or isn't | even there) My APR was compiled without Threads (/var/db/pkg/apr-nothr) Sounds like a problem with APR without threads. I'll look at tweaking the detection. I think this patch to a bit of *magical* code should do the trick. Index: lib/ModPerl/BuildMM.pm === --- lib/ModPerl/BuildMM.pm (revision 648960) +++ lib/ModPerl/BuildMM.pm (working copy) @@ -359,7 +359,7 @@ $apr_config ||= $build-get_apr_config(); -if ($path =~ m/(Thread|Global)Mutex/) { +if ($path =~ m/(Thread|Global)(Mutex|RWLock)/) { return unless $apr_config-{HAS_THREADS}; } Feels like something that doesn't belong in there, but rather in the configuration somewhere in xs/maps... -- Philippe M. Chiasson GPG: F9BFE0C2480E7680 1AE53631CB32A107 88C3A5A5 http://gozer.ectoplasm.org/ m/gozer\@(apache|cpan|ectoplasm)\.org/ signature.asc Description: OpenPGP digital signature
portupgrade and quotes inside pkgtools.conf
Hi list- I'm trying to upgrade apache22 installed from ports using portupgrade under FreeBSD 6.3-STABLE. %portupgrade --version portupgrade 2.4.3 Here is apache22 related information in pkgtools.conf: MAKE_ARGS = { 'www/apache22' = [ 'WITHOUT_IPV6=1', 'WITH_STATIC_MODULES=include rewrite auth vhost_alias', 'WITH_SUEXEC=yes', 'SUEXEC_DOCROOT=/home', 'WITH_SSL_MODULES=yes', ], } It looks like I'm having problems with WITH_STATIC_MODULES=include rewrite auth vhost_alias containing quotes (). Here is the error I receive while executing 'portupgrade apache-2.2.4': ** Makefile possibly broken: www/apache22: Syntax error: Unterminated quoted string /usr/ports/Mk/bsd.apache.mk, line 228: warning: for module in auth_basic auth_digest authn_file authn_dbd authn_dbm authn_anon authn_default authn_alias authz_host authz_groupfile authz_user authz_dbm authz_owner authz_default cache disk_cache file_cache mem_cache dav dav_fs actions alias asis autoindex cern_meta cgi charset_lite dbd deflate dir dumpio env expires headers imagemap include info log_config logio mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias filter version ssl suexec ; do echo include | /usr/bin/grep -wq ${module} 2 /dev/null ; if [ ${?} = 0 ] ; then echo --enable-${module}; else echo --enable-${module}=shared; fi; done returned non-zero status Syntax error: Unterminated quoted string /usr/ports/Mk/bsd.apache.mk, line 254: warning: for module in auth_basic auth_digest authn_file authn_dbd authn_dbm authn_anon authn_default authn_alias authz_host authz_groupfile authz_user authz_dbm authz_owner authz_default cache disk_cache file_cache mem_cache dav dav_fs actions alias asis autoindex cern_meta cgi charset_lite dbd deflate dir dumpio env expires headers imagemap include info log_config logio mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias filter version ssl suexec ; do echo include | /usr/bin/grep -wq ${module} 2 /dev/null || echo ${module}; done returned non-zero status apache-2.2.8 /usr/local/sbin/portupgrade:1433:in `get_pkgname': Makefile broken (MakefileBrokenError) from /usr/local/sbin/portupgrade:622:in `main' from /usr/local/sbin/portupgrade:613:in `each' from /usr/local/sbin/portupgrade:613:in `main' from /usr/local/sbin/portupgrade:588:in `catch' from /usr/local/sbin/portupgrade:588:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:1254:in `call' from /usr/local/lib/ruby/1.8/optparse.rb:1254:in `order!' from /usr/local/lib/ruby/1.8/optparse.rb:1205:in `catch' from /usr/local/lib/ruby/1.8/optparse.rb:1205:in `order!' from /usr/local/lib/ruby/1.8/optparse.rb:1196:in `order' from /usr/local/sbin/portupgrade:565:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:755:in `initialize' from /usr/local/sbin/portupgrade:229:in `new' from /usr/local/sbin/portupgrade:229:in `main' from /usr/local/sbin/portupgrade:2173 Removing quotes gives the following: --- Upgrading 'apache-2.2.4' to 'apache-2.2.8' (www/apache22) --- Building '/usr/ports/www/apache22' with make flags: WITHOUT_IPV6=1 WITH_STATIC_MODULES=include rewrite auth vhost_alias WITH_SUEXEC=yes SUEXEC_DOCROOT=/home WITH_SSL_MODULES=yes make: don't know how to make rewrite. Stop ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! www/apache22 (apache-2.2.4) (clean error) Your advise would be greatly appreciated. Thank you. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Operation not permitted after Updating ports
On Mon, Apr 21, 2008 at 12:15:09PM +0200, Johan Hendriks wrote: I have a small question After the update of a compat port i get the following errors after installing a port! Updating the pkgdb ... Operation not permitted - /usr/local/lib/compat/pkg/libc.so.5 Try something like chflags -R noschg /usr/local/lib/compat ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Operation not permitted after Updating ports
On Mon, Apr 21, 2008 at 12:15:09PM +0200, Johan Hendriks wrote: After the update of a compat port i get the following errors after installing a port! Updating the pkgdb ... Operation not permitted - /usr/local/lib/compat/pkg/libc.so.5 Operation not permitted - /usr/local/lib/compat/pkg/libc_r.so.5 Operation not permitted - /usr/local/lib/compat/pkg/libcrypt.so.2 Operation not permitted - /usr/local/lib/compat/pkg/libthread.so.1 Operation not permitted - /usr/local/lib/compat/pkg/libthr.so.1 Probably caused by said libraries having the schg (immutable) flag set on them. Use the -o flag with /bin/ls to see if it's set. Use chflags(8) to remove it. Keep in mind that you won't be able to use chflags(8) to fix the files if the kern.securelevel sysctl is 1 or higher. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Operation not permitted after Updating ports
I have a small question After the update of a compat port i get the following errors after installing a port! Updating the pkgdb ... Operation not permitted - /usr/local/lib/compat/pkg/libc.so.5 Try something like chflags -R noschg /usr/local/lib/compat Thanks that did the trick Regards, Johan Hendriks ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Operation not permitted after Updating ports
I have a small question After the update of a compat port i get the following errors after installing a port! Updating the pkgdb ... Operation not permitted - /usr/local/lib/compat/pkg/libc.so.5 Operation not permitted - /usr/local/lib/compat/pkg/libc_r.so.5 Operation not permitted - /usr/local/lib/compat/pkg/libcrypt.so.2 Operation not permitted - /usr/local/lib/compat/pkg/libthread.so.1 Operation not permitted - /usr/local/lib/compat/pkg/libthr.so.1 I reinstalled the compat ports but the error still is there. What can I do to resolve this. Regards, Johan Hendriks ___ 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 o ports/108413[patch] net/vnc does not works. o ports/111832ports/lang/drscheme doesn't compile: foreign.c f ports/112921x11-wm/Beryl not loading focus and keybinding settings s ports/113144print/ghostscript-gnu dumps core with several output d o 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/116777The math/scilab port fails in demos-signal-bode. f ports/116778security/nmap ping-scan misses some hosts o ports/117025multimedia/pwcbsd: Pwcbsd-1.4.0 + New USBStack not wor o ports/117128security/ipsec-tools racoon.sh fails with /var on mfs o ports/118808Fix to build ports/lang/drscheme on FreeBSD-7.0 o ports/118877audio/streamripper does not detect song title from str o ports/120372java/linux-sun-jdk16: linux-sun-jre1.6.0 plugin doesn' o ports/121473graphics/gsnapshot crashes upon startup on FreeBSD-6.3 f ports/121830net-mgmt/nagios-plugins: check_disk plugin works incor f ports/122083www/mod_clamav refuses to build with apache22 installe o ports/122128Class not found error during print/pdftk port installa o ports/122251New port: graphics/sK1 An opensource vector graphics e f ports/122276Compiled audio/musicpd segfaults on FreeBSD 7.0 o ports/122306misc/compat5x port fails to extract if you're root o ports/122381net-mgmt/collectd in FreeBSD 7.0 i386 and sparc64 segf f ports/122416deskutils/kmatrix3d and deskutils/ksmoothdock don't in f ports/122791[patch] net-mgmt/collectd - fix WITH_APACHE dependency o ports/122812[Update] www/dokeos : update to 1.8.4 o ports/122832print/ghostscript-gpl/Makefile contains two CONFLICTS f ports/122874[patch] www/havp: update havp to latest 0.88 o ports/122886New version of port textproc/ctpp2: 2.2.0 o ports/122903Update port: net/iscsi-target o ports/122904[patch] jdk15/javaws fails on amd64 f ports/122907[patch] sysutils/fusefs-kmod dataloss on write shortly f ports/122911ports/audio/sox: MP3 support broken f ports/122949net-mgmt/kismet coredumps 36 problems total. Non-critical problems S Tracker Resp. Description o ports/85513 Intel C++ compiler not 100% binary compatible with sys o ports/95294 netpipe doesn't work on amd64 o ports/102544ltmdm driver (comms/ltmdm) crashes system whene line r o ports/107354net/icmpinfo: icmpinfo -vvv does not recocnize any ICM o ports/108795ports/icc: Proposed update to icc port for intel compi o ports/110144New port: math/Matlab7 o ports/110697New port: ports-mgmt/pkg_deps o ports/114825pam module security/pam_abl not working s ports/115216ADA devel/florist exit_process program doesn't compile s ports/115217Ada devel/florist socket program doesn't compile due t f ports/115304
Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed
On Sat, 19 Apr 2008 21:06:40 -0500 Larry Rosenman [EMAIL PROTECTED] wrote: Please do let me know. Still no good. Same exact error with a CURRENT built just this morning (Mon, Apr. 21, 7:00 am CDT). I noticed some conditional compilation stuff in one of the files, based on the version of FreeBSD being used. Perhaps we need some more of that? Thanks! -Original Message- From: Conrad J. Sabatier [mailto:[EMAIL PROTECTED] Sent: Saturday, April 19, 2008 8:46 PM To: Larry Rosenman Cc: 'Kemian Dang'; 'Jeremy Chadwick'; [EMAIL PROTECTED] Subject: Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed On Sat, 19 Apr 2008 20:36:55 -0500 Larry Rosenman [EMAIL PROTECTED] wrote: Do you have a Current 8-Current? What is the date of your sources? It's a pretty current Current. :-) FreeBSD serene.no-ip.org 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Fri Apr 18 01:11:50 CDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOM amd64 In the process now of upgrading sources again and rebuilding world/kernel. We'll see what happens. The version of lsof I have in ports is 4.79, the final release version (minus any of the versioning suffix letters). -Original Message- From: Conrad J. Sabatier [mailto:[EMAIL PROTECTED] Sent: Saturday, April 19, 2008 8:26 PM To: Larry Rosenman Cc: 'Kemian Dang'; 'Jeremy Chadwick'; [EMAIL PROTECTED] Subject: Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed On Fri, 18 Apr 2008 09:51:36 -0500 Larry Rosenman [EMAIL PROTECTED] wrote: You need to upgrade your system sources. The way the developers have implemented some locking changes makes it hard for the lsof configure script to do the right thing. Please upgrade to current RELENG_7, and all should be fine with the 4.79,1 port. Thanks! Larry Rosenman sysutils/lsof maintainer. The lsof upgrade fails in a slightly different manner under 8-CURRENT: cc -pipe -Wno-error -fno-strict-aliasing -Wno-error -DHASEFFNLINK=i_effnlink -D HASF_VNODE -DHASCPUMASK_T -DHASSBSTATE -DHAS_KVM_VNODE -DHAS_UFS1_2 -DHAS_NO_SI_ UDEV -DHAS_SI_PRIV -DHAS_SYS_SX_H -DHAS_LOCKF_ENTRY -DFREEBSDV=8000 -DHASFDESCFS=2 -DHASPSEUDOFS -DHASNULLFS -DHASIPv6 -DHAS_STRFTIME -DLSOF_VSTR=\8.0-CURRENT\ -I/usr/src/sys -O2 -c dnode.c dnode.c: In function 'process_node': dnode.c:760: error: 'struct inode' has no member named 'i_lockf' dnode.c:761: error: 'struct inode' has no member named 'i_lockf' *** Error code 1 So...good to go with RELENG_7, but not HEAD? Hmmm. -- Every man thinks God is on his side. The rich and powerful know he is. -- Jean Anouilh, French dramatist and playwright ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed
I've sent a note to Vic Abell (lsof author) about this. Thanks for the report. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 -Original Message- From: Conrad J. Sabatier [mailto:[EMAIL PROTECTED] Sent: Monday, April 21, 2008 7:09 AM To: Larry Rosenman Cc: 'Kemian Dang'; 'Jeremy Chadwick'; [EMAIL PROTECTED] Subject: Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed On Sat, 19 Apr 2008 21:06:40 -0500 Larry Rosenman [EMAIL PROTECTED] wrote: Please do let me know. Still no good. Same exact error with a CURRENT built just this morning (Mon, Apr. 21, 7:00 am CDT). I noticed some conditional compilation stuff in one of the files, based on the version of FreeBSD being used. Perhaps we need some more of that? Thanks! -Original Message- From: Conrad J. Sabatier [mailto:[EMAIL PROTECTED] Sent: Saturday, April 19, 2008 8:46 PM To: Larry Rosenman Cc: 'Kemian Dang'; 'Jeremy Chadwick'; [EMAIL PROTECTED] Subject: Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed On Sat, 19 Apr 2008 20:36:55 -0500 Larry Rosenman [EMAIL PROTECTED] wrote: Do you have a Current 8-Current? What is the date of your sources? It's a pretty current Current. :-) FreeBSD serene.no-ip.org 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Fri Apr 18 01:11:50 CDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOM amd64 In the process now of upgrading sources again and rebuilding world/kernel. We'll see what happens. The version of lsof I have in ports is 4.79, the final release version (minus any of the versioning suffix letters). -Original Message- From: Conrad J. Sabatier [mailto:[EMAIL PROTECTED] Sent: Saturday, April 19, 2008 8:26 PM To: Larry Rosenman Cc: 'Kemian Dang'; 'Jeremy Chadwick'; [EMAIL PROTECTED] Subject: Re: Upgrading 'lsof-4.79K' to 'lsof-4.79,1' failed On Fri, 18 Apr 2008 09:51:36 -0500 Larry Rosenman [EMAIL PROTECTED] wrote: You need to upgrade your system sources. The way the developers have implemented some locking changes makes it hard for the lsof configure script to do the right thing. Please upgrade to current RELENG_7, and all should be fine with the 4.79,1 port. Thanks! Larry Rosenman sysutils/lsof maintainer. The lsof upgrade fails in a slightly different manner under 8-CURRENT: cc -pipe -Wno-error -fno-strict-aliasing -Wno-error -DHASEFFNLINK=i_effnlink -D HASF_VNODE -DHASCPUMASK_T -DHASSBSTATE -DHAS_KVM_VNODE -DHAS_UFS1_2 -DHAS_NO_SI_ UDEV -DHAS_SI_PRIV -DHAS_SYS_SX_H -DHAS_LOCKF_ENTRY -DFREEBSDV=8000 -DHASFDESCFS=2 -DHASPSEUDOFS -DHASNULLFS -DHASIPv6 -DHAS_STRFTIME -DLSOF_VSTR=\8.0-CURRENT\ -I/usr/src/sys -O2 -c dnode.c dnode.c: In function 'process_node': dnode.c:760: error: 'struct inode' has no member named 'i_lockf' dnode.c:761: error: 'struct inode' has no member named 'i_lockf' *** Error code 1 So...good to go with RELENG_7, but not HEAD? Hmmm. -- Every man thinks God is on his side. The rich and powerful know he is. -- Jean Anouilh, French dramatist and playwright ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Recent ImageMagick change breaks some configure scripts
Hi, the move of the place where the include directories are put breaks some configure scripts. Namely those which only have the possibility to specify the install prefix of the ImageMagick port. Those scripts will take install_location/include and install_location/lib automatically. This change now requires changes to such ports. As I'm in the process of porting some software which depends upon ImageMagick, I downgraded for the moment to the previous version of ImageMagick to be able to work further on porting the software. Please check if this change is really needed, as it's more easy to change the ImageMagick port than to fix each port which depends upon ImageMagick. Thanks, Alexander. -- NANCY!! Why is everything RED?! http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Request to commit a patch: ports/110969
Hi last week someone posted a followup about net-snmp 5.4: he had a problem with an OID. I posted a patch on the same PR (ports/110969) and the person told me it fixed his problem. Could someone please commit this patch? (Even if the PR is closed). Thanks Valerio Daelli ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OpenBSD's isakmpd port maintainership
Edwin Groothuis [EMAIL PROTECTED] wrote: Seems that isakmpd (security/isakmpd) is outdated. I'm currently using it in my production environment. I would like to know does somebody working on bring isakmpd back sync'ed with current OpenBSD code base. Send patches, and poke me on #bsdports on Efnet. I'm very interested in them. This would also open the door for porting ipsecctl(8). Hmmm. -- Christian naddy Weisgerber [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recent ImageMagick change breaks some configure scripts
the move of the place where the include directories are put breaks some configure scripts. Namely those which only have the possibility to specify the install prefix of the ImageMagick port. Those scripts will take install_location/include and install_location/lib automatically. This change now requires changes to such ports. As I'm in the process of porting some software which depends upon ImageMagick, I downgraded for the moment to the previous version of ImageMagick to be able to work further on porting the software. Please check if this change is really needed, as it's more easy to change the ImageMagick port than to fix each port which depends upon ImageMagick. Not easily -- the ImageMagick developers want it this way now, and continuing to patch it for the old way will be difficult. It will also make it harder to use GraphicsMagick (which I recommend strongly) in ImageMagick's stead. The simple fact of the matter is, unfortunately, that ImageMagick crew simply DO NOT CARE for the backward compatibility issues. They change the APIs routinely and even arguments for their command-line utilities change from version to version without much regard... GraphicsMagick split away for this reasons. Yours, -mi ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
cmucl and sbcl keep crashing on FreeBSD 7.0
To whom may concern: I check port tree and know that this address is maintainer mailbox for sbcl port. I've sent similar mail to cmucl maintainer but had no reply yet. I've upgrade to freebsd 7.0 release for quite some times. However, I could not run cmucl and sbcl binary from port package. And the attempts to build from port tree were also failed. Prebuilt sbcl/cmucl core kept crashing every time when building port sources. And clisp compiler complained lots of undefined function names when building sbcl source. Weird, I saw freebsd site still provide binary port packages for cmucl and sbcl both under 7.0-release and 7-stable directories. And there are also many fb7.0 precompiled binaries at cmucl offical site for download. But none of them work for my fb7.0. Do I miss something? Could u give me some inputs about how to fix it? best regards qxb below is stack info shown in gdb when cmucl crashed: - Program terminated with signal 11, Segmentation fault. #0 0x67ff in ?? () (gdb) bt #0 0x67ff in ?? () #1 0x61790e5b in ?? () #2 0x4800 in ?? () #3 0x2000 in ?? () #4 0x0007 in ?? () #5 0x1012 in ?? () #6 0x in ?? () #7 0x in ?? () #8 0x in ?? () #9 0x61713000 in ?? () #10 0x0170 in ?? () #11 0xbfbfe748 in ?? () #12 0x0000 in ?? () #13 0x4800 in ?? () #14 0x2000 in ?? () #15 0x0805cef2 in ?? () #16 0xbfbfe738 in ?? () #17 0x080544ca in os_validate (addr=0x4800, len=536870912) at ../../src/lisp/FreeBSD-os.c:129 Previous frame identical to this frame (corrupt stack?) -- ... there have been two really clean, consistent models of programming so far: the C model and the Lisp model. These two seem points of high ground, with swampy lowlands between them. --Paul Graham ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: lzma (Re: HEADS UP: upgrading ImageMagick to 6.4.0-6)
On Tue, Apr 15, 2008 at 10:07:54PM -0500, Brooks Davis wrote: On Tue, Apr 15, 2008 at 10:35:30PM -0400, Mikhail Teterin wrote: 15 ??? 2008 10:21 ??, Brooks Davis ?? : Sadly, the author's licensing terms will limit the adoption of lzma. The BSD license is well established as the most restrictive acceptable license for successful, widely adopted compression schemes. I wouldn't necessicairly be opposed to seeing support for tar.lzma files in bsd.port.mk, but I don't think lzma has a signficant future if the licensing policy remains as is (i.e. complex and not clearly defined in the source files). == qouth lzma.txt == SPECIAL EXCEPTION #3: Igor Pavlov, as the author of this code, expressly permits you to use code of the following files: BranchTypes.h, LzmaTypes.h, LzmaTest.c, LzmaStateTest.c, LzmaAlone.cpp, LzmaAlone.cs, LzmaAlone.java as public domain code. Without a more careful look, it sounds like enough to integrate lzma in libarchive. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: lzma (Re: HEADS UP: upgrading ImageMagick to 6.4.0-6)
On Mon, Apr 21, 2008 at 11:05:42PM +0400, Andrew Pantyukhin wrote: On Tue, Apr 15, 2008 at 10:07:54PM -0500, Brooks Davis wrote: On Tue, Apr 15, 2008 at 10:35:30PM -0400, Mikhail Teterin wrote: 15 ??? 2008 10:21 ??, Brooks Davis ?? : Sadly, the author's licensing terms will limit the adoption of lzma. The BSD license is well established as the most restrictive acceptable license for successful, widely adopted compression schemes. I wouldn't necessicairly be opposed to seeing support for tar.lzma files in bsd.port.mk, but I don't think lzma has a signficant future if the licensing policy remains as is (i.e. complex and not clearly defined in the source files). == qouth lzma.txt == SPECIAL EXCEPTION #3: Igor Pavlov, as the author of this code, expressly permits you to use code of the following files: BranchTypes.h, LzmaTypes.h, LzmaTest.c, LzmaStateTest.c, LzmaAlone.cpp, LzmaAlone.cs, LzmaAlone.java as public domain code. Without a more careful look, it sounds like enough to integrate lzma in libarchive. That's well hidden (DOC/lzam.txt in the tarball). Someone should produce some sort of lzma-lite distribution that only does the basics. Then this could be a practical option. -- Brooks pgp7kKWQWNrpm.pgp Description: PGP signature
Re: Thunderbird, enigmail, and GCC 3.4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Coleman, Finally I caught the issue for thunderbird. It was due to the difference between our floating point handling and Linux's counterpart. ~ The patch attached would fix the problem at thunderbird part. Unfortunately enigmail plugin compiled with gcc 4.x as shipped with FreeBSD 7.0+ would still crash with Signal 11, but with gcc 3.4 it would work fine. I have not yet figured out why this would happen... Cheers, - -- Xin LI [EMAIL PROTECTED]http://www.delphij.net/ FreeBSD - The Power to Serve! -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.8 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEUEARECAAYFAkgND6wACgkQi+vbBBjt66D0awCY4lzwwwmAaOLuoGEVo9OEHI8u ZwCfUi2KfOWUR3GFFCSiba6g5YK/sjg= =wLNg -END PGP SIGNATURE- Index: Makefile === RCS file: /home/ncvs/ports/mail/thunderbird/Makefile,v retrieving revision 1.90 diff -u -p -r1.90 Makefile --- Makefile19 Apr 2008 17:51:46 - 1.90 +++ Makefile21 Apr 2008 21:58:18 - @@ -8,7 +8,7 @@ PORTNAME= thunderbird DISTVERSION= 2.0.0.12 -PORTREVISION= 2 +PORTREVISION= 3 CATEGORIES=mail ipv6 MASTER_SITES= ${MASTER_SITE_MOZILLA_EXTENDED} MASTER_SITE_SUBDIR=thunderbird/releases/${DISTVERSION}/source Index: files/patch-Double.cpp === RCS file: /home/ncvs/ports/mail/thunderbird/files/patch-Double.cpp,v retrieving revision 1.2 diff -u -p -r1.2 patch-Double.cpp --- files/patch-Double.cpp 16 Nov 2003 18:55:33 - 1.2 +++ files/patch-Double.cpp 21 Apr 2008 21:05:06 - @@ -1,20 +1,20 @@ extensions/transformiix/source/base/Double.cpp.origThu Jan 30 09:26:46 2003 -+++ extensions/transformiix/source/base/Double.cpp Sun Nov 16 01:46:42 2003 -@@ -51,10 +51,10 @@ +--- extensions/transformiix/source/base/Double.cpp.orig2006-06-22 12:13:00.0 -0700 extensions/transformiix/source/base/Double.cpp 2008-04-21 14:04:37.540570448 -0700 +@@ -52,10 +52,10 @@ //A trick to handle IEEE floating point exceptions on FreeBSD - E.D. #ifdef __FreeBSD__ #include ieeefp.h -#ifdef __alpha__ -fp_except_t allmask = FP_X_INV|FP_X_OFL|FP_X_UFL|FP_X_DZ|FP_X_IMP; -#else -+#if defined(__i386__) ++#if defined(__i386__) || defined(__amd64__) fp_except_t allmask = FP_X_INV|FP_X_OFL|FP_X_UFL|FP_X_DZ|FP_X_IMP|FP_X_DNML; +#else +fp_except_t allmask = FP_X_INV|FP_X_OFL|FP_X_UFL|FP_X_DZ|FP_X_IMP; #endif fp_except_t oldmask = fpsetmask(~allmask); #endif -@@ -75,22 +75,31 @@ +@@ -115,22 +115,31 @@ #define TX_DOUBLE_HI32_EXPMASK 0x7ff0 #define TX_DOUBLE_HI32_MANTMASK 0x000f ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: comms/acfax
What is considered the best Satellite Tracking program predictor, in real time, for Ubuntu? Thanks, Roland, KB8XI [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: comms/acfax
On Mon, Apr 21, 2008 at 07:41:07PM -0400, Roland Burgan wrote: What is considered the best Satellite Tracking program predictor, in real time, for Ubuntu? Why not run http://www.pcbsd.org instead and just install the PBI for gpredict or predict? It is a lot easier. - 73 Diane VA3DB (amsat coordinator) -- - [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.db.net/~db ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cmucl and sbcl keep crashing on FreeBSD 7.0
,--- You/Xuebin (Tue, 22 Apr 2008 01:50:02 +0800) * | | To whom may concern: | | I check port tree and know that this address is maintainer mailbox for sbcl | port. I've sent similar mail to cmucl maintainer but had no reply | yet. If you look at the CMUCL version in ports, you will find it to be way old: 19c (which was probably the year 2003) -- i.e. the CMUCL port has not been maintained for quite a while. The FreeBSD distributions at CMUCL's site have been actively maintained and you will find both the 19e-pre2 and the 2008-04 snapshot there for all the latest FreeBSD versions (6.3, 7.0 and 8.0) there. | I've upgrade to freebsd 7.0 release for quite some times. However, I could | not run cmucl and sbcl binary from port package. And the attempts to build | from port tree were also failed. Prebuilt sbcl/cmucl core kept crashing | every time when building port sources. And clisp compiler complained lots of | undefined function names when building sbcl source. Right, you won't be able to build with old (pre 2007-12) CMUCLs on FreeBSD -- the issue was addressed in November 2007. | Weird, I saw freebsd site still provide binary port packages for cmucl and | sbcl both under 7.0-release and 7-stable directories. And there are also | many fb7.0 precompiled binaries at cmucl offical site for download. Things are kept current at the CMUCL site -- and that's the place to get the FreeBSD distributions at this time. -- Alex -- [EMAIL PROTECTED] -- /* * Between grand theft and a legal fee, there only stands a law degree. */ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: fldigi-2.10
On Mon, Apr 21, 2008 at 06:39:46PM -0700, Chris Maness wrote: Hello, Diane, I am having trouble getting fldigi to compile. Also, the binary install core dumps (signal 11) on two different FreeBSD installs. This is on release 7.0. hrmmm ugh fldigi-2.10 runs fine here on i386 FreeBSD 7.0. What architecture are you on? Does it happen to be amd64? I'll need to see a gdb bt if you can. /usr/bin/ld: cannot find -lgio-2.0 gmake: *** [libgiofam.la] Error 1 *** Error code 2 Stop in /usr/ports/devel/gio-fam-backend. *** Error code 1 This problem is actually in devel/gio-fam-backend I have duplicated the problem. /usr/bin/ld: cannot find -lgio-2.0 gmake: *** [libgiofam.la] Error 1 *** Error code 2 But I am not sure how this could happen. Are your ports up to date? Basically gio-fam-backend has a dependancy on /usr/ports/devel/glib20 or should have. Unless glib20 port is installed first, libgiofam will fail. I've only taken a quick cursory look, but it appears this might be related to a commit to /usr/ports/Mk/bsd.gnome.mk # $FreeBSD: ports/Mk/bsd.gnome.mk,v 1.146 2008/03/24 15:59:55 marcus Exp $ In the meantime, cd /usr/ports/devel/glib20;make install then return to your fldigi build. Also, I have been able to get tlf working in console using screen. You might have already known this, but I just found out about it a couple of weeks ago. Maybe put a small notice about screen for vt100 compatibility in the install script. I had sent you an e-mail regarding the terminal issues a while back, but I guess that would be a good fix. The only issue I have found is that backspace still does not work under FreeBSD. Yes, I remember your comment about that. I'll look at it again, thanks. - 73 Diane VA3DB -- - [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.db.net/~db ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]