On Wed, 16 Jan 2002 09:53:41 +0000
[EMAIL PROTECTED] wrote:

> > Maybe you need to tell the linker where the crt_o is:
> > 
> > ex ld;"-L<directory_where_libs_crt_o_reside> <object_file_to_link> .."
> 
> I'll give that a try, but I'm sure it used to work with the single 
> command
> ex cc;"-o <exefilename> <sourcefilename>"
> with the LIB_DIR environment variable pointing at "win1_c68_lib_" where 
> the crt_o file is.  I'll check my boot file again, to make sure I 
> haven't broken it. Last resort will be a full reinstall of c68.

Have you set CC_PATH? 
SETENV "CC_PATH=win1_c68_"
AFAIK this is the only environment variable that has to be set, if you only use cc.
(If you also use ld, then it's not sufficient)
 
Claus

> Ian.
> 
> > -----Original Message-----
> > From: cgraf 
> > Sent: 15 January 2002 21:57
> > To: ql-users
> > Cc: cgraf
> > Subject: Re: [ql-users] EtherQL project.
> > 
> > 
> > On Tue, 15 Jan 2002 12:35:54 +0000
> > [EMAIL PROTECTED] wrote:
> > 
> > > Funny thing's started happening with C68 (4.24f) on my Q40.  It 
> > > compiles the source with no errors, then reports "could not open 
> > > crt.o".  The file is there, where it should be.  Need to 
> > try extracting 
> > > a fresh copy from the zip file, when I get a spare moment...
> > > 
> > > Ian.
> > 
> > Maybe you need to tell the linker where the crt_o is:
> > 
> > ex ld;"-L<directory_where_libs_crt_o_reside> <object_file_to_link> .."
> > 
> > Claus
> > 
> 
> 
> Visit our website at http://www.ubswarburg.com
> 
> This message contains confidential information and is intended only 
> for the individual named.  If you are not the named addressee you 
> should not disseminate, distribute or copy this e-mail.  Please 
> notify the sender immediately by e-mail if you have received this 
> e-mail by mistake and delete this e-mail from your system.
> 
> E-mail transmission cannot be guaranteed to be secure or error-free 
> as information could be intercepted, corrupted, lost, destroyed, 
> arrive late or incomplete, or contain viruses.  The sender therefore 
> does not accept liability for any errors or omissions in the contents 
> of this message which arise as a result of e-mail transmission.  If 
> verification is required please request a hard-copy version.  This 
> message is provided for informational purposes and should not be 
> construed as a solicitation or offer to buy or sell any securities or 
> related financial instruments.
> 

Reply via email to