public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <peter@humphrey.ukfsn.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problem compiling freemind
Date: Tue, 9 Feb 2010 00:50:54 +0000	[thread overview]
Message-ID: <201002090050.54695.peter@humphrey.ukfsn.org> (raw)
In-Reply-To: <5bdc1c8b1002081136h7a5a27d3r5e2dc94dc8663c80@mail.gmail.com>

On Monday 08 February 2010 19:36:49 Mark Knecht wrote:

> I actually meant to try the lower case L. Mine shows some ant stuff
> which I think you were having trouble with, at least in the compile
> messages?

Hmm. That gave me the clue; yes, freemind was throwing an ant error 
during compilation (but that didn't prevent emerge from reporting 
success), so I recompiled all the ant* packages on the system and that's 
fixed it.

Problem now is that I asked for ant-core, ant-nodeps, ant-trax and antlr 
to be remerged, but I saw this:

$ eix -I ant
...
[U] dev-java/antlr (2.7.7@22/01/10 -> 2.7.7{tbz2} 3.1.3-r2(3)): A parser 
generator for C++, C#, Java, and Python
...

That's a puzzle, because I'd only just run an emerge --sync and -uaDv 
world, so why was antlr not upgraded then?

The upgrade of antlr pulled in a new package, stringtemplate.

Whatever was wrong, reinstalling those four packages solved my problem. 
Thanks for the hint, Mark.

-- 
Rgds
Peter.



  reply	other threads:[~2010-02-09  1:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-07 14:46 [gentoo-user] Problem compiling freemind Peter Humphrey
2010-02-07 15:06 ` Mark Knecht
2010-02-07 15:25   ` Mark Knecht
2010-02-07 17:16   ` Peter Humphrey
2010-02-07 18:12     ` Mark Knecht
2010-02-07 23:57       ` Peter Humphrey
2010-02-08 19:36         ` Mark Knecht
2010-02-09  0:50           ` Peter Humphrey [this message]
2010-02-09  1:54             ` Mark Knecht
2010-02-08 13:05 ` Arttu V.
2010-02-08 19:29   ` Peter Humphrey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201002090050.54695.peter@humphrey.ukfsn.org \
    --to=peter@humphrey.ukfsn.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox