From: marco atzeri <marco.atzeri@gmail.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated: octave-5.1.0-1
Date: Wed, 15 Jan 2020 10:36:00 -0000 [thread overview]
Message-ID: <CAB8Xom8jcmGygD23dO5MEvBqyTmx1MUTjEc9B9kHFD=V9NXE_Q@mail.gmail.com> (raw)
In-Reply-To: <20200115190839.20c9104734968c17690830a9@nifty.ne.jp>
On Wed, 15 Jan 2020, 11:09 Takashi Yano, wrote:
> On Mon, 13 Jan 2020 21:02:46 +0100
> Marco Atzeri wrote:
> > New versions 5.1.0-1 of
> > octave
> > octave-devel
> > octave-doc
> > are available in the Cygwin distribution:
>
> After upgrading octave and octave-devel to 5.1.0-1,
> mkoctfile stopped working with error:
> /usr/lib/gcc/i686-pc-cygwin/7.4.0/../../../../i686-pc-cygwin/bin/ld:
> cannot find -loctinterp
> /usr/lib/gcc/i686-pc-cygwin/7.4.0/../../../../i686-pc-cygwin/bin/ld:
> cannot find -loctave
> collect2: error: ld returned 1 exit status
>
> It seems that option -L/usr/lib/octave/5.1.0, which should be added
> by default, is missing.
>
> If -L option is added manually, it works as expected.
>
> --
> Takashi
>
This is an upstream change, it was a surprise also for me the first time.
You can use pkg-config for a proper settings of LDFLAGS and use it in your
makefiles.
Most forge packages were modified to handle this change.
Regards
Marco
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2020-01-15 10:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 20:14 Marco Atzeri
2020-01-15 10:08 ` Takashi Yano
2020-01-15 10:36 ` 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='CAB8Xom8jcmGygD23dO5MEvBqyTmx1MUTjEc9B9kHFD=V9NXE_Q@mail.gmail.com' \
--to=marco.atzeri@gmail.com \
--cc=cygwin@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).