On Thu, 2007-10-18 at 15:47 -0400, Lisandro Grullon wrote: > Hi James, > I follow your advise and even try upgrading the port recursively using > portmaster -rf evolution-data-server , I think the port is broken for > AMD64, I have been trying so many things without any success. Please > advise. Lisandro Grullon > > > > > > > > ______________________________________________________________ > Subject: RE: Evolution-data-server compiling errors. > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > CC: email@example.com > Date: Thu, 18 Oct 2007 12:50:12 -0600 > > Hi Lisandro, > > just a quick note - use "reply to all" or whatever the > equivalent feature is in hotmail. Right now, you've only > replied to *me*, not to both me and the list. I have copied > the list on this email, so in future just use "reply to all". > > It's great that you're keeping the ports tree up to date. Are > you also running a portupgrade regularly? If so, great, if > not: > > portupgrade -a > > > Make *sure* that you read /usr/ports/UPDATING *before* running > the portupgrade and follow any relevant instructions. > > -------- > > If you're portupgrading regularly, are you trimming leaf ports > regularly? If so, great. If not, someone else will have to > recommend a best way to clean leaf ports. > > > ----- > > If you're doing all this, try out: > pkg_info -Ix evolution-data-server > > This will output a package and its version number. Now try: > > portupgrade -rf <whatever that package name and number were> > > > This forces a recursive upgrade of that package. > > > > > > On Thu, 2007-10-18 at 14:34 -0400, Lisandro Grullon wrote: > > Hi James, > > > Yes my port tree is very up to date, I upgrade it > daily. I still puzzle by the errors compiling > evolution, I am using 6.2-R in a AMD 64 system. > > > > > > > ______________________________________________ > > Subject: Re: Evolution-data-server compiling > errors. > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > CC: firstname.lastname@example.org > Date: Thu, 18 Oct 2007 09:07:48 -0600 > > Hey Lisandro, > > I snipped out your log, if that confuses > anyone reading, please be aware there was a > large log file here. > > > First things first: is you ports tree up to > date? > > James > > > > ______________________________________________________ > > Boo! Scare away worms, viruses and so much more! Try > Windows Live OneCare! Try now! > > > > ______________________________________________________________________ > Climb to the top of the charts! Play Star Shuffle: the word scramble > challenge with star power. Play Now!
Hi Lisandro, two things: 1) Please don't top-post. This means that when you hit reply, scroll down to the *bottom* to post your response. The reason for this is so that anyone coming along who might be able to help you will be able to read the entire email conversation in the order it was given. It helps other people help you! :) 2) If you truly believe the port is broken, you have several options: a) write to the port maintainer, if it has one, describing your issue. b) fix the issue and write to the port maintainer with the patch. c) If the port has no maintainer, write to the freebsd-ports mailing list and see if you can get any assistance there. PLEASE note that there, as here, you'll encounter volunteers. So if no one answers, then your only real option is to sit down and work on the port yourself. James _______________________________________________ email@example.com mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"