How to re-run make config?

[FreeBee]

I'm building Xorg and I accidentally entered two conflicting video drivers. Now I need to re-run make config, but that says:

===> No options to configure

So, I'm stuck. How can I proceed?

[vermaden]

# make rmconfig config

[FreeBee]

Originally Posted by vermaden

# make rmconfig config

I tried it and ...

===> No user-specified options configured for xorg-7.4_2
===> No options to configure

[DutchDaemon]

x11/xorg is a meta-port, which has no options of itself. The countless ports it draws in to build Xorg certainly have. You'll have to figure out which port it actually is ..

Some of them are:

/usr/ports/x11-drivers/xorg-drivers
/usr/ports/x11-fonts/xorg-fonts
/usr/ports/x11-servers/xorg-server
/usr/ports/x11-themes/xcursor-themes
/usr/ports/x11/xbitmaps
/usr/ports/x11/xorg-apps
/usr/ports/x11/xorg-docs
/usr/ports/x11/xorg-libraries

You can also check out the /var/db/ports/*/options files.

[FreeBee]

Found it! Great! Thanks.

[FreeBee]

checking whether Python support is requested... checking whether /usr/local/bin/python2.6 version >= 2.5... yes
checking for /usr/local/bin/python2.6 version... 2.6
checking for /usr/local/bin/python2.6 platform... freebsd8
checking for /usr/local/bin/python2.6 script directory... ${prefix}/lib/python2.6/site-packages
checking for /usr/local/bin/python2.6 extension module directory... ${exec_prefix}/lib/python2.6/site-packages
checking for headers required to compile python extensions... not found
configure: error: Python headers not found
===> Script "configure" failed unexpectedly.
Please run the gnomelogalyzer, available from
"http://www.freebsd.org/gnome/gnomelogalyzer.sh", which will diagnose the
problem and suggest a solution. If - and only if - the gnomelogalyzer cannot
solve the problem, report the build failure to the FreeBSD GNOME team at
gnome@FreeBSD.org, and attach (a)
"/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.6.7/config.log",
(b) the output of the failed make command, and (c) the gnomelogalyzer output.
Also, it might be a good idea to provide an overview of all packages installed
on your system (i.e. an `ls /var/db/pkg`). Put your attachment up on any
website, copy-and-paste into http://freebsd-gnome.pastebin.com, or use
send-pr(1) with the attachment. Try to avoid sending any attachments to the
mailing list (gnome@FreeBSD.org), because attachments sent to FreeBSD mailing
lists are usually discarded by the mailing list software.
*** Error code 1

Stop in /usr/ports/devel/gobject-introspection.
*** Error code 1

Stop in /usr/ports/sysutils/polkit.
*** Error code 1

Stop in /usr/ports/sysutils/consolekit.
*** Error code 1

Stop in /usr/ports/sysutils/hal.
*** Error code 1

Stop in /usr/ports/sysutils/hal.
*** Error code 1

Stop in /usr/ports/x11-servers/xorg-server.
*** Error code 1

Stop in /usr/ports/x11-servers/xorg-server.
*** Error code 1

Stop in /usr/ports/x11/xorg.

Gnomelogalyzer:

Generating build log. Please wait... done.

The cause of your build failure is not known to gnomelogalyzer.sh. Before
e-mailing the build log to the FreeBSD GNOME team at freebsd-gnome@FreeBSD.org,
TRY EACH OF THE FOLLOWING:

* If you are generating your own logfile, make sure to generate it with
something similar to:
"make 2>&1 | tee /path/to/logfile" (sh/bash/ksh/zsh) or
"make |& tee /path/to/logfile" (csh/tcsh)
* Make sure your cvsup(1) configuration file specifies the 'ports-all'
collection
* Run cvsup(1) and attempt the build again
* Check /usr/ports/UPDATING for information pertinent to your build
failure
* 99% of the commonly reported build failures can be solved by
running "portupgrade -a" --> I'm at this stage right now.
* Read the FAQs at http://www.FreeBSD.org/gnome/
* Search the archives of freebsd-gnome@FreeBSD.org. Archives can be
searched at http://www.freebsd.org/gnome/index.html#search

If you have not performed each of the above suggestions, don't bother asking
for help. The chances are good that you'll simply be told to perform one of
the aforementioned steps.