On 20/3/06, Carlos Eduardo de Brito Novaes wrote:
>Are you moving packages like this for any special reason? I mean, seens to
> require some knowledgment that would be very usefull for a package management
> system (an old project that I never had the time to study and implement). ;)
> Would you be
On Thursday 23 March 2006 09:36, Simon Geard wrote:
> On Wed, 2006-03-22 at 06:25 -0600, Randy McMurchy wrote:
> > You can't expect the developers to compare their software against
> > what other software does. We can only expect that the developers
> > adequately document what their software does,
On Wed, 2006-03-22 at 06:25 -0600, Randy McMurchy wrote:
> You can't expect the developers to compare their software against
> what other software does. We can only expect that the developers
> adequately document what their software does, and how to use it. And
> in this case, I believe they do.
> Yes, thank you for the detailed explanation! That's why I joined the
> LFS/CLFS/BLFS community. It's the best place to advance your knowledge of
> computer programming and OS operation.
>
> Shame the developers of those tools couldn't explain it so well.
Well, well. I keep on learning too. Every
On Wed, 2006-03-22 at 05:49 +, John Gay wrote:
> > On 3/22/06, Simon Geard <[EMAIL PROTECTED]> wrote:
> > > Actually, they do cover different problems, although there is some
> > > overlap. Libtool is fairly specialised towards the task of hiding the
> > > differences in the build process that
On Wednesday 22 March 2006 10:29, Lennon Cook wrote:
> On 3/22/06, Simon Geard <[EMAIL PROTECTED]> wrote:
> > Actually, they do cover different problems, although there is some
> > overlap. Libtool is fairly specialised towards the task of hiding the
> > differences in the build process that exist
On 3/22/06, Simon Geard <[EMAIL PROTECTED]> wrote:
> Actually, they do cover different problems, although there is some
> overlap. Libtool is fairly specialised towards the task of hiding the
> differences in the build process that exist on different platforms, e.g
> Windows vs Linux vs HP-UX vs Op
On Tue, 2006-03-21 at 23:16 +1100, Lennon Cook wrote:
> It strikes me that pkg-config does everything
> libtool does, just in more general ways, and so I don't see a need for
> any package to use *both*.
Actually, they do cover different problems, although there is some
overlap. Libtool is fairly
On 3/20/06, Lennon Cook <[EMAIL PROTECTED]> wrote:
>Now that I'm beggining to understand how it works,
> libtool (and, for that matter, pkg-config) strikes me as a horrid
> kludge, but I don't think theres any real alternative. My symlinks are
> also kludgy, but I believe them to be slightly less s
On 3/20/06, Carlos Eduardo de Brito Novaes <[EMAIL PROTECTED]> wrote:
> Em Sábado 18 Março 2006 21:56, Lennon Cook escreveu:
> > And so the question becomes - what would be the best course
> > of action here? Is it safe to just adjust the paths in this file, or
> > would I be better to recompile GT
Em Sábado 18 Março 2006 21:56, Lennon Cook escreveu:
> And so the question becomes - what would be the best course
> of action here? Is it safe to just adjust the paths in this file, or
> would I be better to recompile GTK with glib living in /opt?
I dont really think it is necessary to recompile a
Carlos Eduardo de Brito Novaes wrote:
> If you are moving these files to /opt/foo, I think you must pass a:
> LDFLAGS=$LDFLAGS -L/opt/foo/lib -L/opt/lib/foo1.../lib
> for each package you install and this really seens ugly.
I'm already seeing things like this passed straight to LD in my logs,
a
Hello.
As far as I know, .la files are text files created by libtool. They give
information about a library such as libungif.la is about libungif.so.
They are needed to a new software to check the existence, path, version and
dependencies (flags) of this library.
In the past, I had to change so
I have recently taken to moving many pieces of my system into /opt . I
have come across an annoying little problem with *.la files when I'm
doing this - Specifically, when I install a package which includes
*.la files, no other package that depends on those files can find them
there. Is there an en
14 matches
Mail list logo
