public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] libexif-0.6.22-1
Date: Thu, 31 Dec 2020 09:44:10 +0100	[thread overview]
Message-ID: <87eej6pdph.fsf@Rainer.invalid> (raw)
In-Reply-To: <20201231170440.4EB5.50F79699@gmail.com> (Lemures Lemniscati via Cygwin-apps's message of "Thu, 31 Dec 2020 17:04:41 +0900")

Lemures Lemniscati via Cygwin-apps writes:
> exif is troublesome:
>
>   i686 build failed on my local machine,
>   while it's successfully built on AppVeyor CI.

If it's not due to fork errors, then I'd suspect some difference in the
way Windows itself is set up.

> I've reinstalled cygwin32 and tried again, but the results are same.

A reinstallation is unlikely to do anything useful unless you suspect
that you've messed it up previously.  You can trigger a full rebase once
in a while, although I haven't needed that in a long time.

My recommendation is still to keep the (32bit and 64bit) Cygwin
installations that you use for packaging separate from the one you do
any daily work in and keep them in a second-level directory of a
physical drive (like D:\Freeware\Cygwin32).  Do not use any /cygdrive
resources, instead mount everything you need via /etc/fstab.d/builduser.
Keep any locale settings as plain as possible.

>   CCLD     exif.exe
> libtool:   error: cannot find the library '/usr/lib/libintl.la' or unhandled argument '/usr/lib/libintl.la'

Next time you might want to run that again with "V=1" or whatever
invocation removes the cloaking of the linker command line and see if
that gives you a better clue as to what is the problem here.

So it turns out to fail the same on my system locally… and if you look
into .appveyor.yaml you'll find this little nugget:

--8<---------------cut here---------------start------------->8---
# Work around a libpopt-devel-1.16-2 packaging issue that causes the error:
#   libtool: error: cannot find the library '/usr/lib/libintl.la' or unhandled argument '/usr/lib/libintl.la'
# See http://www.cygwin.com/ml/cygwin-apps/2017-07/msg00005.html
- cmd: if [%CONFIG%]==[cygwin] (
    C:\%CONFIG%\bin\bash -e -l -c "rm /usr/lib/libpopt.la" )
--8<---------------cut here---------------end--------------->8---

…and indeed that makes things work.  :-)


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

  reply	other threads:[~2020-12-31  8:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-30 23:33 Lemures Lemniscati
2020-12-31  2:07 ` Lemures Lemniscati
2020-12-31  8:04   ` Lemures Lemniscati
2020-12-31  8:44     ` Achim Gratz [this message]
2020-12-31  8:49       ` Achim Gratz
2020-12-31  9:32         ` Lemures Lemniscati
2020-12-31 10:54           ` Lemures Lemniscati
2020-12-31 15:44             ` Marco Atzeri
2020-12-31 22:22               ` Lemures Lemniscati
2021-01-02 22:13                 ` Achim Gratz
2021-01-03  2:46                   ` Lemures Lemniscati
2021-01-03  3:22                     ` Marco Atzeri
2021-01-03  9:51                     ` Achim Gratz
2021-01-04 13:58                       ` Lemures Lemniscati

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=87eej6pdph.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).