cons-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: uninitialized value


From: mali
Subject: Re: uninitialized value
Date: Tue, 19 Jun 2001 14:43:48 +0800

Hi Steven,

You are right. cc is a symbolic to gcc and then linked to colorgcc, which is 
written in Perl.  And I guess maybe there is something wrong the Perl itself, 
so just now I updated to perl-5.6.1(from perl-5.00503).  Now everything seems 
Ok.:)

Thanks again for your help.

Best Regards
Robbert

----- Original Message ----- 
From: Steven Knight <address@hidden>
To: mali <address@hidden>
Sent: Tuesday, June 19, 2001 12:19 AM
Subject: Re: uninitialized value 


> Robbert--
> 
> Thanks for the thorough debug info.  Next steps...
> 
> > Thank you for your help. I tried the following, and found there is sth. 
> > wrong when running " exec($com)",
> > but  don't know how to fix it. Btw, the os is Mandrake 7.0.
> 
> I only have access to a straight Red Hat system, so apologies in advance
> if some of this gets pedantic just to weed out any possibility of
> significant differences.
> 
> > address@hidden hello]$ cat Construct
> > $env=new cons( );
> > Program $env 'hello', 'hello.c';
> > address@hidden hello]$ cc -c hello.c
> > address@hidden hello]$ cc -o hello hello.o
> 
> What's $PATH set to?  Could you supply output from "whereis cc" to find
> out if there are any other "cc" executables out there?  What happens
> when you explicitly try:
> 
> /usr/bin/cc -c hello.c
> 
> For that matter, what does "file /usr/bin/cc" say?  And if it's a
> symbolic link, what does "file" report for the target of the link?
> 
> > address@hidden hello]$ rm -f hello
> > address@hidden hello]$ perl -d cons hello
> >
> > Loading DB routines from perl5db.pl version 1.0402
> > Emacs support available.
> >
> > Enter h or `h h' for help.
> >
> > main::(cons:20):        $ver_num = "2.2";
> >   DB<1> c 1493
> > cc -o hello hello.o
> > build::command::action(cons:1493):                    eval 'exec($com)';
> 
> At this point, what do you see when you try:
> 
> x $env->{ENV}
> 
> Actually, it might also be useful to look at
> 
> x $env
> 
> Although that will print out a lot of stuff...
> 
> --SK
> 
> 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]