Hi folks,
For a few days now, I have a lot of problems with wine. I've managed to get it going a few days back, but I can't remember how. Now it just seg faults at startup. I just did a:
[dimi@dimi wine.build]$ make -s clean [dimi@dimi wine.build]$ ../wine.src/configure --with-ntpd --silent && make -s depend && make -s [root@dimi wine.build]# make -s install
but that did not fix it:
[dimi@dimi dimi]$ which wine /usr/local/bin/wine [dimi@dimi dimi]$ wine Segmentation fault [dimi@dimi dimi]$ gdb wine GNU gdb Red Hat Linux (5.3post-0.20021129.18rh) Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"... (gdb) run Starting program: /usr/local/bin/wine
Program received signal SIGSEGV, Segmentation fault. 0x420ebe3c in __libc_pthread_init () from /lib/tls/libc.so.6 (gdb)
Am I the only one with this problem?
Le lun 01/09/2003 à 10:28, Dimitrie O. Paun a écrit :
Hi folks,
For a few days now, I have a lot of problems with wine. I've managed to get it going a few days back, but I can't remember how. Now it just seg faults at startup. I just did a:
[dimi@dimi wine.build]$ make -s clean [dimi@dimi wine.build]$ ../wine.src/configure --with-ntpd --silent && make -s depend && make -s
---------------------^ Should be --with-nptl :)
Vincent
On September 1, 2003 10:36 am, Vincent Béron wrote:
[dimi@dimi wine.build]$ ../wine.src/configure --with-ntpd --silent && make -s depend && make -s
---------------------^
Should be --with-nptl :)
OK, and why don't I get an error? I've always assumed I'd be told if I misstype it!
Le lun 01/09/2003 à 10:43, Dimitrie O. Paun a écrit :
On September 1, 2003 10:36 am, Vincent Béron wrote:
[dimi@dimi wine.build]$ ../wine.src/configure --with-ntpd --silent && make -s depend && make -s
---------------------^
Should be --with-nptl :)
OK, and why don't I get an error? I've always assumed I'd be told if I misstype it!
./configure --with-worthless-arg|grep worthless don't show anything either (and nothing on stderr).
I'd say autoconf works that way, just silently processing unknown args.
Vincent
On September 1, 2003 10:58 am, Vincent Béron wrote:
./configure --with-worthless-arg|grep worthless don't show anything either (and nothing on stderr).
I'd say autoconf works that way, just silently processing unknown args.
Well, it does, but it's Just Not Cool(TM). I wonder if we could do some error checking ourselves. Is the current behaviour desirable?
Dimitrie O. Paun wrote:
I'd say autoconf works that way, just silently processing unknown args.
Well, it does, but it's Just Not Cool(TM). I wonder if we could do some error checking ourselves. Is the current behaviour desirable?
It works that way because it may call other configure scripts, and pass the --with-* options to them, so it doesn't know in advance which --with options are valid and which are not.
That doesn't mean we can't try and detect invalid ones ourselves though.
Mike
On Mon, 2003-09-01 at 16:01, Dimitrie O. Paun wrote:
Well, it does, but it's Just Not Cool(TM). I wonder if we could do some error checking ourselves. Is the current behaviour desirable?
Desirable, probably not. Standard, yes. It's just autotools sucking, it'd be nice to replace it with a newer build system at some point.
man, 01.09.2003 kl. 16.43 skrev Dimitrie O. Paun:
On September 1, 2003 10:36 am, Vincent Béron wrote:
[dimi@dimi wine.build]$ ../wine.src/configure --with-ntpd --silent && make -s depend && make -s
---------------------^
Should be --with-nptl :)
OK, and why don't I get an error? I've always assumed I'd be told if I misstype it!
Guess you've always assumed wrong, then. It's just the way autoconf works - with --enable-* and --with-*, you can give it anything, autoconf will just set a variable named whatever you gave it, and leaves to the script to interpret the particular variable names it's interested in.