Re: libtool ignorant of lack of headers in /usr

[Carol Spears]

good morning libtool bugs,
On Tue, Oct 18, 2005 at 09:56:49AM +0200, Ralf Wildenhues wrote:
> 
> Nonono.  Read again:
>    Go to the directory where `pangoft2topgm' should be created.[1]
> 
> Then execute all the other stuff again.  I could not find any typos in
> my instructions yet, so please wash, rinse, repeat, report back.
> 
okay, i am sorry about the accusations and embarrassed by my previous
attachments.

i gave up.  i spent one evening without gui building everything i needed
and everything went well.  current cvs or svn versions of all that stuff
are not very unstable or difficult to install.

if i type what you say right now, all will go well.

i should apologize for taking your time like i did, when all i wanted
was to be able to build new stuff while still using the old stuff.  i am
sorry.  it is however a change in how things work and i am still left
with so many questions about the change.

this is a maillist dedicated to fixing libtool-bugs.  just because i
consider it a bug does not mean everyone else will.  especially if
everyone who fixes the bugs is getting their mail, chatting, authoring
software and even receiving therapy via emacs and does not see the need
for a nice desktop to watch all that stuff with.  this is where i
apologize that vi was the option given to me when i first started and at
that time, i had to learn latex to be able to turn in a paper first and
perhaps did not have the time to learn a complicated keyboard driven
text editor.

my main question now is where do i find the answers to the following
questions:
how come libtool changed the way it works?  even if i cannot prove it to
the libtool-bugs maillist, it did change.  i would like to understand
what caused the change.

what purpose do the files with the extension .la have?  it was suggested
to me to remove them.  this idea is very appealing because of these
libtool issues and also because of my respect for the person who
suggested it.

on the lighter side, i don't know how many of you are building software
in the standard sized xterm window -- but, newer autotools is drawing a
very funny picture in the warnings; it is extremely entertaining to me.
not a bug at all :)


> *snipped all useless output*
> 
yeah. [b]

carol [c]

> 
> [1] That is not necessarily the directory where you typed `make' before
> reporting this bug.  I cannot know for certain in which directory you
> typed `make', so I'm not trying to infer it.  GNU make helps you though,
> to find out where `pangoft2topgm' should be created: it usually prints
> the directory names when entering or leaving them. 
  
  yes, i read it but i do not understand it.  at least you can tell from
  my attempt i know which directory i am working in.  what i did not
  know was that you were asking questions about that one little part of
  the build.  i am sorry i wasted both of our time.


[b] nothing infuriates/frustrates me more than having a build break on a 
test.  having said that, i have no idea if i even use pgm or not and i did 
not see if i could disable the tests in ./configure --help

[c] while i was pasting spew to attach to the mail yesterday, i had a
nice flashback to my dad grabbing a book, announcing he would be in the
library and heading off to the lavoratory (bathroom, water closet, etc)
for an undefinable amount of time.  i wonder how i got the feeling i was
hanging out in the mens room when i subscribed to this list?