Date: Sat, 6 Mar 1999 18:31:25 -0000 From: "Erik Arokszallasi" <erik@erba.hu> To: "Ben Smithurst" <ben@scientia.demon.co.uk> Cc: <FreeBSD-questions@FreeBSD.ORG> Subject: Problems compiling prots Message-ID: <029601be67ff$8fd64be0$416126c3@erba.satimex.tvnet.hu>
next in thread | raw e-mail | index | archive | help
Hi! Ok, I will take care, sorry. In the mean time I tried this again and wrote the whole procedure in a tmp file. The last line are here: cc -DHAVE_CONFIG_H -I. -I.. -Ichrtrans -I./chrtrans -I.. -I../src -I ../WWW/Library/Implementation -O -pipe -c ./LY cc -DHAVE_CONFIG_H -I. -I.. -Ichrtrans -I./chrtrans -I.. -I../src -I ../WWW/Library/Implementation -O -pipe -c ./LY cc -DHAVE_CONFIG_H -I. -I.. -Ichrtrans -I./chrtrans -I.. -I../src -I ../WWW/Library/Implementation -O -pipe -c ./LY cc -DHAVE_CONFIG_H -I. -I.. -Ichrtrans -I./chrtrans -I.. -I../src -I ../WWW/Library/Implementation -O -pipe -c ./LY cc -O -pipe chrtrans/makeuctb.c -o chrtrans/makeuctb *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Or do you think should I send the whole file as an attachment? Thanks Erik Arokszallasi -----Original Message----- From: Ben Smithurst <ben@scientia.demon.co.uk> To: Erik Arokszallasi <erik@erba.hu> Cc: FreeBSD-questions@FreeBSD.ORG <FreeBSD-questions@FreeBSD.ORG> Date: Saturday, March 06, 1999 6:16 PM Subject: Re: problems compiling ports >Erik Arokszallasi wrote: > >> I hope you can help me. > >Probably not, since you haven't provided enough information. > >> We have installed a FreeBSD 3.1 and we have also the whole ports >> collection, we tried to install a lot of programs like lynx for >> instance and we are getting trouble in the compiling. The problem is >> that we also wanted to compile such source which is not available >> in the package list. In the given directory we typed make install >> and then we are getting a lot of compilations and chekings and after >> few seconds( depending how long the source is) we are getting this >> message: > >> ***error code 1 >> STOP >> ***error code 1 >> STOP > >*sigh* Here are four free clues: > >1. Use a subject line on your message, like the one I've added. People > are likely to ignore messages with no subject. >2. Keep line lengths under 80 characters. I've rewrapped the lines. >3. Only post messages once. You posted this message three times, with only > minor differences between each. >4. When people give you good advice, act on it. Evren asked you to post > the entire error message you received. You haven't done this. > >There must have been something above the "*** error code 1" explaining >what caused the error. How about reading and/or posting that so people >might have a clue what's going wrong? > >You'd do well to read Greg Lehey's guidelines for posting to >freebsd-questions, there is a link from http://www.lemis.com/ > >-- >Ben Smithurst >ben@scientia.demon.co.uk > >send a blank message to ben+pgp@scientia.demon.co.uk for PGP key > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?029601be67ff$8fd64be0$416126c3>