make -D recent problem?

[Kris Kennaway]

On Thu, May 03, 2007 at 03:14:58PM -0300, JoaoBR wrote:
> 
> 
> On Thursday 03 May 2007 15:00:24 Kris Kennaway wrote:
> > On Thu, May 03, 2007 at 02:43:43PM -0300, JoaoBR wrote:
> > > On Thursday 03 May 2007 14:23:13 Kris Kennaway wrote:
> > > > > > > I guess this is a port configuration problem because certainly
> > > > > > > others need them too but did not have this problem, only
> > > > > >
> > > > > > No, it's because something is stale on your system and needs to be
> > > > > > rebuilt.
> > > > >
> > > > > I dont know, look
> > > > >
> > > > > # pkg_info -L gtk-2\* | grep libgdk-x11
> > > > > /usr/local/lib/libgdk-x11-2.0.a
> > > > > /usr/local/lib/libgdk-x11-2.0.la
> > > > > /usr/local/lib/libgdk-x11-2.0.so
> > > > > /usr/local/lib/libgdk-x11-2.0.so.0
> > > > >
> > > > > this files are not beeing installed in /usr/X11R6/lib
> > > > >
> > > > > but some ports are looking there and not in /usr/local/lib
> > > >
> > > > Right, my suggestion quoted at the top of this email was an
> > > > instruction for figuring out which these "some ports" are.
> > >
> > > well
> > > as you can see gtk2 is installing them into /usr/local/lib
> > >
> > > but some ports are looking in /usr/X11R6/lib
> > >
> > > that is the reason we I am saying that the is something wrong in some
> > > port configurations
> >
> > OK, I was willing to help you figure this out, but you've ignored my
> > instructions 3 times now, so I'm giving up and will let you deal with
> > it on your own.
> >
> 
> whatt?
> 
> you're very funny, sure I did
> seems you do not read with attention

Probably it is because English is not your first language, but you
really did not follow my instructions.

If you had followed them, your email would contain the results of your
grep -r command.  This command would show which ports refer to the
incorrect /usr/X11R6 location, and I would have helped you to figure
out which ports they belong to.  Rebuilding those ports is all that is
necessary to fix your problem, but first you have to identify which
ports they are.

> but no problem since the problem *is* solved thanks to your help

By doing the ln -s you worked around the problem but didn't solve it.
There might be other problems later on.

Kris