Anope IRC Services

Anope Support => 1.8.x/1.7.x Support (Read Only) => Topic started by: STING on August 16, 2006, 07:15:55 PM

Title: [1.7.15] problem with ./Config
Post by: STING on August 16, 2006, 07:15:55 PM
[Anope 1.7.15 on linux system]

Hello,

It seems i'm the only one with the following problem.
Anope-1.7.13 runs ./Config fine
Anope-1.7.15 doesn't anymore:

Quote

checking for short... yes
checking size of short... configure: error: cannot compute sizeof (short), 77
See `config.log' for more details.


Where .13 reports:

Quote

checking for short... yes
checking size of short... 2


Someone any idea how I can solve this problem?

[Edited on 16-8-2006 by STING]

[Edited on 16-8-2006 by STING]
Title:
Post by: n00bie on August 16, 2006, 07:31:14 PM
as told by Trystan that was something with MySQL.

Disabled MYSQL checking while doing /Config and that will help. I have the same problems with that errors before and disabling Mysql checking fixed the problem :)
Title:
Post by: STING on August 16, 2006, 07:34:00 PM
Thanks alot, that helped!
Title:
Post by: Jan Milants on September 14, 2006, 02:21:04 PM
is there a way to get around this though...
just updated my services - in a little less lazy moment - from a .13 svn where sql was working fine and ran into this little bugger... (http://forum.anope.org/images/smilies-new/frusty.gif)
Title:
Post by: katsklaw on September 14, 2006, 10:03:49 PM
the .15 mysql problems that were reported were fixed in svn. One could use svn or wait for the next release.
Title:
Post by: Jan Milants on September 14, 2006, 11:00:14 PM
Quote
Originally posted by katsklaw
the .15 mysql problems that were reported were fixed in svn. One could use svn or wait for the next release.


i had the problem with svn.. build 1154
Title:
Post by: katsklaw on September 15, 2006, 11:01:01 PM
Then it's not the "problems that were reported" which was fixed on 9/10/06 as bug #595 which is in r1150. :)
Title:
Post by: Jan Milants on September 16, 2006, 12:25:03 AM
the #595 bug had nothing to do with errors during config, which is what this thread is about.. this is about anope not even compiling with SQL support.... (where it used to work in older releases..)

[Edited on 15-9-2006 by Viper]
Title:
Post by: katsklaw on September 16, 2006, 01:08:30 AM
oh you're right .. my bad.

[Edited on 16-9-2006 by katsklaw]
Title:
Post by: Dave Robson on September 16, 2006, 10:27:44 AM
It happens when your "mysql-config" program isnt setup right, so when anope does a" mysql-config --cflags" it gets an incorrect answer back, which breaks stuff - not sure what we can/should do about this....
Title:
Post by: Jan Milants on September 16, 2006, 11:23:16 AM
hmmm so i should contact my host about this then ?
the weird thing is that up to version 14 i never had a problem with compiling with sql, so something must have changed, either by my host, or in anope...
Title:
Post by: Dave Robson on September 16, 2006, 12:52:32 PM
anope previously didnt use mysql-config - we just randomly tried "common" locations for mysql.  Now we use mysql-config, which is part of mysql, and should tell us exactly where it is... problem is when it isnt setup properly :/
Title:
Post by: NDarkstar on September 18, 2006, 11:51:05 PM
For what it's worth, this issue exists on a stock Fedora Core 5 install.
Title:
Post by: Dave Robson on September 19, 2006, 07:12:45 AM
can you give us the output of a "mysql-config --cflags" ?
Title:
Post by: pwpreacher on September 19, 2006, 11:49:10 AM
on my fedora core 5 I get this result.

/usr/lib/mysql/mysql_config --cflags
-I/usr/include/mysql -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fno-strict-aliasing -fwrapv
Title:
Post by: NDarkstar on October 16, 2006, 06:11:32 PM
This issue with mysql still occurs in build 1.7.16.

Recently performed a clean reinstall of FC5 on my server and mysql_config --cflags gives the same output as pwpreacher.
Title:
Post by: Pieter Bootsma on August 08, 2007, 08:07:27 PM
Can you paste the entire output of ./Config plus the entire contents of config.log of an errornous invocation?
Title:
Post by: SNU on August 08, 2007, 09:36:27 PM
LoL 10 Months later? Hopefully he didn't wait that long and found a solution :D
Title:
Post by: NDarkstar on August 09, 2007, 02:37:58 AM
Well, for what it's worth, 1.7.19 does not have this issue under FC5.

Would you like me to dig up a copy of 1.7.15 to get the output for you, or is this a closed issue?
Title:
Post by: Pieter Bootsma on August 09, 2007, 08:10:05 PM
There's still something fishy going on apparently, but i do not need a config.log if it's now fixed for you :)