On Wed, 2001-11-28 at 08:53, Jonathan Perkin wrote:
> Question one:  Please describe your computer system
>       Hardware type?
> 
>               Sun Ultra 10
> 
>       Operating System? (try uname -a for most, or uname -X for SCO)
> 
>               SunOS inet34 5.8 Generic_108528-03 sun4u sparc SUNW,Ultra-5_10
> 
>       Your compiler (include version, if known)
> 
>               gcc version 2.95.2 19991024 (release)
> 
> Question two:  Where does your problem occur?
>       [ ]  Configure time (dies while running configure)
>       [x]  Compiler time (dies when you type 'make')
>       [ ]  Run time (You got a "CRITICAL PROTECTION ERROR")
>       [ ]  Run time (You got a "PANIC" message)
>       [ ]  Run time (non-fatal logic bug)
> 
> If it is at compile time, please include a cut and paste of
> everything that appears on your screen from the line when you 
> type 'make' until you see your prompt again.  Please do not leave
> out any lines, for any line may contain very important information!
> 
> gcc -g -O  -o epic alias.o alist.o array.o commands.o compat.o crypt.o ctcp.o
> dcc.o debug.o exec.o files.o flood.o functions.o funny.o glob.o help.o
> history.o hook.o if.o ignore.o input.o irc.o ircaux.o ircsig.o keys.o
> lastlog.o list.o log.o mail.o names.o network.o newio.o notice.o notify.o
> numbers.o output.o parse.o queue.o reg.o screen.o server.o status.o term.o
> timer.o translat.o vars.o who.o window.o words.o   info.o -lcurses
> -L/usr/ccs/lib  -lsocket -lnsl -lresolv -lcrypt -lm
> Undefined                       first referenced
>  symbol                             in file
> setenv                              commands.o
> unsetenv                            commands.o
> ld: fatal: Symbol referencing errors. No output written to epic
> collect2: ld returned 1 exit status
> gmake[1]: *** [epic] Error 1
> 
> Please include any other information that you think we should know about.
> 
>       Yes, Solaris sucks for removing setenv(3), but that doesn't mean EPIC
>       should implement it without supporting putenv(3) or something which
>       Solaris does support :)
>       Unsure whether this latest change breaks SunOS 4.x support too..
> 
> Thank you for taking the time to fill this out.  We hope that this form
> will make finding and fixing bugs much less of a headache for both
> us and you.  We will reply to you as soon as possible (probably the next
> school day), and we will let you know when we've fixed the problem and
> give you a patch for it.
> 
> Author(s): Originally by Michael Sandroff, 
>          Current copyright holder is Matthew Green
>          EPIC is developed by EPIC Software Labs for the EPIC project.
>          "EPIC" and "ESL" are trademarks of the EPIC project.
> Product:  ircII-EPIC4pre2 (see UPDATES) 
> 
> <EOF>
> _______________________________________________
> List mailing list
> [EMAIL PROTECTED]
> http://epicsol.org/mailman/listinfo/list
putenv() is POSIX while setenv() is a BSDism...  putenv() should be more
widely supported anyway, so I'm not sure why we're using setenv()

-- 
Ben Winslow ([EMAIL PROTECTED]) : Common sense is the collection of
       System Administrator       : prejudices acquired by age
   Bluecherry Internet Services   : eighteen. -- Albert Einstein  
    http://www.bluecherry.net/    : 
          (573) 592-0800          : 

Attachment: signature.asc
Description: PGP signature

Reply via email to