|
FreeBSD Ports and Packages Installation and upgrading of ports and packages on FreeBSD. |
|
Thread Tools | Display Modes |
|
|
|||
How to get port's building options?
Hi,
I would like to see with which options (WITH_*** or WITHOUT_***) a port can be built. Is there a way to see this recursively through the dependencies? Quote:
Regards |
|
|||
"make config" will bring up the ncurses configuration screen; make "config-recursive" does the same for meta-ports that have multiple configuration screens in the various subports.
You can also read the Makefile(s). |
|
|||
Thank you for your answers.
@anomie: Stupid question but.... once i get the WITH options through that method... how do I use them to compile in one command line? @DrJ I have seen this one but, it doesn't really solve my problem. I can help for a port and it's depedencies but it won't help if i have 20 ports to install in a row. or did I miss an option? |
|
|||
Quote:
Quote:
|
|
|||
thank you.
I tried : make -DWITH_OPTION but it is still firing the GUI for the options. So far the repetitive "make config" seems to be the best solution... but it is not quite what i wanted though... Ideal would be to use the line "make -DWITH_OPTION" without the GUI appearing. |
|
|||
Quote:
Quote:
I don't view it as much of a limitation, personally. Most ports these days use all the cores you have, so there really is no point in running them in parallel. You also can get into trouble doing that anyway. It also is usually a good idea to see that one port has installed properly before moving on to the next. Otherwise you really should script the session to figure out what happened, and those files then get huge and cumbersome. |
|
||||
>Most ports these days use all the cores you have,
They don't. There are a small number of ports only that are able to build in parallel. It's a new knob in make.conf (since some weeks), but usually it's done via a whitelist (it's an ongoing project).
__________________
use UNIX or die :-) |
|
|||
I'll stand corected. Most of the ones *I* have installed seem to use multiple cores. Gnome does, for example.
|
|
||||
>Most of the ones *I* have installed seem to use multiple cores.
Yes but take a closer look, they aren't compiling with -jx. You're just seeing the use of multiple cores because the scheduler allocates some tasks like disk io etc. to different cores. Firefox, QT, GTK, OO etc. are on the agenda - but tests take a long time. And guess why? See for example icu: http://www.freshports.org/devel/icu/ Quote:
[edit] http://blogs.freebsdish.org/pav/2009...-for-everyone/ Multi processor compilations for everyone
__________________
use UNIX or die :-) |
|
|||
That may be, but I noted that portupgrades of Gnome after the announcement (for parallel ports builds) my computer idle time dropped to 5% (according to top) when before it was about 50%. Build times went down too. That's more than disk buffering, I'd think.
|
|
|||
Well some do, and most don't. Clearly I looked at top only when the parallel build upgrades were taking place. You can also feel it -- an idle time of 5% is sure different than 50%.
|
|
|||
I hope you have either a decent CPU or some patience! My set-up unfortunately requires the latter.
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Find command (Linux options?) | deadeyes | FreeBSD General | 11 | 23rd August 2009 06:07 PM |
portupgrade -af, how to submit fetch options? | bsdfan | FreeBSD Ports and Packages | 4 | 28th December 2008 09:05 PM |
Change compile options for a determined port | Treppiede | FreeBSD Ports and Packages | 4 | 5th October 2008 05:59 AM |
Change Makefile options in ports | shep | FreeBSD Ports and Packages | 5 | 18th August 2008 07:58 AM |
Buildworld make.conf options | siffland | FreeBSD Installation and Upgrading | 4 | 12th May 2008 12:02 AM |