Compiling error again.

[ckin-]

I get this after doing make

Linking eggdrop .

gcc -pipe -o ../eggdrop bg.o botcmd.o botmsg.o botnet.o chanprog.o cmds.o dcc.o dccutil.o dns.o flags.o language.o match.o main.o mem.o misc.o misc_file.o modules.o net.o rfc1459.o tcl.o tcldcc.o tclhash.o tclmisc.o tcluser.o userent.o userrec.o users.o -L/usr/local/lib -ltcl8.3 -lm -ldl -lnsl md5/md5c.o compat/*.o `cat mod/mod.xlibs` -lssl -lcrypto -L/usr/lib -L/usr/lib
touch ../eggdrop

Successful compile: eggdrop

make[1]: Leaving directory `/home/mee/eggdrop1.6.17/src'
make[1]: Entering directory `/home/mee/eggdrop1.6.17/src/mod'
make[2]: Entering directory `/home/mee/eggdrop1.6.17/src/mod/assoc.mod'
gcc -pipe -I/usr/kerberos/include/ -Wall -I. -I../../.. -I../../.. -I../../../src/mod -DHAVE_CONFIG_H -DMAKING_MODS -c .././assoc.mod/assoc.c
mv assoc.o ../
gcc -pipe -o ../../../assoc.so ../assoc.o -L/usr/local/lib -ltcl8.3 -lm -ldl -lnsl
/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/../../../crt1.o(.text+0x18): In function `_start':
../sysdeps/i386/elf/start.S:77: undefined reference to `main'
collect2: ld returned 1 exit status
make[2]: *** [../../../assoc.so] Error 1
make[2]: Leaving directory `/home/mee/eggdrop1.6.17/src/mod/assoc.mod'
make[1]: *** [assoc.mod_so] Error 2
make[1]: Leaving directory `/home/mee/eggdrop1.6.17/src/mod'
make: *** [modules] Error 2

I did
CFLAGS="-I/usr/kerberos/include/" ./configure --with-ssl=/usr
then I edited the Makefile and removed the line in XSSL include something that has been mentioned here before. I thought that would fix the previous compiling error I got but then this came up instead.

any ideas?
TIA

[ckin-]

c'mon someone must know something about this error ;/

[ckin-]

81 views and not a single eggdrop expert who can give a helping hand? guess I'm screwed..

[Alchera]

It's probably a RH specific problem and you should research the RH forums.

[demond]

screwed up Makefile, gcc tries to link an executable, and .so module is not an executable (no main() entry point); gcc (or ld) should be invoked with -Bshareable

[ckin-]

I noticed now I forgot to mention that I dont have access to the command uname, so I get error after ./configure that it cant determine the system it's trying to compile on. maybe that's what messing it up. I've mailed the admins about them maybe giving me access to that command.

also demond I have no idea what your talking about heh. I havent messed with the Makefile at all, although with the compiler not getting access to what system it's on it maybe messes that stuff up? I dunno.

maybe u know the solution to the prob and can be more specific on how to solve it?

I'll try googling on the RedHat forums as Alchera mentioned aswell.

any more help is appreciated!

TIA

EDIT::
Ok the only prob was the uname access. worked now after admin made me use the command. thx for the help anyways

[Alchera]

@ ckin- It would have been more helpful (to all) if you'd stated from the outset that it was not your box.

[demond]

uname is essential for configure, talk to your admin and demand execution permissions for it

[De Kus]

uname is essential for configure, talk to your admin and demand execution permissions for it

is there really not way? Can't it be used from the .cache file or the env vars (all neccessary informations are stored there as well)? My admin probably accicently blocked uname and now i cant configure there, too .

[demond]

well, you can always patch your configure script with uname's output

[KrzychuG]

Or use mine simplified uname and modify configure script a little ;)

[De Kus]

Or use mine simplified uname and modify configure script a little

wow, this looks so simply, but its simply great, because putting it as bin/uname in my home dir I could use ./configure without any modifcations again .

[DonnaA2Z]

Believe me, I'm no bot expert, I'm a newbie and am here for help as well. But your problem sounds like a similar problem that I had in the beginning.

What kind of shell is your bot on, linux ... Solaris... do you know?

If it is a Solaris, you should use "make eggdrop" instead of just "make" at that step.

The "uname" file ... I can recall having an issue with that myself, but I can't recall what the exact solution was unfortunately.

You can try to chmod +x uname in order to get permissions, if you know where the file is and can change the permissions.

Or it could be a problem with the bot installation finding all the TCL stuff it needs. Or the wrong version is installed on the server for your bot. In which case will probably require assistance from your admin.

Donna