Re: [kde-freebsd] gettext error
Ok folks, gettext-0.16.1_1 is now in the tree, with --disable-threads. Thank you all for you input. -aDe ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] gettext error
On 2007-Apr-07 06:38:12 -0700, FreeBSD WickerBill <[EMAIL PROTECTED]> wrote: >Whatever the final decision, if it entails another 'world-wide compiler >thrash test' then please advise in UPDATING to run the portupgrade with the >--batch flag so people don't wind up baby sitting their consoles ;-) Note that '--batch' is not a total panacea. I've been bitten in the past by batch updates breaking my system when I lost config options that I needed (php5 defaults to not building the Apache plugin). -- Peter Jeremy pgpQ4sPJCe79K.pgp Description: PGP signature ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] gettext error
Andy Fawcett wrote: > On Saturday 07 April 2007 11:32:19 Ade Lovett wrote: >> On Apr 06, 2007, at 23:44 , Joe Marcus Clarke wrote: >> > Well, I've already expressed my opinion that threading be disabled. >> > Since FreeBSD doesn't allow mixing threaded libraries with non- >> > threaded >> > executables (without linking the executable with PTHREAD_LIBS) :-(, >> > threading is just dangerous. I don't think we want to force all ports >> > that link to libintl to become thread-aware. >> >> Yup. I think this is the way to go myself. I'd just like consensus >> from the KDE folks before I simply bump PORTREVISION and add -- >> disable-threads to CONFIGURE_ARGS. > > Sounds fine to me too. We've not had it threaded before, so not missed it > either. > > Unless lofi has some strong objection to this, consider this an ok from > kde@ Ok from me as well. FWIW, we'd probably be fine either way, since everything that links to qt already needs to link to a threads library. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] gettext error
On 4/7/07, Ade Lovett <[EMAIL PROTECTED]> wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Apr 06, 2007, at 23:44 , Joe Marcus Clarke wrote: > Well, I've already expressed my opinion that threading be disabled. > Since FreeBSD doesn't allow mixing threaded libraries with non- > threaded > executables (without linking the executable with PTHREAD_LIBS) :-(, > threading is just dangerous. I don't think we want to force all ports > that link to libintl to become thread-aware. Yup. I think this is the way to go myself. I'd just like consensus from the KDE folks before I simply bump PORTREVISION and add -- disable-threads to CONFIGURE_ARGS. Whatever the final decision, if it entails another 'world-wide compiler thrash test' then please advise in UPDATING to run the portupgrade with the --batch flag so people don't wind up baby sitting their consoles ;-) Thanks... -- --I'm not 'renting' my OS-- ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] gettext error
On Saturday 07 April 2007 11:32:19 Ade Lovett wrote: > On Apr 06, 2007, at 23:44 , Joe Marcus Clarke wrote: > > Well, I've already expressed my opinion that threading be disabled. > > Since FreeBSD doesn't allow mixing threaded libraries with non- > > threaded > > executables (without linking the executable with PTHREAD_LIBS) :-(, > > threading is just dangerous. I don't think we want to force all ports > > that link to libintl to become thread-aware. > > Yup. I think this is the way to go myself. I'd just like consensus > from the KDE folks before I simply bump PORTREVISION and add -- > disable-threads to CONFIGURE_ARGS. Sounds fine to me too. We've not had it threaded before, so not missed it either. Unless lofi has some strong objection to this, consider this an ok from kde@ Andy -- Andy Fawcett | [EMAIL PROTECTED] | [EMAIL PROTECTED] "In an open world without walls and fences, | [EMAIL PROTECTED] we wouldn't need Windows and Gates." -- anon | [EMAIL PROTECTED] ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] gettext error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Apr 06, 2007, at 23:44 , Joe Marcus Clarke wrote: > Well, I've already expressed my opinion that threading be disabled. > Since FreeBSD doesn't allow mixing threaded libraries with non- > threaded > executables (without linking the executable with PTHREAD_LIBS) :-(, > threading is just dangerous. I don't think we want to force all ports > that link to libintl to become thread-aware. Yup. I think this is the way to go myself. I'd just like consensus from the KDE folks before I simply bump PORTREVISION and add -- disable-threads to CONFIGURE_ARGS. - -aDe -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFGF1cUpXS8U0IvffwRAm9HAJ9uSipqISopth6GtvEbJqasS4BL4ACglqpI lcBVf2O0KvO+pokdwcJpamo= =fJPo -END PGP SIGNATURE- ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] gettext error
On Apr 06, 2007, at 22:52 , Vijay Patel ((NewsLetters)) wrote: > Hello, > > I was also facing similar problem. & As per discussion of this > thread, its because, I am using FreeBSD 5.2 with latest > ports.tar.gz (As I am at remote location, FreeBSD upgrade is not > possible for me). > Here is how I solved problem of gettext. Here's the background. gettext-0.16.1 is now threads aware. In its current form, the port is indeed slightly broken, something that didn't come up during build and gnome-devel testing, and nork@ has kindly provided me with a patch. However, I have received isolated reports that the threaded-gettext is causing edge case issues with other ports. So, I am faced with something of a dilemma, since PORTREVISION will be bumped in either case (yes folks, y'all get to rebuild stuff, consider it a worldwide thrash-test of compilers ;) 1. Make devel/gettext respect PTHREAD_LIBS, and leave the threading in place 2. Disable threading entirely I'm open to either option here, and have taken the liberty of cc'ing the GNOME and KDE folks since they're very large consumers. -aDe ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] gettext error
On Fri, 2007-04-06 at 23:38 -0700, Ade Lovett wrote: > On Apr 06, 2007, at 22:52 , Vijay Patel ((NewsLetters)) wrote: > > > Hello, > > > > I was also facing similar problem. & As per discussion of this > > thread, its because, I am using FreeBSD 5.2 with latest > > ports.tar.gz (As I am at remote location, FreeBSD upgrade is not > > possible for me). > > Here is how I solved problem of gettext. > > Here's the background. > > gettext-0.16.1 is now threads aware. In its current form, the port > is indeed slightly broken, something that didn't come up during build > and gnome-devel testing, and nork@ has kindly provided me with a patch. > > However, I have received isolated reports that the threaded-gettext > is causing edge case issues with other ports. > > So, I am faced with something of a dilemma, since PORTREVISION will > be bumped in either case (yes folks, y'all get to rebuild stuff, > consider it a worldwide thrash-test of compilers ;) A PORTREVISION bump will not require users to rebuild everything. Portupgrade, portmaster, etc. will just rebuild gettext, and update dependencies accordingly. Tinderboxes and pointyhat, on the other hand, will have to rebuild all dependent ports. > > 1. Make devel/gettext respect PTHREAD_LIBS, and leave the threading > in place > 2. Disable threading entirely > > I'm open to either option here, and have taken the liberty of cc'ing > the GNOME and KDE folks since they're very large consumers. Well, I've already expressed my opinion that threading be disabled. Since FreeBSD doesn't allow mixing threaded libraries with non-threaded executables (without linking the executable with PTHREAD_LIBS) :-(, threading is just dangerous. I don't think we want to force all ports that link to libintl to become thread-aware. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
