Re: freebsd-questions Digest, Vol 110, Issue 20

>   33. Re: * Command failed [exit code 1]:
/usr/bin/script -qa
>       /tmp/portupgrade84798.26 make (Vizion)
> From: Vizion <vizionvizion.occoxmail.com>

hello,

thanks for your reply to my question.

> >gmake[1]: Leaving directory
`/usr/ports/www/firefox/work/mozilla'
> >gmake: *** [default] Error 2
> >*** Error code 2
> >Stop in /usr/ports/www/firefox.

> What were the lines before:
> >gmake[1]: Leaving directory
`/usr/ports/www/firefox/work/mozilla'

.... unfortunately, i only clipped the lines i did, trying
to keep my 
message as short as possible. doh! i'm not sure where to
locate the 
file that all those screens of garbled text goes to either.
i looked 
in /var/log, but i couldn't see anything that looked likely.
any idea 
where i could find the file?

(i tried, successfully, to update the portupgrade port,
after posting my 
question. but the firefox port upgrade, subsequently, still
refused to 
compile.)


_______________________________________________
freebsd-questionsfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"

On Monday 05 September 2005 00:52,  the author David Armour
contributed to the 
dialogue on-
 Re: freebsd-questions Digest, Vol 110, Issue 20: 

>>   33. Re: * Command failed [exit code 1]:
/usr/bin/script -qa
>>       /tmp/portupgrade84798.26 make (Vizion)
>> From: Vizion <vizionvizion.occoxmail.com>
>
>hello,
>
>thanks for your reply to my question.
>
>> >gmake[1]: Leaving directory
`/usr/ports/www/firefox/work/mozilla'
>> >gmake: *** [default] Error 2
>> >*** Error code 2
>> >Stop in /usr/ports/www/firefox.
>>
>> What were the lines before:
>> >gmake[1]: Leaving directory
`/usr/ports/www/firefox/work/mozilla'
>
>... unfortunately, i only clipped the lines i did,
trying to keep my
>message as short as possible. doh! i'm not sure where to
locate the
>file that all those screens of garbled text goes to
either. i looked
>in /var/log, but i couldn't see anything that looked
likely. any idea
>where i could find the file?
>
>(i tried, successfully, to update the portupgrade port,
after posting my
>question. but the firefox port upgrade, subsequently,
still refused to
>compile.)


Just do the make again -- you will get the compiler errors.

If you are compiling from an X window you can just save the
jhistory into a 
file - otherwise you will have to redirect the console
output to a file

david
40 yrs navigating and computing in blue waters.
English Owner & Captain of British Registered 60'
bluewater Ketch S/V Taurus.
 Currently in San Diego, CA. Sailing bound for Europe via
Panama Canal after 
completing engineroom refit.
_______________________________________________
freebsd-questionsfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"

On Sep 5, 2005, at 4:52 PM, David Armour wrote:

>>   33. Re: * Command failed [exit code 1]:
/usr/bin/script -qa
>>       /tmp/portupgrade84798.26 make (Vizion)
>> From: Vizion <vizionvizion.occoxmail.com>
>>
>
> hello,
>
> thanks for your reply to my question.
>
>
>>> gmake[1]: Leaving directory
`/usr/ports/www/firefox/work/mozilla'
>>> gmake: *** [default] Error 2
>>> *** Error code 2
>>> Stop in /usr/ports/www/firefox.
>>>
>
>
>> What were the lines before:
>>
>>> gmake[1]: Leaving directory
`/usr/ports/www/firefox/work/mozilla'
>>>
>
> ... unfortunately, i only clipped the lines i did,
trying to keep my
> message as short as possible. doh! i'm not sure where
to locate the
> file that all those screens of garbled text goes to
either. i looked
> in /var/log, but i couldn't see anything that looked
likely. any idea
> where i could find the file?
>
> (i tried, successfully, to update the portupgrade port,
after  
> posting my
> question. but the firefox port upgrade, subsequently,
still refused to
> compile.)

David,
     Just try to recompile; if it doesn't work, it will come
up  
again. This is by far a much earlier and quicker way to
finding the  
initial problem as opposed to looking for logs, etc because
odds  
hunting for the specific log will take a while in the build 

directory. Besides, your compile might work this time if you
try again.
-Garrett
_______________________________________________
freebsd-questionsfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"