Compiling error's eggdrop1.6.18+ssl tcl8.4.14

[bleh1234]

while compiling eggdrop 1.6.18 with ssl patch i ran in to these error's/warning's

I have searched the web several times re-downloaded packages but still gettting them.

Anyone has a clue?

Code: Select all

gcc -pipe -mwin32 -g -O2 -Wall -I.. -I.. -DHAVE_CONFIG_H   -c tcl.c
tcl.c:493: warning: dereferencing type-punned pointer will break strict-aliasing
 rules
tcl.c: In function `readtclprog':
tcl.c:746: warning: assignment discards qualifiers from pointer target type

tcl.c line:
493: {"uptime", (int *) &online_since, 2},
746: result = Tcl_GetVar(interp, "errorInfo", TCL_GLOBAL_ONLY);

Code: Select all

gcc -pipe -mwin32 -g -O2 -Wall -I.. -I.. -DHAVE_CONFIG_H   -c userent.c
userent.c: In function `del_entry_type':
userent.c:1135: warning: dereferencing type-punned pointer will break strict-ali
asing rules

userent.c line:
1135: return list_delete((struct list_type **) &entry_type_list,

Don't know what i'm doing wrong or if it harms eggdrop.

[DragnLord]

take note that it says "warning", not "error"

did eggdrop finish compiling?
if it finished compiling did it install?
if it installed does it run?

[bleh1234]

take note that it says "warning", not "error"

did eggdrop finish compiling?
if it finished compiling did it install?
if it installed does it run?

Yup it does all of that but those warnings aren't for nothing and have no idea how it effects eggdrop itself.

[Alchera]

They are simply warnings. These are similar to the putlog entries of eggdrop; they are there for the benefit of the coder and do not affect the working of eggdrop if it compiled error free!

[awyeah]

Don't know what i'm doing wrong or if it harms eggdrop.

Don't worry it won't harm your eggdrop. Even if your eggdrop drops, I'm sure it wont shatter to pieces, as it has a hard shell around it.

If there was an error the compiling would have immediately stopped right there. So then you know theres a problem with either the open source eggdrop, tcl package installed or maybe your OS.

[rosc2112]

Those warnings are just peculiarities in the differences between types of compilers and C programming styles (vintages?) Newer versions of gcc in particular are getting a lot stricter so throws more warnings, but generally if a piece of code compiles and runs without segfaulting, warnings are harmless.

Wouldn't hurt to read up on C programming and gcc's peculiarities, there's a lot of websites out there devoted to teaching C and Gnu C, and in particular, the "make" program, so you can actually use error messages effectively (just cos make said an error occurred on a certain line, doesn't always mean it was THAT line, it could be preceding lines in the chain.)