I'm running tmda-0.92 on Solaris 8
Any ideas?
I'm not sure anyone has ever used tmda-cgi with solaris yet. Welcome to beta testing.
At the point in the stacktrace you mentioned, the configure script tryes to get the environment variable "USER". If this isn't set in solaris, this would cause the error.
You can try the attached patch which may or may not fix the problem. It will try to look for $USER, then $LOGNAME, then call os.getlogin() as a last resort.
If this does not work, find out for me what environment variable solaris puts the current username in, and I'll make another patch.
If it does work, there may be other places in the code where the convention of using $USER for the current username may cause troubles. Let me know if this is the case and we can fix it.
-- Jim Ramsay "Me fail English? That's unpossible!"
diff -u -r1.20 configure
--- configure 10 Dec 2003 19:35:08 -0000 1.20
+++ configure 9 Mar 2004 17:31:23 -0000
@@ -446,8 +446,14 @@
F.write('#define VLOOKUP "TMDA_VLOOKUP=%(VLookup)s"\n' % OptD)
if OptD["Config"] != "None":
if OptD["Config"].find("~") >= 0:
+ if os.environ.has_key( "USER" ):
+ user = os.environ["USER"]
+ elif os.environ.has_key( "LOGNAME" ):
+ user = os.environ["LOGNAME"]
+ else:
+ user = os.getlogin()
OptD["Config"] = \
- string.replace(OptD["Config"], "/%s/" % os.environ["USER"], "/~/")
+ string.replace(OptD["Config"], "/%s/" % user, "/~/")
print """NOTE:
tmda-cgi will look for config files at: %s
Where <user> will be replaced by the user's login name.
_____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
