From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: libtool not finding /usr/lib/libintl.la or what?
Date: Sat, 01 Jul 2017 07:29:00 -0000 [thread overview]
Message-ID: <2dd41143-617a-4695-5a6d-e5bb9ce8f625@gmail.com> (raw)
In-Reply-To: <Pine.BSF.4.63.1707010013510.96361@m0.truegem.net>
On 01/07/2017 09:18, Mark Geisert wrote:
> On Sat, 1 Jul 2017, Marco Atzeri wrote:
>> On 01/07/2017 07:47, Mark Geisert wrote:
>>> Esteemed co-conspirators,
>>> I've been pulling my hair out trying to build a new cygutils package on
>>> 32-bit Cygwin. The exact same source package builds fine on 64-bit but
>>> 32-bit fails with the following...
>>>
>>> CC src/ipc/semstat.o
>>> CXX src/cygdrop/src_cygdrop_cygdrop-cygdrop.o
>>> CCLD src/cygicons/libicons.la
>>> CCLD src/banner/banner.exe
>>> libtool: error: cannot find the library '/usr/lib/libintl.la' or
>>> unhandled argument '/usr/lib/libintl.la'
>>
>> it is pulled by /usr/lib/libpopt.la.
>>
>>
>> try
>>
>> $ cd /usr/lib
>> $ mv libpopt.la libpopt.la_bk
>>
>> and run again make in build
>
> Amazing. That does work. But what is the correct way to deal with this
> when some random user wants to build 32-bit cygutils from source?
> Should the build procedure actually do what you suggested? I could not
> figure out which package supplies (or used to supply) libintl.la for 32
> bits.
> Thanks much,
>
> ..mark
we should remove the not needed /usr/lib/*.la (not all)
as we did from start on the 64bit version
prev parent reply other threads:[~2017-07-01 7:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-01 5:50 Mark Geisert
2017-07-01 6:46 ` Marco Atzeri
2017-07-01 7:18 ` Mark Geisert
2017-07-01 7:29 ` Marco Atzeri [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=2dd41143-617a-4695-5a6d-e5bb9ce8f625@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-apps@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).