From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: Andreas Enge <andreas@enge.fr>
Cc: 54928@debbugs.gnu.org
Subject: bug#54928: Libtool 2.4.6 vs. 2.4.7
Date: Thu, 14 Apr 2022 14:25:23 +0200 [thread overview]
Message-ID: <b1e483ca81870d16b0a9593e0d1090fceb9097ac.camel@ist.tugraz.at> (raw)
In-Reply-To: <YlgOZqog/H2MKjxN@jurong>
Am Donnerstag, dem 14.04.2022 um 14:07 +0200 schrieb Andreas Enge:
> > > I have installed libtool@2.4.7 into my profile
> > That is a mistake.
> >
> > > as well as a number of other development tools
> > Probably also a mistake.
>
> Could you elaborate why? If you work on a project, it seems necessary
> to install development tools (gcc-toolchain, autoconf, automake,
> make, texinfo, ...).
True, but to keep adverse effects resulting from environment mixing to
a minimum, you would typically only use those inside ‘guix environment’
(now ‘guix shell’) and refrain from global installation. See also a
number of talks suggesting you put a ‘guix.scm’ file into the project
root directory for this very purpose.
> > I think the problem is caused in the ../libtool symlink, which is
> > probably not updated to reflect your installation. This is a known
> > issue with stale build files, which also happens if you garbage-
> > collect stuff. distclean or maintainerclean should solve your
> > issue. Or you might just as well delete the symlink manually :)
>
> I had already removed it, and the problem persisted. I suppose that
> autoreconf or configure created it again in version 2.4.6, and during
> make my version 2.4.7 was used instead.
I'm not sitting in front of your computer, so I can hardly estimate
what has already been expanded where. However, the typical flow should
go like this:
1. autoreconf pulls missing files from your libtool into the auxiliary
directory (typically build-aux).
2. configure detects your libtool and configures it according to the
configuration options you pass.
3. make invokes libtool -- if make detects the Makefile itself to be
old, it might restart from 2.
In any case, the error points towards autoreconf not using 2.4.6, but
2.4.7 as base, i.e. an error in step (1). Maybe you forgot to run it?
Also, never run autoreconf without -v, it stands for "very important".
As a general rule, the GNU build system does not provide a tooclean
target for make.
Cheers
prev parent reply other threads:[~2022-04-14 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 9:53 bug#54928: Libtool 2.4.6 vs. 2.4.7 Andreas Enge
2022-04-14 11:29 ` Liliana Marie Prikler
2022-04-14 12:07 ` Andreas Enge
2022-04-14 12:22 ` Andreas Enge
2022-04-14 12:25 ` Liliana Marie Prikler [this message]
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=b1e483ca81870d16b0a9593e0d1090fceb9097ac.camel@ist.tugraz.at \
--to=liliana.prikler@ist.tugraz.at \
--cc=54928@debbugs.gnu.org \
--cc=andreas@enge.fr \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.