Re: Does building linux packages under poudriere require linux compatibility emulation?
14.01.2017, 12:18, "René Ladan" : > Op 14 jan. 2017 01:07 schreef "Mark Martinec" > : > > When building packages under poudriere on 11.0-RELEASE-p7 (from a command > line in a terminal window) I'm noticing occasional streams of diagnostic: > > ELF binary type "3" not known. > > which seem to be related to building some linux packages (example below, > parallel builds). Poudriere still reports success for these builds. > > The host where poudriere is running does not have linux.ko loaded. > > Does building such packages really require linuxilator configured > on the build host ??? For example, your log includes building qdoc3. It is likely to be used in build process of other Qt packages. > > Mark > > I rhink the host wouldn't need the linuxolator for building the Linux > packages, unless those packages run other Linux packages for their build. > > René > > [00:23:56] >> [02][00:00:00] Starting build of www/linux-c6-qt47-webkit > [00:23:57] >> [13][00:00:00] Starting build of textproc/linux-c6-libxml2 > ELF binary type "3" not known. > ELF binary type "3" not known. > [00:24:09] >> [19][00:00:28] Finished build of > textproc/linux-c6-aspell: Success > [00:24:11] >> [19][00:00:00] Starting build of devel/qt4-makeqpf > [00:24:11] >> [11][00:00:24] Finished build of > security/linux-c6-openssl-compat: Success > ELF binary type "3" not known. > ELF binary type "3" not known. > ELF binary type "3" not known. > ELF binary type "3" not known. > ELF binary type "3" not known. > [00:24:12] >> [11][00:00:00] Starting build of x11-toolkits/vte > ELF binary type "3" not known. > ELF binary type "3" not known. > ELF binary type "3" not known. > ELF binary type "3" not known. > [00:24:16] >> [07][00:00:24] Finished build of > graphics/linux-c6-glx-utils: Success > ELF binary type "3" not known. > ELF binary type "3" not known. > ELF binary type "3" not known. > [00:24:17] >> [07][00:00:00] Starting build of devel/qt4-qdoc3 > ELF binary type "3" not known. > ELF binary type "3" not known. > [00:24:19] >> [13][00:00:22] Finished build of > textproc/linux-c6-libxml2: Success > [00:24:19] >> [13][00:00:00] Starting build of graphics/goocanvas > [00:24:27] >> [10][00:02:26] Finished build of graphics/sdl_gfx: Success > [00:24:29] >> [10][00:00:00] Starting build of multimedia/mjpegtools > [00:24:34] >> [04][00:02:15] Finished build of devel/linux-c6-devtools: > Success > [00:24:35] >> [04][00:00:00] Starting build of > devel/linux-c6-ncurses-base > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Regards, Konstantin ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Optimising generated rules for SAT solving (5/12 are duplicates)
23.11.2016, 19:42, "Hans Petter Selasky" : > On 11/23/16 17:27, Ed Schouten wrote: >> Hi Hans, >> >> 2016-11-23 15:27 GMT+01:00 Hans Petter Selasky : >>> I've made a patch to hopefully optimise SAT solving in our pkg utility. >> >> Nice! Do you by any chance have any numbers that show the performance >> improvements made by this change? > > Hi Ed, > > I tried measuring with "time", but figured out that it was doing a lot > of other stuff too. Isolating this piece of code was not so easy. > > > Assuming that the SAT solver of >> pkg(1) uses an algorithm similar to DPLL[1], a change like this would >> affect performance linearly. My guess is therefore that the running >> time is reduced by approximately 5/12. Is this correct? >> >> By the way, why attach a zip file with a diff? GitHub's pull requests >> are awesome! :-) > > GitHub wouldn't allow me to make a .diff attachment. If you really want to be nasty and not submit your change as a pull request, GitHub allows you to paste your patch as a comment: ```diff ``` > >> [1] Davis-Putnam-Logemann-Loveland algorithm: >> https://en.wikipedia.org/wiki/DPLL_algorithm > > --HPS > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Regards, Konstantin ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Patch for premake 4.4 beta 5 from premake 4
CC'ing premake developers.
24.06.2014, 18:09, "Vitaly Magerya" :
> TL;DR: could a brave ports comitter apply an update for
> devel/premake4 at [1]? That would be much appreciated.
>
> Redports logs for this update are at [2].
>
> Note that redports for some reason doesn't invoke regression-test
> target today; probably a bug on their part.
>
> On 2014-06-24 09:51, Sergei G wrote:
>> I had to update Premake 4 port (4.3) to 4.4 beta 5 on FreeBSD
>> 10.0-RELEASE #0.
>>
>> I included patch file with changes applied to Premake 4 port. The
>> changes consist of:
>>
>> 3 regression tests failed (it appears due to at least one missing patch
>> file):
> The main cause of these regressions is actually a very strange
> one (and you're right that those patches are what fixed it in
> the past). So, in one of it's routines premake tries to open
> '/etc/ld.so.conf'; it does so via Lua function 'io.open'. Now,
> FreeBSD doesn't have that file, and in theory 'io.open' should
> return 'nil', which should cause premake to skip this file. What
> actually happens is that 'io.open' returns some object that is
> neither nil, nor a proper file object. Premake thinks that 'io.open'
> succeeded, and tries to read from that non-nil, non-file object,
> which doesn't work.
>
> Why doesn't 'io.open' return 'nil' here is a mystery to me. Maybe
> premake ships with buggy Lua sources. I don't know.
>
> In any case, this problem is fixed in the patch at [1].
>> Once I installed premake I observed that it generated Makefile with gcc
>> in it, instead of clang. Should switch to clang be applied at premake or
>> Box2D project level?
> It appears that Premake only supports GCC for its "gmake" target.
>
> It is possible to simply replace "gcc" with "clang" in the premake
> sources, and it will mostly work, but:
> 1) it will not work for projects that use advanced options, since
> clang does not support, and in fact fails on some of the flags
> premake may pass to it ("-ffast-math" for example);
> 2) makefiles generated on FreeBSD will fail on other platforms
> (not sure if premake promises them to work though).
>
> The long-term solution for premake is to recognize "clang" as a
> valid compiler, and provide a set of flags it understands.
>
> The short-term solution for programs that use premake is to either
> require GCC from ports, or to manually replace "gcc" with "clang"
> before building, patching out incompatible compiler flags, if any.
>
> Note that Box2D v2.3.1 doesn't seem to use any flags that clang
> doesn't understand, so it is safe to change "gcc" into "cc", and
> "g++" into "c++" in the makefiles that premake generates for it.
>
> [1] http://tx97.net/~magv/diff/premake-4.4.b5.diff
> [2] https://redports.org/buildarchive/20140624134401-54287/
> ___
> 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"
--
Regards, Konstantin
___
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: any javascript browser works on sparc64?
19.06.2014, 12:26, "Anton Shterenlikht" : > I had to switch to sparc64 for my X clients. > www/firefox is blocked by multimedia/libvpx. > > Can anybody recommend a working web browser with > javascript? > It should be possible to build Firefox without libvpx which is needed only to decode WebM HTML5 video (I guess you can get along with it on sparc64 :) So I would try to hack port (or maybe even Firefox source if there is no appropriate configure option - there shouldn't be a lot of places in code where libvpx is used) Alternatively, you can try Konqueror, but it's JS support is somewhat outdated. Maybe something WebKit-based will also work for you (but not Chromium!) -- Regards, Konstantin ___ 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: [CFT/HEADSUP] Ports now have Stack Protector support
22.09.2013, 19:48, "Eitan Adler" : > On Sun, Sep 22, 2013 at 10:01 AM, Konstantin Tokarev > wrote: > >> 21.09.2013, 18:26, "Nathan Whitehorn" : >>> On 09/21/13 09:09, Bryan Drewery wrote: >>>> On 9/21/2013 9:00 AM, Nathan Whitehorn wrote: >>>>> On 09/21/13 05:47, Bryan Drewery wrote: >>>>>> Ports now support enabling Stack Protector [1] support on FreeBSD 10 >>>>>> i386 and amd64, and older releases on amd64 only currently. >>>>> Why only those architectures? >>>>> -Nathan >>>> I was only able to test on amd64 and i386. And that took 37 exp-runs >>>> over a month. >>>> >>>> See commit and CHANGES for more discussion on why not i386 on <10: >>>> >>>> http://svnweb.freebsd.org/ports?view=revision&revision=327697 >>> OK. If I set this on powerpc anyway, will it turn on? I'm happy to >>> (slowly) test it there. >> AFAIU, it's pointless to use stack protector on ppc because stack smashing >> attacks are just impossible here. > > Could you explain why? Oops, I was wrong. It's impossible to overwrite return address directly by smashing stack (because it's kept in register), but other techniques exist. -- Regards, Konstantin ___ 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: [CFT/HEADSUP] Ports now have Stack Protector support
21.09.2013, 18:26, "Nathan Whitehorn" : > On 09/21/13 09:09, Bryan Drewery wrote: > >> On 9/21/2013 9:00 AM, Nathan Whitehorn wrote: >>> On 09/21/13 05:47, Bryan Drewery wrote: Ports now support enabling Stack Protector [1] support on FreeBSD 10 i386 and amd64, and older releases on amd64 only currently. >>> Why only those architectures? >>> -Nathan >> I was only able to test on amd64 and i386. And that took 37 exp-runs >> over a month. >> >> See commit and CHANGES for more discussion on why not i386 on <10: >> >> http://svnweb.freebsd.org/ports?view=revision&revision=327697 > > OK. If I set this on powerpc anyway, will it turn on? I'm happy to > (slowly) test it there. AFAIU, it's pointless to use stack protector on ppc because stack smashing attacks are just impossible here. -- Regards, Konstantin ___ 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: [HEADSUP][CFT] New compiler USES flag, please test, review comment
13.09.2013, 19:04, "Pietro Cerutti" : > On 2013-Sep-13, 15:17, Baptiste Daroussin wrote: > >> USES= compiler:c++11 >> >> Means you need a c++1 capable compiler but not necessary a c++ 11 aware >> standard >> library, in that case if the base compiler is not able to support c++11 >> clang33 >> will be used from ports otherwise gcc 4.6+ if you specify it in make.conf. >> >> USES= compiler=stdc++11 >> >> You need a c++11 aware stdlibrary, if the base compiler doesn't have it >> then gcc >> 4.6+ will be used. > > Very nice! I suggest to change these last two names in > > c++11-lang > c++11-lib > > since 'stdc++11' sounds too much like libstdc++ for me (implying GNU's > implementation). Or like "standard C++11" vs "non-standard C++11". -- Regards, Konstantin ___ 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: gdb doesn't work well with qtcreator
09.08.2012, 15:50, "HU Dong" : > Hi,all! > I just installed devel/qtcreator from port. Everything seemed to > work fine except the debugger. At first I set it to /usr/bin/gdb, it > simply crashed when I started debugging, with a dialog reporting "The > gdb process crashed." Then I installed devel/gdb and set the debugger > to /usr/local/bin/gdb, qtcreator reported that "Application process > could not be stopped:The program is not being run." and "Cannot > continue debugged process:The program is not being run." > I've spent much time searching on the internet, but found nothing > helpful. Did anyone run into the same problem? > > Env: FreeBSD 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 > 01:47:53 UTC 2012 > r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 Which version og gdb are you using? Qt Creator officially requires gdb >= 7.2, and may have issues with earlier versions. Maybe it's worthwhile to ask on qt-crea...@qt-project.org too. -- Regards, Konstantin ___ 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: port variants
13.04.2012, 23:55, "Chris Inacio" : > On Apr 13, 2012, at 3:39 PM, Freddie Cash wrote: > >> On Fri, Apr 13, 2012 at 12:04 PM, Chris Inacio wrote: >>> I was recently asked to do some FreeBSD ports support work. I mostly use a >>> Mac and the MacPorts system. MacPorts has the concept of a variant for a >>> port, but I can't find the analogue in the FreeBSD system. >>> >>> Does the FreeBSD ports system have the concept of a variant? If so, can >>> someone point me in the right direction on how to create one? >> Describing what a "variant" is, how it works in MacPorts, and what you >> are trying to do would help a lot. :) >> >> The closest guess I could make would be "slave port", but I don't >> think that works the same way. > > Sorry, you're right. > > For example, a port of say Emacs could have a variant of X11. > > So Emacs or Emacs+X11. > > The X11 variant would (somewhat obviously) include building regular Emacs but > also the X11 toolbar etc. while Emacs wouldn't include any X11 features (& > dependencies). > > On the Mac, we can build universal binaries (PowerPC, ia32, and x86_64), at > the cost of disk space. So we can build almost any package with the > +universal variant. > > Is that a reasonable explanation? Seems like you need makefile options: http://www.freebsd.org/doc/en/books/porters-handbook/makefile-options.html -- Regards, Konstantin ___ 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: KDE3 de facto EOL, Project Trinity?
09.10.2011, 22:30, "Jakub Lach": > Speaking of lightness, XFCE is memory hungry > these days and Linux centric, and Fluxbox is > not that light after all. Are you saying that Fluxbox is heavier than KDE3?? -- Regards, Konstantin ___ 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: devel/anjuta: creating project does not offer project's dialog.
01.07.2011, 11:49, "O. Hartmann" : > On 07/01/11 09:35, Konstantin Tokarev wrote: > >> 01.07.2011, 11:06, "O. Hartmann" >>> And, for those actively developing, is there a good alternative to >>> Anjuta (no KDevelop, since I do not like KDE and do not have KDE). Thanks, >>> Oliver >> Depending on what you need you can try: >> Geany >> Vim >> Eclipse >> Qt Creator >> >> Actually, KDevelop does not require you to run KDE, it just needs KDE >> libraries. > > Thanks for your fast response. > My target is mostly C, not C++, so I had my difficulties with QTCreator. If so, vim (with proper .vimrc + bunch of plugins) can be ideal IDE for you. -- Regards, Konstantin ___ 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: devel/anjuta: creating project does not offer project's dialog.
01.07.2011, 11:06, "O. Hartmann" > And, for those actively developing, is there a good alternative to > Anjuta (no KDevelop, since I do not like KDE and do not have KDE). Thanks, > Oliver Depending on what you need you can try: Geany Vim Eclipse Qt Creator Actually, KDevelop does not require you to run KDE, it just needs KDE libraries. -- Regards, Konstantin ___ 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: Best way to uninstall X
07.04.2011, 23:15, "David Demelier" : > On 07/04/2011 19:29, Konstantin Tokarev wrote: > >> 07.04.2011, 20:59, "Attos";: >>> Hello all, >>> >>> What is the best way to uninstall X and all the applications that run under >>> X? >>> >>> Thanks in advance. >> rm -rf /* > > This kind of answers can be avoided. WIll you argue it doesn't uninstall "X and all the applications that run under X?" :) BTW, it may be faster to install system from scratch in this case. -- Regards, Konstantin ___ 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: Best way to uninstall X
07.04.2011, 20:59, "Attos" : > Hello all, > > What is the best way to uninstall X and all the applications that run under > X? > > Thanks in advance. rm -rf /* -- Regards, Konstantin ___ 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: Compiling ports in a post-9.0-RELEASE world
17.03.2011, 20:33, "Matthias Andree" : > Not necessarily. If it's a documented extension that you'd allowed (and > even by sticking to the implicit gnu89 language default of GCC) then > you'll hardly hear back anything else than "invalid, works as documented". Note that Clang supports c89 and gnu89 modes[1] [1] http://clang.llvm.org/docs/UsersManual.html#c_modes -- Regards, Konstantin ___ 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: Compiling ports in a post-9.0-RELEASE world
17.03.2011, 15:39, "Konstantin Tokarev" : > 16.03.2011, 11:33, "Alberto Villa" ;: > >> On Wednesday 16 March 2011 09:15:07 Konstantin Tokarev wrote: >>> From http://clang.llvm.org/docs/LanguageExtensions.html >>> >>> "In addition to the language extensions listed here, Clang aims to >> support >>> a broad range of GCC extensions." >>> >>> So GCC extensions may also be considered as missing features. >> gcc-isms also means "bad code which is nonetheless supported by gcc" > > In this case don't hesitate to file a bug against gcc :) Let me elaborate my idea a bit. One may think that reporting bugs on GCC he supports development of technology that FreeBSD does not endorse [1]. I don't think so. 1) Latest versions of GCC are more standard-compliant than earlier ones, and bad written code tends to produce compilation errors with newer GCC. For example, I've seen lots of legacy code written for GCC 3.x but failing to compile with 4.x. 4.x branch is also being improved. 2) Active upstreams and Linux distributions try to make code compatible with latest and greatest GCC. So if newer version is fixed not to compile some kind of broken code, there will be big chances that upstreams will fix it themselves. 3) Projects with dead upstreams should be excluded from ports collection someday, unless maintainers are willing to do "upstream" job. Folks using this software will be able to build it using "right" GCC version which is known to compile this "crap" properly. And last but not least, GCC is still great compiler, despite of its drawbacks and licensing issues. [1] Bugs could be reported only for latest GCC version, i.e. 4.5.2, and 4.2.x will never get fixes. -- Regards, Konstantin ___ 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: Compiling ports in a post-9.0-RELEASE world
16.03.2011, 11:33, "Alberto Villa" : > On Wednesday 16 March 2011 09:15:07 Konstantin Tokarev wrote: > >> From http://clang.llvm.org/docs/LanguageExtensions.html >> >> "In addition to the language extensions listed here, Clang aims to > > support > >> a broad range of GCC extensions." >> >> So GCC extensions may also be considered as missing features. > > gcc-isms also means "bad code which is nonetheless supported by gcc" In this case don't hesitate to file a bug against gcc :) -- Regards, Konstantin ___ 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: Is it possible to install only some parts of libreoffice?
07.03.2011, 00:54, "Heino Tiedemann" : > Konstantin Tokarev ; wrote: > >> 03.03.2011, 03:27, "Charlie Kester" ;: >>> On Wed 02 Mar 2011 at 15:06:52 PST Charlie Kester wrote: >>>> I don't want or need all of the programs in the libreoffice suite. >>>> >>>> In fact, the only reason I might install it is to get the presentation >>>> program so I can work with PowerPoint files I occasionally download from >>>> the web. (There don't seem to be any workable, lighterweight >>>> alternatives, as there are for .doc and .xls files.) >>>> >>>> Would it be possible to provide some options to select which components >>>> to install? Or is the suite written in such a way that I have to >>>> install the whole thing in order to get one piece? >> It doesn't make much sense because all components of OOo/LibO are tightly >> integrated. > > I remember my debian GNU/Linux times some years ago: > > If i remember correcly there was the possibillity to install > Openoffice (what is the root of libreoffice) in peaces: Needed was a > "openoffice core" package and maybe another "openoffice lib" (or so) > package. After that you could install writer / base / calc and so on > seperatly... Right, but actually there's no much sense in it, because all components are just launchers for soffice.bin executable -- Regards, Konstantin ___ 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: Compiling ports in a post-9.0-RELEASE world
16.03.2011, 13:33, "Ade Lovett" : > On Mar 16, 2011, at 04:39 , Anton Shterenlikht wrote: > >> What will happen to ports in non-clang arches (sparc64, ia64) after 9.0R? > > With any luck, they will die a silent death and be pointed in the direction > of NetBSD that likes to look after irrelevant architectures. i386/amd64 for > primary use, arm/mips for embedded. Anything else is just ridiculous. What about Power Architecrure (formerly PowerPC)? It's widely used both for embedded and enterprise (pSeries, Blue Gene, etc.) -- Regards, Konstantin ___ 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: Compiling ports in a post-9.0-RELEASE world
16.03.2011, 02:27, "Alberto Villa" : > On Tuesday 15 March 2011 19:20:40 Konstantin Tokarev wrote: > >> 3. Fix Clang to compile more ports > > lots of problems are due to gcc-isms in software, so it's not always possible >From http://clang.llvm.org/docs/LanguageExtensions.html "In addition to the language extensions listed here, Clang aims to support a broad range of GCC extensions." So GCC extensions may also be considered as missing features. -- Regards, Konstantin ___ 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: Compiling ports in a post-9.0-RELEASE world
15.03.2011, 21:32, "Charlie Kester" : > On Tue 15 Mar 2011 at 11:20:40 PDT Konstantin Tokarev wrote: > >> 3. Fix Clang to compile more ports > > That would be my vote too, but we should probably focus on solutions the > ports team can control. You can post bug reports to Clang team. maybe some of them will be solved before the release of 9.0 -- Regards, Konstantin ___ 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: Compiling ports in a post-9.0-RELEASE world
13.03.2011, 01:00, "Doug Barton" : > Howdy, > > As many of you are no doubt already aware, much work has been undertaken > to make clang the default compiler for the src tree starting with > 9.0-RELEASE. It is not 100% certain that this change will be made, but > it's looking more likely every day. > > This raises an interesting question for how to deal with compiling ports > after 9.0 is released. So far there are 2 main ideas for how to deal > with this: > > 1. Fix all ports to compile with both gcc 4.2 (for RELENG_[78]) and clang. > 2. Adopt an official "ports compiler," which would likely be one of the > gcc versions from the ports tree itself, and update all ports to work > with it. 3. Fix Clang to compile more ports My $0.02 -- Regards, Konstantin ___ 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: (no subject)
04.03.2011, 10:44, "Anoop K" : > Hello, > I am a MS windows user and have come here from PC-BSD. I would like to > make a port request for Radiance < http://radsite.lbl.gov/radiance/ >. > > N.B: > I have only begun experimenting with FreeBSD and have 8.2 installed on > a stand alone multi boot machine, running KDE environment. You can start here: http://www.freebsd.org/doc/en/books/porters-handbook/ -- Regards, Konstantin ___ 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: Is it possible to install only some parts of libreoffice?
03.03.2011, 03:27, "Charlie Kester" : > On Wed 02 Mar 2011 at 15:06:52 PST Charlie Kester wrote: > >> I don't want or need all of the programs in the libreoffice suite. >> >> In fact, the only reason I might install it is to get the presentation >> program so I can work with PowerPoint files I occasionally download from >> the web. (There don't seem to be any workable, lighterweight >> alternatives, as there are for .doc and .xls files.) >> >> Would it be possible to provide some options to select which components >> to install? Or is the suite written in such a way that I have to >> install the whole thing in order to get one piece? It doesn't make much sense because all components of OOo/LibO are tightly integrated. -- Regards, Konstantin ___ 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: security/qca-tls 1.0_7 does not build in 9-CURRENT
02.03.2011, 08:56, "Matthias Apitz" : > Hello, > > Compiling the above mentioned port fails with: > > # make > ===> Building for qca-tls-1.0_7 > c++ -c -pipe -Wall -W -O2 -pipe -fno-strict-aliasing -fPIC -DQCA_PLUGIN > -DOSSL_097 -DOSSL_098 -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -DQT_PLUGIN > -DQT_SHARED -DQT_TABLET_SUPPORT > -I/usr/local/share/qt/mkspecs/freebsd-g++ -I. > -I../../../../../local/include -I../../../../../local/include > -I/usr/local/include -o qca-tls.o qca-tls.cpp Maybe you have OpenSSL 1.0.x, and qca-tls is configured for 0.9.8? (-DOSSL_097 -DOSSL_098) These versions are source-incompatible. -- Regards, Konstantin ___ 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: How to not use OPTIMIZED_FLAGS properly
07.02.2011, 20:34, "Ruslan Mahmatkhanov" : > Hello. > > I'm working on port that doesn't builds with "-O2 -pipe", that passed to > Makefile by default (it exits with message about virtual memory is > exhausted). I can avoid this by setting CFLAGS="" and CXXFLAGS="" in > CONFIGURE_ENV. But portlint is complaining like this: > > WARN: Makefile: CFLAGS/CXXFLAGS are not needed in CONFIGURE_ENV as they > are already added there in bsd.port.mk. > FATAL: Makefile: CFLAGS are clobbered in CONFIGURE_ENV. Alter CFLAGS in > the Makefile with CFLAGS+=... instead > FATAL: Makefile: CXXFLAGS are clobbered in CONFIGURE_ENV. Alter > CXXFLAGS in the Makefile with CXXFLAGS+=... instead > > What is the right way to do the job? > > PS. If i set -O0 in CONFIGURE_ENV, it's later redefined to "-O2 -pipe". Have you tried CFLAGS+=-O0 as portlint suggested? -- Regards, Konstantin ___ 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: policy on having the same routines in different library archives?
> I realise that fortran numerical libraries will > not interest many, so perhaps this is irrelevant anyway.. > I guess ones who are interested will prefer to have a choice of BLAS implementation depending on target hardware, parallelization scales, peculiarities of problem, personal preference, etc., etc. -- Regards, Konstantin ___ 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: policy on having the same routines in different library archives?
02.02.2011, 13:28, "Anton Shterenlikht" : > I've put a port of Slatec together: > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/151970 > > Recently I realised that some 110 routines in Slatec > are already present in math/blas, and the Blas versions > seem to be newer. > > % ar -t /usr/local/lib/libblas.a | sort > blas.sorted > % ar -t /usr/local/lib/libslatec.a | sort > slatec.sorted > % comm -12 blas.sorted slatec.sorted | wc > 110 110 882 > % > > I can see benefits and disadvantages of having same > routines in different libraries. Advantages are > that a user can choose to only install Slatec, > with no Blas, and that no fine tuning of the > distribution is required. > Disadvantages could be extra size and potential > for confusion, e.g. when linking against both > libraries. > > Is there a FreeBSD ports policy on this? FYI: there are lots of BLAS implementations in the world, all of them having the same API. The same for LAPACK. -- Regards, Konstantin ___ 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: [www/chromium] Illegal instruction: 4 on Pentium3
> Chromium requires sse2 normally, as detailed in this bug report: > > http://crbug.com/9007 This bug report is related to Chromium 2, but I've run Chromium 4 on PIII on Linux without problems -- Regards, Konstantin ___ 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: GIMP 2.4 - better ui usability
23.10.2010, 18:38, "Tomek CEDRO" : > On Fri, Oct 22, 2010 at 11:10 AM, Konstantin Tokarev > wrote: > >>> Maybe someone has similar feeling, so I thought maybe >>> its not that bad idea to create GIMP 2.4 port that keep all of the >>> nice features destroyed by a new design team in GIMP 2.6? >> Haven't you tried to take in contact with GIMP developers? > > Unfortunately yes [1], a new group of shitheads with "better sense of > taste" got into project and they know better than users what is more > comfortable. There are dozens of requests on bugzilla [2] to bring the > menu back to the toolbox, even separate project dedicated to make this > menu visible again in the toolbar [3]. All this is rejected, even no > option to make it work is being left. The old work and good habits are > destroyed with no alternative. The only arguments of Martin Nordholts > that I had talked with is that I "have no taste" because he knows no > "another program that has two main menus" (*) and so "There is no > arguing this, we won't add the menu back. Period.". I don't understand > why they don't want to leave this menu in toolbox as user choice > option. I only hope this kind of stuff never happens on FreeBSD > project. Probably port of gimp-classic (or option in GIMP port to add this patch) would be better solution than using outdated version. UI is not the only component of GIMP being changed by developers -- Regards, Konstantin ___ 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: GIMP 2.4 - better ui usability
> Maybe someone has similar feeling, so I thought maybe > its not that bad idea to create GIMP 2.4 port that keep all of the > nice features destroyed by a new design team in GIMP 2.6? Haven't you tried to take in contact with GIMP developers? -- Regards, Konstantin ___ 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: Distributed Version Control for ports(7) ( was: Re: autoconf update )
22.09.2010, 14:11, "Adam Vande More" : > BSD license > has a particular advantage in embedded/black box systems, so not polluting > base with more viral licensing is pretty important to project as whole I > think. Do embedded systems really need to use ports tree? I guess no, or only during initial setup by manufacturer -- Regards, Konstantin ___ 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: Distributed Version Control for ports(7) ( was: Re: autoconf update )
> This dvcs is BSD licensed: IMHO, if it's worth to change VCS, it would be much wiser to use well-known one -- Regards, Konstantin ___ 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: Distributed Version Control for ports(7) ( was: Re: autoconf update )
> > 1). http://bit.ly/d5UrtN > > 2). http://www.keltia.net/BSDCan/paper.pdf > > 3). http://bit.ly/97Y8Xi > > 4). Because CVS just does not do any of this. > > Make your final comparison here: > http://bit.ly/cyQBn8 > > For the sake of argument can you think of any reason to not switch ? Why not Git? Or you prefer to manage ports tree from Windows? -- Regards, Konstantin ___ 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: Re: GPLv3-licensed ports
> No, 3-clause BSD license is compatible with GPLv3 [1] (you can follow > multiple arrows on that figure). You can combine BSD-licensed code with > GPLv3-licensed code and either use it privately or redistribute it under > GPLv3. Pretty much the same as with GPLv2. Surely. > > This actually implies that the packages and possibly the patches in GPL > ports are covered by GPL too... hence the "legal decision" I guess. OK. Patches itself (sources) may have any compatible license (including BSD), but when they are applied to GPL sources, produced sources fall under GPL completely, including modified parts -- Regards, Konstantin ___ 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"
Fwd: FreeBSD Port: qtcreator-1.2.1: Not installable
Пересылаемое сообщение 28.10.09, 17:19, "Konstantin Tokarev" : 28.10.09, 16:42, "Konstantin Tokarev" : Do you really need Qt Creator IDE as dependency? I guess you need install qt4-qui-4.5.2 package, it will download qt4-core, qt4-qmake, qt4-uic, qt4-moc, qt4-rcc. If your software needs more Qt libraries than just Core and Gui, install whole qt4-4.5.2, it will install all mentioned packages plus all Qt libraries That's FreeBSD user-friendly :-) > 27.10.09, 21:55, "Sam Fourman Jr." : > > On Tue, Oct 27, 2009 at 8:11 PM, Adrian Glaubitz > > wrote: > > > Hi there, > > > > > > I have a linux/qt4 software project that I wanted to test on FreeBSD as > > > well. I'm not really a FreeBSD user > > > but I am trying to get my code to build there. Anyway, it requires > > > "qtcreator" among other dependencies which > > > is not installable with "pkg_add" at the moment, > > > > > > "pkg_add -r qtcreator" > > > > > > tells me that the file at the given URL > > > (ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7.2-release/Latest/qtcreator.tbz) > > > cannot be fetched. I am really not into *BSD so I can't tell I am doing > > > something wrong > > > but I guess the package seems to be missing on the mirrors. -- Regards, Konstantin Ловкая почта находится здесь: http://mail.yandex.ru/promo/new/hotkeys Завершение пересылаемого сообщения -- Regards, Konstantin Меткая почта находится здесь:http://mail.yandex.ru/promo/new/labels ___ 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: [Fwd: Re: acroread9 crashes after maybe 10 seconds ofoperation.]
Throw this proprietary and veeery slow shit^Wsoftware out of ports tree! 19.10.09, 17:31, "Stephen Montgomery-Smith" : > Boris Samorodov wrote: > > 1wk...@gmail.com writes: > > > >> Unfortunately, the map_at_zero sysctl didn't work for me. The > >> following massage still recorded in dmesg. > >> > >>> linux: pid 1378 (acroread): syscall inotify_init not implemented > >> I set the sysctl variable just before the kernel boot. After loading > >> kernel and modules and before booting the kernel, escape to the > >> command line mode of the loader, and type set > >> security.bsd.map_at_zero=1, then boot. > >> > >> Something wrong? > > > > Install acroread8 instead of acroread9. > This is my experience: I updated FreeBSD 8.0 about a week ago. > acroread8 stopped working with the helpful message "Abort." So I tried > out acroread9, which had never worked for me, and still didn't. Then I > saw these emails and tried > # sysctl security.bsd.map_at_zero=1 > acroread9 still didn't work. But then acroread8 started working again! > Stephen > ___ > 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" -- Regards, Konstantin Почта в порядке находится здесь: http://mail.yandex.ru/promo/new/order ___ 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"
