Build of firefox from ports does not finish
It ends with the following: gmake[5]: Leaving directory `/usr/ports/www/firefox/work/mozilla-release/browser/app/profile/extensions' gmake[4]: Leaving directory `/usr/ports/www/firefox/work/mozilla-release/browser/app' gmake[3]: Leaving directory `/usr/ports/www/firefox/work/mozilla-release/browser' gmake[2]: Leaving directory `/usr/ports/www/firefox/work/mozilla-release' gmake[1]: Leaving directory `/usr/ports/www/firefox/work/mozilla-release' if test -d ./dist/bin ; then touch ./dist/bin/.purgecaches ; fi hg: not found sed: /usr/ports/www/firefox/work/mozilla-release/build/unix/*.pc: No such file or directory Any ideas as to what is 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: unbroken dev/icu in current
On 07/03/12 20:35, Ruslan Mahmatkhanov wrote: Chris Rees wrote on 03.07.2012 22:22: On 3 July 2012 12:51, Rodrigo OSORIO wrote: Hi, The port dev/icu fails to build in current due to an lock issue caused by the use of threads api. Disabling threads for icu in current solves the problem and the port can be build successfully and AFAIK this unbroke some of the ports who depends on icu. I don't know if this can be an acceptable short-term workaround for this por ? I've been reliably informed that icu builds just fine on CURRENT from 1/July. I'll update my Tinderbox and let you know. Chris Can confirm that it builds without an issue on r237936 (Sun Jul 1 19:07:45 2012) with default option set (threads enabled). Chris, That's excellent ! I didn't sync my svn last week. Hope this fix in current unbroken most of the ports in "run away" state. Regards - rodrigo ___ 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: unbroken dev/icu in current
On 3 July 2012 20:20, Ruslan Mahmatkhanov wrote: > Chris Rees wrote on 03.07.2012 22:53: > >> On 3 July 2012 19:35, Ruslan Mahmatkhanov wrote: >>> >>> Chris Rees wrote on 03.07.2012 22:22: >>> On 3 July 2012 12:51, Rodrigo OSORIO wrote: > > > > Hi, > > The port dev/icu fails to build in current due to an lock issue > caused by the use of threads api. > Disabling threads for icu in current solves the problem and the port > can be build successfully and AFAIK this unbroke some of the ports who > depends on icu. > > I don't know if this can be an acceptable short-term workaround for > this > por ? I've been reliably informed that icu builds just fine on CURRENT from 1/July. I'll update my Tinderbox and let you know. Chris >>> >>> >>> >>> Can confirm that it builds without an issue on r237936 (Sun Jul 1 >>> 19:07:45 >>> 2012) with default option set (threads enabled). >>> >> >> Great now I need to find an appropriate OSVERSION for marking >> BROKEN on; I'm tempted to start with 100 and end with 114; if >> no-one yells at me I'll commit it in an hour or so. >> >> Chris > > > Why to not just ask Rodrigo to update? I think this BROKEN is only needed if > icu doesn't builds on a system, that was installed from official FreeBSD > -current snapshot. If memory serves me well there is many extra cautions in > docs that using -current, csuped in wrong time, may produce various > problems, so "It's a -current, babe" should sound reasonable, I believe. > Is there any extra info (error logs), or was you able to reproduce it on > some of your -current system? > Rodrigo, can you please update your system and check if problem is gone? Sure, but many of us with Tinderboxes would be thankful for the hint, and I'm sure the pointyhatters would like the lack of errorlog until they update the jails. It can stay in temporarily for a short while, at least Chris ___ 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: unbroken dev/icu in current
Chris Rees wrote on 03.07.2012 22:53: On 3 July 2012 19:35, Ruslan Mahmatkhanov wrote: Chris Rees wrote on 03.07.2012 22:22: On 3 July 2012 12:51, Rodrigo OSORIO wrote: Hi, The port dev/icu fails to build in current due to an lock issue caused by the use of threads api. Disabling threads for icu in current solves the problem and the port can be build successfully and AFAIK this unbroke some of the ports who depends on icu. I don't know if this can be an acceptable short-term workaround for this por ? I've been reliably informed that icu builds just fine on CURRENT from 1/July. I'll update my Tinderbox and let you know. Chris Can confirm that it builds without an issue on r237936 (Sun Jul 1 19:07:45 2012) with default option set (threads enabled). Great now I need to find an appropriate OSVERSION for marking BROKEN on; I'm tempted to start with 100 and end with 114; if no-one yells at me I'll commit it in an hour or so. Chris Why to not just ask Rodrigo to update? I think this BROKEN is only needed if icu doesn't builds on a system, that was installed from official FreeBSD -current snapshot. If memory serves me well there is many extra cautions in docs that using -current, csuped in wrong time, may produce various problems, so "It's a -current, babe" should sound reasonable, I believe. Is there any extra info (error logs), or was you able to reproduce it on some of your -current system? Rodrigo, can you please update your system and check if problem is gone? -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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"
Upgrading Base System openssl
One of my clients needs to upgrade OpenSSL on their FreeBSD 8.3 systems to the latest version. This is easily accomplished using the port. However: They do not want a 2nd installation of OponSSL under /usr/local, they want to totally replace the existing base system version. There are some ports such as mail/sendmail that work that way, and others such as security/openssh-portable that have a config option [OVERWRITE_BASE] for this purpose. Is there a reason why the OpenSSL port does not have the ability to replace the base system version? is there an obvious way to do this that i am missing? and finally, if i were to submit patches adding an OVERWRITE_BASE option to the port, would someone be willing to commit them? thanks, tom ___ 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: unbroken dev/icu in current
On 3 July 2012 19:35, Ruslan Mahmatkhanov wrote: > Chris Rees wrote on 03.07.2012 22:22: > >> On 3 July 2012 12:51, Rodrigo OSORIO wrote: >>> >>> >>> Hi, >>> >>> The port dev/icu fails to build in current due to an lock issue >>> caused by the use of threads api. >>> Disabling threads for icu in current solves the problem and the port >>> can be build successfully and AFAIK this unbroke some of the ports who >>> depends on icu. >>> >>> I don't know if this can be an acceptable short-term workaround for this >>> por ? >> >> >> I've been reliably informed that icu builds just fine on CURRENT from >> 1/July. I'll update my Tinderbox and let you know. >> >> Chris > > > Can confirm that it builds without an issue on r237936 (Sun Jul 1 19:07:45 > 2012) with default option set (threads enabled). > Great now I need to find an appropriate OSVERSION for marking BROKEN on; I'm tempted to start with 100 and end with 114; if no-one yells at me I'll commit it in an hour or so. Chris ___ 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: unbroken dev/icu in current
Chris Rees wrote on 03.07.2012 22:22: On 3 July 2012 12:51, Rodrigo OSORIO wrote: Hi, The port dev/icu fails to build in current due to an lock issue caused by the use of threads api. Disabling threads for icu in current solves the problem and the port can be build successfully and AFAIK this unbroke some of the ports who depends on icu. I don't know if this can be an acceptable short-term workaround for this por ? I've been reliably informed that icu builds just fine on CURRENT from 1/July. I'll update my Tinderbox and let you know. Chris Can confirm that it builds without an issue on r237936 (Sun Jul 1 19:07:45 2012) with default option set (threads enabled). -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: unbroken dev/icu in current
On 3 July 2012 12:51, Rodrigo OSORIO wrote: > > Hi, > > The port dev/icu fails to build in current due to an lock issue > caused by the use of threads api. > Disabling threads for icu in current solves the problem and the port > can be build successfully and AFAIK this unbroke some of the ports who > depends on icu. > > I don't know if this can be an acceptable short-term workaround for this > por ? I've been reliably informed that icu builds just fine on CURRENT from 1/July. I'll update my Tinderbox and let you know. Chris ___ 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: KDE 4 hangs at splash screen when using KMS enabled 10-CURRENT
Hi, On Tuesday, July 03, 2012 02:09:08 AM Nikolay Tychina wrote: > 2012/7/2 Erich Dollansky : > > On Monday, July 02, 2012 04:32:41 PM Nikolay Tychina wrote: > >> > FreeBSD X220.ovitrap.com 10.0-CURRENT FreeBSD 10.0-CURRENT #9: Sun Jul > >> > 1 15:34:52 WIT 2012 > >> > >> Could you please backup ~/.kde4 and start it once again? > >> My system seems to be quite the same as yours but KDE behaves differently. > > > > I moved .kde4 out of the way, edited .xinitrc and came to the same result. > > The only difference was that KDE did some 'migration' and was real slow > > coming up. > > > > Stupid question. When did you compile the ports the last time? Could it be > > that your KDE is a bit too old? > > > > My installation is pretty fresh as I just replaced the hard disk. > > => I compiled fresh CURRENT and fresh ports right after, all this appox. > the day before I mailed first message. > BTW, CPU is Intel Celeron G530 and maybe that's relevant. Will do some > googling about it. > this makes a real difference. The Celeron should not have the GPU integrated. You have to find out now where the GPU is and of what type it is. Some are supported by KMS, others are not supported. Still, you said before that the other window managers start properly. So, your problem should not be related to hardware. I also have now no real idea what could be the cause of the problem. Erich ___ 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"
European court allows software licence resale, & blocks PD capture ?
Hi s...@guug.de & po...@freebsd.org I set Reply-To: "Julian H. Stacey" To avoid cross posts between: Responders in German wanting s...@guug.de http://lists.guug.de/pipermail/sage/ Responders in English wanting po...@freebsd.org http://lists.freebsd.org/pipermail/freebsd-ports/ + Bcc'd: ( Melanie, Michael E, David H, Norbert & Gary, mecc@, Bevi @Or., Polyt. ) German below - Deutsch Unten. Just for interest: Here is a European court judgment: REFERENCE for a preliminary ruling under Article 267 TFEU from the Bundesgerichtshof (Germany), made by decision of 3 February 2011, received at the Court on 14 March 2011, in the proceedings UsedSoft GmbH v Oracle International Corp., German http://curia.europa.eu/juris/document/document.jsf?text=&docid=124564&pageIndex=0&doclang=de&mode=req&dir=&occ=first&part=1&cid=5204011 English http://curia.europa.eu/juris/document/document.jsf?text=&docid=124564&pageIndex=0&doclang=en&mode=req&dir=&occ=first&part=1&cid=5204011 My Summary ( IANAL = I Am Not A Lawyer ): Sofware licenses _Can_ be legaly resold. Judgement also seem to block a few ex- public domain authors who occasionaly try to claw back public domain software (inc. old versions!) to become their closed source. ( Some ports occasionaly removed from http://www.Freebsd.org/ports/ inc. one recently) -Original Message- From: Informationskanal zu aktuellen Entwicklungen im Informations- und Medienrecht [mailto:infola...@listserv.dfn.de] On Behalf Of Prof. Dr. Thomas Hoeren Sent: Dienstag, 3. Juli 2012 13:06 To: infola...@listserv.dfn.de Subject: [INFOLAW-L] EuGH: Online-Erschöpfung J - nach 30 Jahren Streit endlich das richtige Urteil in Sachen Online-Erschöpfung! EuGH, Urteil vom 3. Juli 2012 - Rechtssache C-128/11 EuGH erlaubt Weiterverkauf von gebrauchten Software-Lizenzen auch im Falle eines Onlinerewerbs. Das Recht auf ausschließliche Verbreitung der Programmkopien erschöpfe sich mit dem Erstverkauf. Stelle ein Konzern seinem Kunden eine Kopie zur Verfügung und erlaube ihm über einen Lizenzvertrag das unbefristete Nutzungsrecht dieser Kopie, so erlische sein Recht auf ausschließliche Verbreitung. Durch ein solches Geschäft werde nämlich das Eigentum an dieser Kopie übertragen Dem Weiterverkauf der Kopie könne er sich dann nicht mehr widersetzen. Das gelte auch für verbesserte und aktualisierte Fassungen - weil sie Bestandteil der Kopie seien. .. http://curia.europa.eu/juris/document/document.jsf?text=&docid=124564&pageIndex=0&doclang=de&mode=req&dir=&occ=first&part=1&cid=5204011 - -- Prof. Dr. Thomas Hoeren Institut für Informations-, Telekommunikations- und Medienrecht Leonardo-Campus 9 D-48149 Münster Tel.: +49/251/8338600 Fax: +49/251/8338601 http://www.uni-muenster.de/Jura.itm/Hoeren ** INFOLAW-L Informationskanal zu aktuellen Entwicklungen im Informations- und Medienrecht Abmelden durch Mail an infolaw-l-signoff-requ...@listserv.dfn.de Administrative Fragen oder Probleme an infolaw-l-requ...@listserv.dfn.de Archiv unter http://www.listserv.dfn.de/archives/infolaw-l.html Ergaenzende Materialien unter http://www.uni-muenster.de/Jura.itm/hoeren/ ** --- End of Forwarded Message Cheers, Julian -- Julian Stacey, Unix since 1978, Consultant '85, BSD Linux C Sys. Eng. Munich Reply below not above, like a play script. Indent old text with "> ". Send plain text. Not: HTML, multipart/alternative, base64, quoted-printable. Mail from @yahoo dumped @berklix. http://berklix.org/yahoo/ ___ 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: make failed for editors/libreoffice
On 2012-07-02 10:23, Leslie Jensen wrote: ... > Assertion failed: (EST != EST_Delayed && EST != EST_Uninstantiated), > function isNothrow, file > /usr/ports/lang/clang/work/llvm-3.1.src/tools/clang/lib/CodeGen/../../include/clang/AST/Type.h, > > line 2873. ... > clang: note: diagnostic msg: Preprocessed source(s) and associated run > script(s) are located at: > clang: note: diagnostic msg: /tmp/null_canvascustomsprite-TmaoHV.ii > clang: note: diagnostic msg: /tmp/null_canvascustomsprite-TmaoHV.sh ... > clang: note: diagnostic msg: Preprocessed source(s) and associated run > script(s) are located at: > clang: note: diagnostic msg: /tmp/null_canvasbitmap-m0BlpL.ii > clang: note: diagnostic msg: /tmp/null_canvasbitmap-m0BlpL.sh Can you please mail me the .ii and .sh files that are mentioned above? E.g. these files: /tmp/null_canvascustomsprite-TmaoHV.ii /tmp/null_canvascustomsprite-TmaoHV.sh /tmp/null_canvasbitmap-m0BlpL.ii /tmp/null_canvasbitmap-m0BlpL.sh Also, is this on i386 or amd64, and are you on -CURRENT or -STABLE? ___ 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: make failed for editors/libreoffice
On FreeBSD 9.0 Release I built without problems with Clang 3.0 On Tue, Jul 3, 2012 at 5:45 AM, Boris Samorodov wrote: > Hi All, > > 02.07.2012 12:23, Leslie Jensen пишет: > >> internal build errors: >> >> ERROR: error 65280 occurred while making >> /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.4.2/canvas/prj >> >> it seems that the error is inside 'canvas' >> > > I've got the same error at FreeBSD-CURRENT and latest ports tree with > base clang and clang/llvm from ports. > > -- > WBR, Boris Samorodov (bsam) > FreeBSD Committer, http://www.FreeBSD.org The Power To Serve > > > ___ > 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-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
unbroken dev/icu in current
Hi, The port dev/icu fails to build in current due to an lock issue caused by the use of threads api. Disabling threads for icu in current solves the problem and the port can be build successfully and AFAIK this unbroke some of the ports who depends on icu. I don't know if this can be an acceptable short-term workaround for this por ? Regards, - rodrigo ___ 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: make failed for editors/libreoffice
Hi All, 02.07.2012 12:23, Leslie Jensen пишет: internal build errors: ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.4.2/canvas/prj it seems that the error is inside 'canvas' I've got the same error at FreeBSD-CURRENT and latest ports tree with base clang and clang/llvm from ports. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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"
