Re: Firefox & thunderbird crash saving a file
On 12/7/06, Jeremy Messenger <[EMAIL PROTECTED]> wrote: Guys, more of 'me too' are so useless. Please make your bug report useful. marcus is still waiting for someone to fill out his request[1]. I can't fill out his request, because I still can't reproduce it on two systems. If I can reproduce it then his request will be complete, because all of my ports are always compile with the debug. I shall rebuild things with debugging enabled and see if I can get a meaningful trace next time it happens. /JMS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Firefox & thunderbird crash saving a file
Jeremy Messenger wrote: > > > Guys, more of 'me too' are so useless. Please make your bug report > useful. marcus is still waiting for someone to fill out his request[1]. > I can't fill out his request, because I still can't reproduce it on two > systems. If I can reproduce it then his request will be complete, > because all of my ports are always compile with the debug. > > [1] > http://lists.freebsd.org/pipermail/freebsd-gnome/2006-November/016179.html I'm about half way through rebuilding everything with debug symbols, but FYI I can reproduce this at will just by trying to print with CUPS from either thunderbird or firefox 2.0. The traces I have gotten make it look like threading problems, and they persist using libpthread or libthr. 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 "[EMAIL PROTECTED]"
Re: php 5.2.0... go boom!
Hi Jonathan, You can check the order php loads it's extensions by looking at /usr/local/etc/php/extensions.ini Kind regards, Spil. On 07/12/06, Jonathan Horne <[EMAIL PROTECTED]> wrote: hi spil, i did end up getting my 5.1.6 back, i just reloaded that folder from some nightly backups. for now, i am still on 5.1.6. about the only php application im having trouble with, is phpsysinfo. apache 2.2.x and 2.0.x both have the same behavior. can you tell me how to check the order the modules are loading? phpsysinfo requires xml and pcre extensions. cheers, and thanks for remembering my thread, jonathan On Thursday 07 December 2006 05:51, you wrote: > Hi Jonathan, > > Have you found a solution yet to your segfaulting php 5.2.0? > There are reports that it has to do with the order of loading the > extensions (notably, session seems to have to be one of the last, and > mysql last) > > Please let me know if it helps (and even if it doesn't) or any other > solutions. My php 5.2.0 still won't fly (although the debug-version > does!). > > See > http://lists.freebsd.org/pipermail/freebsd-ports/2006-November/036596.html > > Kind regards, > > Spil > > On 08/11/06, Jonathan Horne <[EMAIL PROTECTED]> wrote: > > well, im franticly researching that bit of text that has flashed by > > during countless portupgrades... "backing up previous version". right > > about now, i would LOVE to have php 5.1.6_3 back... > > > > 1) anyone else have bad luck with the upgrade to 5.2.0? my httpd-error > > logs are filling with this: > > > > [Tue Nov 07 20:49:09 2006] [notice] child pid 58928 exit signal > > Segmentation fault (11 > > > > 2) can anyone shed light on the fabled "way of backing out of a > > portupgrade gone awry? > > > > thanks, > > jonathan > > ___ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > > "[EMAIL PROTECTED]" ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: php 5.2.0... go boom!
wait, wasn't the word on that to put extension=session.so up into the first line, else boom? mario;> So, Spil Oss wrote: > Hi Jonathan, > > You can check the order php loads it's extensions by looking at > /usr/local/etc/php/extensions.ini > > Kind regards, > > Spil. > > On 07/12/06, Jonathan Horne <[EMAIL PROTECTED]> wrote: >> hi spil, >> >> i did end up getting my 5.1.6 back, i just reloaded that folder from >> some nightly backups. for now, i am still on 5.1.6. about the only >> php application im having trouble with, is phpsysinfo. apache 2.2.x >> and 2.0.x both have the same behavior. can you tell me how to check >> the order the modules are loading? phpsysinfo requires xml and pcre >> extensions. >> >> cheers, and thanks for remembering my thread, >> jonathan >> >> On Thursday 07 December 2006 05:51, you wrote: >> > Hi Jonathan, >> > >> > Have you found a solution yet to your segfaulting php 5.2.0? >> > There are reports that it has to do with the order of loading the >> extensions (notably, session seems to have to be one of the last, >> and mysql last) >> > >> > Please let me know if it helps (and even if it doesn't) or any other >> solutions. My php 5.2.0 still won't fly (although the debug-version >> does!). >> > >> > See >> > http://lists.freebsd.org/pipermail/freebsd-ports/2006-November/036596.html >> > >> > Kind regards, >> > >> > Spil >> > >> > On 08/11/06, Jonathan Horne <[EMAIL PROTECTED]> wrote: >> > > well, im franticly researching that bit of text that has flashed >> by during countless portupgrades... "backing up previous version". >> right about now, i would LOVE to have php 5.1.6_3 back... >> > > >> > > 1) anyone else have bad luck with the upgrade to 5.2.0? my >> httpd-error logs are filling with this: >> > > >> > > [Tue Nov 07 20:49:09 2006] [notice] child pid 58928 exit signal >> Segmentation fault (11 >> > > >> > > 2) can anyone shed light on the fabled "way of backing out of a >> portupgrade gone awry? >> > > >> > > thanks, >> > > jonathan >> > > ___ >> > > freebsd-questions@freebsd.org mailing list >> > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> > > To unsubscribe, send any mail to >> > > "[EMAIL PROTECTED]" >> > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Cleaning out the ports
Dear all, I am looking for a good way to clean out the installed ports: when having used a system for some time, one is often left with leave ports that do not have any direct use (e.g. a library) and are not required anymore by any other installed port. Is there a way to find such ports and remove them easily? Best regards, Erwin Van de Velde ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Cleaning out the ports
On 08/12/2006, at 9:04 PM, Erwin Van de Velde wrote: Dear all, I am looking for a good way to clean out the installed ports: when having used a system for some time, one is often left with leave ports that do not have any direct use (e.g. a library) and are not required anymore by any other installed port. Is there a way to find such ports and remove them easily? pkg_cutleaves (available from sysutils/pkg_cutleaves) will help you to identify packages that are not required. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Cleaning out the ports
> Dear all, > > I am looking for a good way to clean out the installed ports: when > having used a system for some time, one is often left with leave > ports that do not have any direct use (e.g. a library) and are not > required anymore by any other installed port. Is there a way to find > such ports and remove them easily? Have a look at sysutils/pkg_cutleaves and sysutils/pkg_rmleaves. Emanuel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Cleaning out the ports
Erwin Van de Velde wrote: > I am looking for a good way to clean out the installed ports: when having > used > a system for some time, one is often left with leave ports that do not have > any direct use (e.g. a library) and are not required anymore by any other > installed port. Is there a way to find such ports and remove them easily? sysutils/pkg_rmleaves -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
x11-toolkits/py-wxPython26-unicode build failure with python2.5
wxPython-2.6.3.3 fails to build on my FreeBSD-6.1 with Python-2.5, with
cc -DNDEBUG -O -pipe -D__wchar_t=wchar_t -DTHREAD_STACK_SIZE=0x10 -O -pipe
-fPIC -DSWIG_TYPE_TABLE=_wxPython_table -DHAVE_CONFIG_H -DWXP_USE_THREAD=1
-UNDEBUG -DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES
-DNO_GCC_PRAGMA -DXTHREADS -DXUSE_MTSAFE_API -Iinclude -Isrc
-I/usr/X11R6/include/wx-2.6/gtk2-unicode-release-2.6
-I/usr/X11R6/include/wx-2.6 -I/usr/local/include/atk-1.0
-I/usr/local/include/cairo -I/usr/local/include/glib-2.0
-I/usr/local/lib/glib-2.0/include -I/usr/X11R6/include/gtk-2.0
-I/usr/X11R6/lib/gtk-2.0/include -I/usr/X11R6/include/pango-1.0
-I/usr/X11R6/include -I/usr/local/include/freetype2 -I/usr/local/include
-I/usr/local/include/python2.5 -c src/gtk/_core_wrap.cpp -o
build-gtk2.unicode/temp.freebsd-6.1-PRERELEASE-amd64-2.5/src/gtk/_core_wrap.o
-O3
src/gtk/_core_wrap.cpp: In function `void wxSizerItem_SetUserData(wxSizerItem*,
PyObject*)':
src/gtk/_core_wrap.cpp:3193: error: 'class wxSizerItem' has no member named
'SetUserData'
The wxSizerItem declaration in include/wx/sizer.h includes:
#if wxABI_VERSION > 20602
void SetUserData(wxObject* userData)
{ delete m_userData; m_userData = userData; }
#endif
but the code seems to indicate that wxABI_VERSION should be 20699 automatically
when building wxPython itself.
--
How many Vietnam vets does it take to screw in a light bulb?
You don't know, man. You don't KNOW.
Cause you weren't THERE. http://bash.org/?255991
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
rsync with --flags patch: unable to rsync hardlinks to files w/ schg
Hi *, we're running two jail-hosts with some jails in it. The two hosts (will) replicate the active jails to each other to have a fallback. On the backup-host I run the following command: rsync -avHWx -e ssh --flags --delete [EMAIL PROTECTED]:/data/jails/ /data/jails Doing so brings me the following errors for each jail: rsync: link "/data/jails/jail4711/usr/bin/chfn" => jail4711/usr/bin/ypchsh failed: Operation not permitted (1) rsync: link "/data/jails/jail4711/usr/bin/chpass" => jail4711/usr/bin/ypchsh failed: Operation not permitted (1) rsync: link "/data/jails/jail4711/usr/bin/chsh" => jail4711/usr/bin/ypchsh failed: Operation not permitted (1) rsync: link "/data/jails/jail4711/usr/bin/ypchfn" => jail4711/usr/bin/ypchsh failed: Operation not permitted (1) rsync: link "/data/jails/jail4711/usr/bin/ypchpass" => jail4711/usr/bin/ypchsh failed: Operation not permitted (1) rsync: link "/data/jails/jail4711/usr/bin/passwd" => jail4711/usr/bin/yppasswd failed: Operation not permitted (1) These files have the "schg" flag on jailhost1, which get rsynced to jailhost2. Theese files are not present on jailhost2 after this: ls: /data/jails/jail4711/usr/bin/passwd: No such file or directory Any idea how to get rid of this? Regards Raphael Becker ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Account Details Verification.
Dear Valued Customer, Commonwealth Bank Groups is currently working to increase security for all Online Banking users. To ensure the integrity of our online payment system, we periodically review your accounts. Your account might be restricted due to numerous login attempts into your online account. Restricted accounts continue to receive payments, but they are limited in their ability to send or withdraw funds. To lift up this restriction, you need to confirm your online banking details..In order to confirm your account stability. Click on the following link to confirm your online banking details. [1]http://www.commbank.com.au/update _ *Important* You are required to provide all necessary information completely and correctly otherwise, due to security reasons, we may have to close your account temporarily. Yours sincerely, Commonwealth Bank of Australia commbank.com.au/NetBank References 1. http://www.ladelund.eu/pics/I/www/www3.netbank.commbank.com.au/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
(Bug|Port)athon next weekend (Dec. 16/17)
Hey folks, We're going to hold the next (bug|port)athon next weekend. Same place as usual (@freebsd-bugbusters on EFNet). As you may know, some of our ports committers have been working hard on fixing ports to be X11BASE-clean so that the PREFIX merge can be done without (too much) hassle. Anyway, work isn't finished and we could probably use your help. The ports PR count is approximately 815 and we could easily do better than that, so join IRC next weekend and help us close some of those PRs. Cheers. PS: A PR a day keeps the doctor away. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: OpenPGP digital signature
Re: distfile belongs to?
On Thu, Dec 07, 2006 at 10:22:13PM -0800, Doug Barton wrote:
> Doug Barton wrote:
> > Wesley Shields wrote:
> >
> >> Part 2 (the bsd.port.mk piece) is the patch posted by Doug with Ade's
> >> suggestions.
> >
> > You missed the second patch I sent with the ${file%:*} changes.
>
> One more for fun. :) I was looking through bsd.port.mk for another
> purpose tonight and came across ${ALLFILES}. Not only does it combine
> dist and patch files into one variable, it has the benefit of not
> adding the : stuff to the filenames in the first place.
>
> Learning as I go,
Me too! I've just sent your patch (thanks again) and the pkg_info
piece.
http://www.freebsd.org/cgi/query-pr.cgi?pr=106483
We'll see where things go from here!
-- WXS
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Qt4 in Ports
Hi, Would like to know if the forecast to include the Qt4 in ports. Therefore still I am developing my applications in Qt3 and would like to use Qt4. Thanks, Cristiano Panvel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [CFR] ftp/curl update and API incompatibility
On Fri, Dec 08, 2006 at 07:57:59PM +0200, Peter Pentchev wrote: > On Wed, Dec 06, 2006 at 02:56:57PM +0200, Peter Pentchev wrote: > > Hi, > > > > I'm writing to you all because you are listed as maintainers of ports > > that depend directly on ftp/curl. Attached is a patch that updates > > ftp/curl to version 7.16.0; however, this update might need some testing. > > After some comments from some of the maintainers, here's an updated > version of the patch, which also takes care of the ports that do not > specify a shared library version in the curl dependency (i.e. they depend > on "curl", not "curl.3"). This patch also: > - bumps the PORTREVISION of the ftp/php4-curl, ftp/php5-curl, and > www/pecl-pecl_http ports; [snip] And of course, as Alex Dupre kindly pointed out, the PORTREVISION on php5-curl should be 1, not 2. Updated curl-16-03.patch available at http://people.FreeBSD.org/~roam/patches/curl/ G'luck, Peter -- Peter Pentchev [EMAIL PROTECTED][EMAIL PROTECTED][EMAIL PROTECTED] PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 If this sentence didn't exist, somebody would have invented it. pgp7Zc63SflvD.pgp Description: PGP signature
FreeBSD Port: ataidle-0.9
Hi Bruce, I recently downloaded and installed ataidle (version ataidle-0.9 for freebsd). Unfortunately it refused to work. After some digging around on internet I found the following post (http://www.archivesat.com/FreeBSD_hardware/thread435791.htm). Fortunately I do have a FreeNAS system running so I took ataidle from that system and it worked. So can you make a new binary build for freebsd somewhere in the future? Thanks in advance, Marc -- Marc Kip [EMAIL PROTECTED] 040-2845257 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bsdstats 5.3 on 6-STABLE and netcat weirdness
On Wed, Dec 06, 2006 at 10:19:06PM +0800, LI Xin wrote:
> Marc G. Fournier wrote:
> >
> > 'k, I don't know how to fix this one ... I thought about doing:
> >
> > .if ${OSVERSION} <= 492101
> > RUN_DEPENDS=nc:${PORTSDIR}/net/netcat
> > .endif
> >
> > not sure which version brought in nc, but 492101 is the last of the 4.x
> > series
> > ... but it portlint fails miserably if I don't put bsd.port.pre.mk before
> > it,
> > but also fails if I do:
> >
> > WARN: Makefile: no MASTER_SITES found. is it ok?
> > WARN: Makefile: "RUN_DEPENDS" has to appear earlier.
> > 0 fatal errors and 2 warnings found.
> >
> > Is there a better way of doing this ... ?
>
> I think you want something like:
>
> .if ${OSVERSION} < 503102 || (${OSVERSION} >= 60 && ${OSVERSION} <
> 600010)
>
> instead of just considering 492101.
That's a good suggestion.
Mark, as to the portlint problem - well, portlint cannot really be
expected to handle each and every corner case in a port Makefile :)
It is doing a wonderful job as it is, but every now and then you have
to make a choice between a working port and a clean port ;)
To make the OSVERSION check work, you do indeed need a bsd.port.pre.mk
inclusion before it. Then... just ignore the portlint warnings.
And... thanks for a great utility! :)
G'luck,
Peter
--
Peter Pentchev [EMAIL PROTECTED][EMAIL PROTECTED][EMAIL PROTECTED]
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553
I am the meaning of this sentence.
pgpgfGwBpJiKC.pgp
Description: PGP signature
Re: lang/gnat-gcc41 build error
Petr, if you still have interest in building gnat-gcc41 please try the attached ports. It is no longer possible to use your own GNAT for bootstrapping; the procedure starts with downloading binary version of GNAT 3.15p, which builds 3.4, which builds 4.1. You may not like that very much, but I'd like you to know that my priority is simplicity and stability and that I am grateful for your reports which helped me in that direction. -- Regards, Karel Miklav gnat-gcc34.tbz Description: Binary data gnat-gcc41.tbz Description: Binary data ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: distfile belongs to?
Wesley Shields wrote:
> On Thu, Dec 07, 2006 at 10:22:13PM -0800, Doug Barton wrote:
>> Doug Barton wrote:
>>> Wesley Shields wrote:
>>>
Part 2 (the bsd.port.mk piece) is the patch posted by Doug with Ade's
suggestions.
>>> You missed the second patch I sent with the ${file%:*} changes.
>> One more for fun. :) I was looking through bsd.port.mk for another
>> purpose tonight and came across ${ALLFILES}. Not only does it combine
>> dist and patch files into one variable, it has the benefit of not
>> adding the : stuff to the filenames in the first place.
>>
>> Learning as I go,
>
> Me too! I've just sent your patch (thanks again) and the pkg_info
> piece.
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=106483
>
> We'll see where things go from here!
Great! I hate to say this, but I just sent a followup to the PR with a
slight mod for the show.c patch. My fault for not testing that bit
previously. Otherwise it looks fantastic, and I encourage the portmgr
folks to test it ASAP. :)
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 "[EMAIL PROTECTED]"
FreeBSD Port: aolserver-openacs-pg-4.0.10_2
Hi Aldert, I'm just checking to see if you are still maintaining this port. I spent the better part of 2 days trying to get OpenACS installed in such a way as to use the xowiki package. I've installed and de- installed a few times... :) I'm scripting the output from my installation process now, so if I do get everything to work, I'd be happy to share my experience so that others may benefit. Best, Prem Thomas ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to break the bootstrapping chain
I'm trying to maintain the gnat-gcc* Ada compiler ports, currently there are gnat-gcc34 and 41. I'd like to introduce newer versions, and retire experimental 34, which is built from an ancient binary which requires FreeBSD 4 compatibility. I'd like to know: 1. what do I have to do that gnat-gcc packages will appear on FreeBSD FTP sites? 2. can I use one of FreeBSD packages to bootstrap others or do I have to somehow provide my own binary? In case I was not clear enough: the GNAT compiler can only be bootstrapped with another GNAT. If I base the procedure on a FreeBSD package, I can no longer provide the port for that package ... or do I? Damn, who invented this chicken and egg thing :) -- Regards, Karel Miklav ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to break the bootstrapping chain
On Fri, Dec 08, 2006 at 10:12:04PM +0100, Karel Miklav wrote: > I'm trying to maintain the gnat-gcc* Ada compiler ports, > currently there are gnat-gcc34 and 41. I'd like to > introduce newer versions, and retire experimental 34, > which is built from an ancient binary which requires > FreeBSD 4 compatibility. I'd like to know: > > 1. what do I have to do that gnat-gcc packages will > appear on FreeBSD FTP sites? Get a buildable package committed to the FreeBSD ports tree. > 2. can I use one of FreeBSD packages to bootstrap > others or do I have to somehow provide my own > binary? You'd need to provide your own binary. Kris pgpJr7AoiAScY.pgp Description: PGP signature
Re: How to break the bootstrapping chain
On Fri, 8 Dec 2006, Karel Miklav wrote: I'm trying to maintain the gnat-gcc* Ada compiler ports, currently there are gnat-gcc34 and 41. I'd like to introduce newer versions, and retire experimental 34, which is built from an ancient binary which requires FreeBSD 4 compatibility. I'd like to know: 1. what do I have to do that gnat-gcc packages will appear on FreeBSD FTP sites? 2. can I use one of FreeBSD packages to bootstrap others or do I have to somehow provide my own binary? In case I was not clear enough: the GNAT compiler can only be bootstrapped with another GNAT. If I base the procedure on a FreeBSD package, I can no longer provide the port for that package ... or do I? Damn, who invented this chicken and egg thing :) You'll have to do the same thing as the lang/gnat port and provide your own bootstrapping compiler. No matter what you do (*), it will require FreeBSD-X compat. AFAIK, we are currently supporting FreeBSD 5, 6, and 7, so the bootstrap should be based on FreeBSD-5, so it can work for 6 and 7 as well. If it is based on 6 or 7, then it will not be able to work on the other two. (*) The only way you can avoid this, is to provide 3 different bootstrap compilers (one for 5, 6, and 7) and teach the port to depend on the appropriate bootstrapper. -- DE ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: php 5.2.0... go boom!
On Fri, 2006-12-08 at 01:54 -0800, Mario Theodoridis wrote: > wait, > wasn't the word on that to put > extension=session.so > up into the first line, else boom? Not exactly. Moving sessions to first position worked for _me_. People report same problem with other modules too - it's random. It's general problem with extensions loading order; it's mentioned on main php site ( previous discussions contain links ). M. -- Citroën Xantia HDi 2.0 110KM '00 Plaisir gris quartz #4438 Warszawa / Kolobrzeg ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to break the bootstrapping chain
Kris Kennaway wrote: On Fri, Dec 08, 2006 at 10:12:04PM +0100, Karel Miklav wrote: 1. what do I have to do that gnat-gcc packages will appear on FreeBSD FTP sites? Get a buildable package committed to the FreeBSD ports tree. Ups, sorry, they _are_ on the main site. They're just not mirrored on couple other sites I checked. -- Thanks, Karel Miklav ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to break the bootstrapping chain
On Sat, Dec 09, 2006 at 12:14:43AM +0100, Karel Miklav wrote: > Kris Kennaway wrote: > >On Fri, Dec 08, 2006 at 10:12:04PM +0100, Karel Miklav wrote: > >> 1. what do I have to do that gnat-gcc packages will > >>appear on FreeBSD FTP sites? > > > >Get a buildable package committed to the FreeBSD ports tree. > > Ups, sorry, they _are_ on the main site. They're just not > mirrored on couple other sites I checked. They are there right now, but once the corresponding port changes they will change/go away. The packages are just a reflection of the current state of the ports tree. Kris pgpZoVGE6KRVk.pgp Description: PGP signature
Re: How to break the bootstrapping chain
Le Sam 9 déc 06 à 0:14:43 +0100, Karel Miklav <[EMAIL PROTECTED]> écrivait : > Kris Kennaway wrote: > >On Fri, Dec 08, 2006 at 10:12:04PM +0100, Karel Miklav wrote: > >> 1. what do I have to do that gnat-gcc packages will > >>appear on FreeBSD FTP sites? > > > >Get a buildable package committed to the FreeBSD ports tree. > > Ups, sorry, they _are_ on the main site. They're just not > mirrored on couple other sites I checked. I guess that you need one binary package to bootstrap, *and* your source tarball. See the port lang/mlton for such an example. -- Th. Thomas. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to break the bootstrapping chain
Thank you Daniel. Now when I see that the gnat-gcc packages actually are on the FTP servers, there's no need to panic. Those who are not comfortable with backwards compatibility stuff installed as a result of building from ports can just install the package. There's not really much to improve, except if I provide separate binaries for FreeBSD 5 and maybe 6. I'll keep abusing your bootstrapper till then ... and yeah, thanks for that too ;) -- Karel Miklav ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
xorg-nestserver won't build on 4.11, says stdint.h missing
I've been having a really weird video problem on my two machines when running 4.11. My 4.11 machines run XFree86 4.5.0 I have a dual-head setup I've been using for a few years. Recently, the left monitor looks like it has a vertical sync problem, but I'm pretty sure it's not the video hardware, because only host "lightning" have the problem until today. Now "daemon" also has it. I can pull the drives out (mobile racks) and put FreeBSD 6.1 in and these don't have the problem. So I thought I'd switch to xorg. But when I try to build xorg-nestserver or xorg-server, the build breaks complaining that stdint.h doesn't exist. Can anyone confirm that these ports will build under 4.11? -- i386 FreeBSD 4.11-STABLE There are 10 types of people in this world. Ones that understand binary and then, the others. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg-nestserver won't build on 4.11, says stdint.h missing
On Fri, Dec 08, 2006 at 07:19:27PM -0500, Steven Friedrich wrote: > I've been having a really weird video problem on my two machines when running > 4.11. My 4.11 machines run XFree86 4.5.0 > > I have a dual-head setup I've been using for a few years. Recently, the left > monitor looks like it has a vertical sync problem, but I'm pretty sure it's > not the video hardware, because only host "lightning" have the problem until > today. Now "daemon" also has it. I can pull the drives out (mobile racks) > and put FreeBSD 6.1 in and these don't have the problem. > > So I thought I'd switch to xorg. But when I try to build xorg-nestserver or > xorg-server, the build breaks complaining that stdint.h doesn't exist. > > Can anyone confirm that these ports will build under 4.11? It's possible you're the first person to try it. You really should try to migrate off of 4.x, maintainers are not required to support it and all support will soon be terminated. Kris pgpzBXpNqNKkD.pgp Description: PGP signature
Re: xorg-nestserver won't build on 4.11, says stdint.h missing
On Friday 08 December 2006 19:27, Kris Kennaway wrote: > On Fri, Dec 08, 2006 at 07:19:27PM -0500, Steven Friedrich wrote: > > I've been having a really weird video problem on my two machines when > > running 4.11. My 4.11 machines run XFree86 4.5.0 > > > > I have a dual-head setup I've been using for a few years. Recently, the > > left monitor looks like it has a vertical sync problem, but I'm pretty > > sure it's not the video hardware, because only host "lightning" have the > > problem until today. Now "daemon" also has it. I can pull the drives > > out (mobile racks) and put FreeBSD 6.1 in and these don't have the > > problem. > > > > So I thought I'd switch to xorg. But when I try to build xorg-nestserver > > or xorg-server, the build breaks complaining that stdint.h doesn't exist. > > > > Can anyone confirm that these ports will build under 4.11? > > It's possible you're the first person to try it. You really should > try to migrate off of 4.x, maintainers are not required to support it > and all support will soon be terminated. > > Kris oki doki. From perusing the web site, I can see that I have to upgrade thru the 5.x series first, if I do a source upgrade. If I do a binary upgrade, I can go straight to 6.1, right? -- i386 FreeBSD 4.11-STABLE There are 10 types of people in this world. Ones that understand binary and then, the others. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg-nestserver won't build on 4.11, says stdint.h missing
On Friday 08 December 2006 19:27, Kris Kennaway wrote: > On Fri, Dec 08, 2006 at 07:19:27PM -0500, Steven Friedrich wrote: > > I've been having a really weird video problem on my two machines when > > running 4.11. My 4.11 machines run XFree86 4.5.0 > > > > I have a dual-head setup I've been using for a few years. Recently, the > > left monitor looks like it has a vertical sync problem, but I'm pretty > > sure it's not the video hardware, because only host "lightning" have the > > problem until today. Now "daemon" also has it. I can pull the drives > > out (mobile racks) and put FreeBSD 6.1 in and these don't have the > > problem. > > > > So I thought I'd switch to xorg. But when I try to build xorg-nestserver > > or xorg-server, the build breaks complaining that stdint.h doesn't exist. > > > > Can anyone confirm that these ports will build under 4.11? > > It's possible you're the first person to try it. You really should > try to migrate off of 4.x, maintainers are not required to support it > and all support will soon be terminated. > > Kris oki doki. From perusing the web site, I can see that I have to upgrade thru the 5.x series first, if I do a source upgrade. If I do a binary upgrade, I can go straight to 6.1, right? Opps, I've been reading the Install notes for 5.x and I can't do a binary pgrade from 4.x. -- i386 FreeBSD 4.11-STABLE There are 10 types of people in this world. Ones that understand binary and then, the others. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
freebsd current No module named xish.domish again
# /usr/local/etc/rc.d/jabber-pyaim-transport start Starting jabber_pyaim. Could not find the XML DOM. If you're using Twisted 2.x make sure you have twisted.words installed. Traceback (most recent call last): File "/usr/local/lib/jabber/pyaim/PyAIMt.py", line 11, in ? import main File "/usr/local/lib/jabber/pyaim/src/main.py", line 4, in ? import utils File "/usr/local/lib/jabber/pyaim/src/utils.py", line 12, in ? from tlib.twistwrap import Element, SuxElementStream File "/usr/local/lib/jabber/pyaim/src/tlib/twistwrap.py", line 68, in ? from twisted.xish.domish import SuxElementStream, Element, unescapeFromXml, elementStream ImportError: No module named xish.domish and last times fixes don't do it this time :( randy ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: php 5.2.0... go boom!
On Fri, Dec 08, 2006 at 11:54:27PM +0100, Miros?aw Jaworski wrote: > On Fri, 2006-12-08 at 01:54 -0800, Mario Theodoridis wrote: > > wait, > > wasn't the word on that to put > > extension=session.so > > up into the first line, else boom? > > Not exactly. > > Moving sessions to first position worked for _me_. > People report same problem with other modules too - it's random. Our production web server (4.11-STABLE, Apache 2.2.3, PHP 5.2.0) uses the following order with success: $ cat /usr/local/etc/php/extensions.ini extension=gd.so extension=mysql.so extension=zlib.so extension=session.so extension=pcre.so extension=xml.so extension=iconv.so extension=mbstring.so extension=sqlite.so > It's general problem with extensions loading order; it's mentioned > on main php site ( previous discussions contain links ). Yes -- and this is something that really needs to be addressed in the ports PHP framework, because if it's worthy enough for official PHP documentation on it, it'll continue to bite us until it's fixed. Each PHP port could have a priority number associated with it, the end result being that you sort the extensions loaded in order of the priority number when making/changing extensions.ini. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networkinghttp://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: [py-transports] freebsd current No module named xish.domish again
PyAIMt 0.8 should fix this. (it uses the same twistfix library that PyMSNt uses) Daniel On Dec 8, 2006, at 8:31 PM, Randy Bush wrote: # /usr/local/etc/rc.d/jabber-pyaim-transport start Starting jabber_pyaim. Could not find the XML DOM. If you're using Twisted 2.x make sure you have twisted.words installed. Traceback (most recent call last): File "/usr/local/lib/jabber/pyaim/PyAIMt.py", line 11, in ? import main File "/usr/local/lib/jabber/pyaim/src/main.py", line 4, in ? import utils File "/usr/local/lib/jabber/pyaim/src/utils.py", line 12, in ? from tlib.twistwrap import Element, SuxElementStream File "/usr/local/lib/jabber/pyaim/src/tlib/twistwrap.py", line 68, in ? from twisted.xish.domish import SuxElementStream, Element, unescapeFromXml, elementStream ImportError: No module named xish.domish and last times fixes don't do it this time :( randy ___ py-transports mailing list py-transports@blathersource.org http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg-nestserver won't build on 4.11, says stdint.h missing
On Fri, Dec 08, 2006 at 08:32:47PM -0500, Steven Friedrich wrote: > On Friday 08 December 2006 19:27, Kris Kennaway wrote: > > On Fri, Dec 08, 2006 at 07:19:27PM -0500, Steven Friedrich wrote: > > > I've been having a really weird video problem on my two machines when > > > running 4.11. My 4.11 machines run XFree86 4.5.0 > > > > > > I have a dual-head setup I've been using for a few years. Recently, the > > > left monitor looks like it has a vertical sync problem, but I'm pretty > > > sure it's not the video hardware, because only host "lightning" have the > > > problem until today. Now "daemon" also has it. I can pull the drives > > > out (mobile racks) and put FreeBSD 6.1 in and these don't have the > > > problem. > > > > > > So I thought I'd switch to xorg. But when I try to build xorg-nestserver > > > or xorg-server, the build breaks complaining that stdint.h doesn't exist. > > > > > > Can anyone confirm that these ports will build under 4.11? > > > > It's possible you're the first person to try it. You really should > > try to migrate off of 4.x, maintainers are not required to support it > > and all support will soon be terminated. > > > > Kris > oki doki. > > From perusing the web site, I can see that I have to upgrade thru the 5.x > series first, if I do a source upgrade. If I do a binary upgrade, I can go > straight to 6.1, right? > > Opps, I've been reading the Install notes for 5.x and I can't do a binary > pgrade from 4.x. It's possible to do a binary upgrade to 6.1 (or 6.2-rc1 if you want extra bug fixes), with some extra steps. Make sure you install the source tree, then do cd /usr/src make delete-old to delete old files which can cause problems for later builds (this is what the 5.5 install notes warn about). Then you will need to upgrade your /etc using mergemaster (see the docs). You'd have to do both of these steps anyway if you were doing a source upgrade, so you've still saved yourself the time and effort. Kris pgpZ9tT35h7HT.pgp Description: PGP signature
RE: xorg-nestserver won't build on 4.11, says stdint.h missing
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steven > Friedrich > Sent: Friday, December 08, 2006 6:19 PM > To: freebsd-ports@FreeBSD.org > Subject: xorg-nestserver won't build on 4.11, says stdint.h missing > > I've been having a really weird video problem on my two machines when running > 4.11. My 4.11 machines run XFree86 4.5.0 > > I have a dual-head setup I've been using for a few years. Recently, the left > monitor looks like it has a vertical sync problem, but I'm pretty sure it's > not the video hardware, because only host "lightning" have the problem until > today. Now "daemon" also has it. I can pull the drives out (mobile racks) > and put FreeBSD 6.1 in and these don't have the problem. > > So I thought I'd switch to xorg. But when I try to build xorg-nestserver or > xorg-server, the build breaks complaining that stdint.h doesn't exist. > > Can anyone confirm that these ports will build under 4.11? > [Bill Milford] I submitted a PR with a patch for this a long time ago. ports/102868 It hasn't been committed. I have since stop running X on my 4.11 server as I am preparing to move to a 6.1 server soon. Bill ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
