configure: WARNING: sys/sysctl.h: present but cannot be compiled
configure: WARNING: sys/sysctl.h: check for missing prerequisite headers?
configure: WARNING: sys/sysctl.h: see the Autoconf documentation
configure: WARNING: sys/sysctl.h: section "Present But Cannot Be Compiled"
configure:
On Tue, 2003-10-14 at 14:07, Dimitrie O. Paun wrote:
> Yes, winecfg still needs a lot of work. I think the version in the tree
> is fairly up-to-date.
That is correct, I have no outstanding patches as far as I'm aware. I'll
get back to it soon enough, still settling down and finding the best
hacki
On October 13, 2003 04:20 pm, Alex Pasadyn wrote:
> I think there are two separate problems that are being addressed, and it
> makes sense to have and document two stages of configuration. Step one
> doesn't ask too many questions (really just whether you want to use an
> existing "C" drive or not
It's true, winesetuptk is very usable (It's a wizard), and winecfg look more
complicated than anything in windows. I did read that some very simple programs
could run without a windows like filesystem. As winecfg is a winelib app, I
suppose it may be possible to run it without a windows like filesy
After taking a look at winesetuptk, I have some questions:
I've been watching the IRC channel and I've seen a lot of people who
install wine first (either from a binary package or from "make install")
and then ask how to configure it. They want a single command they can
run to simply get thing
