public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Lemures Lemniscati <lemures.lemniscati@gmail.com>
To: cygwin@cygwin.com
Subject: Re: libtool-2.4.6 needs to be rebuilt for gcc-10
Date: Sat, 29 May 2021 15:07:36 +0900	[thread overview]
Message-ID: <20210529150735.5969.50F79699@gmail.com> (raw)
In-Reply-To: <20210529123138.8DA7.50F79699@gmail.com>

On Sat, 29 May 2021 12:31:41 +0900, Lemures Lemniscati
> Hi!
> 
> libtool needs to be rebuilt for gcc-10,
> since libtool-2.4.6-7 (current) is built for gcc-7.4.0.
> 
> I tried to rebuild it, but some tests failed on an x86_64 build.
> 
> 
> --
> Here attached a set of files, which might be a candidate for cygport.
> It is also placed at a personal playground [2] forked from [1].
> 
> A local build from it is placed at [3].
> 
> Release number is set to '9', because it is '8' at a current master
> branch (commit 3486306) in the cygwin-packages repository of libtool [1]. 
> 
> [1]: https://www.cygwin.com/git/?p=git/cygwin-packages/libtool.git
> [2]: https://github.com/cygwin-lem/libtool-cygport/tree/n_2.4.6-9
> [3]: https://github.com/cygwin-lem/libtool-cygport/tree/n_2.4.6-9_gh-pages
>      or https://cygwin-lem.github.io/libtool-cygport/index.html
> 
> --
> But in cygport test, an x86_64 build brings unexpected failures as in
> 
>   https://ci.appveyor.com/project/cygwin/scallywag/builds/39372313/job/qjaaymd2s4ts9dly#L717
> 
> > Linking and loading.
> >  27: link against a preloaded static library         ok
> >  28: build and dynamically load a module             FAILED (demo.at:406)
> >  29: preload static and dynamic module               FAILED (demo.at:423)
> >  30: deplibs_check_method                            ok
> >  31: disable fast install                            FAILED (demo.at:485)
> >  32: force PIC objects                               FAILED (demo.at:501)
> >  33: force non-PIC objects                           skipped (demo.at:535)
> >  34: hardcoding library path                         FAILED (demo.at:612)
> >  35: binary relinking at install time                FAILED (demo.at:720)
> >  36: uninstalled libraries have priority             FAILED (demo.at:791)
> >  37: linking with long file names                    FAILED (demo.at:978)
> >  38: override pic_flag at configure time             ok
> >  39: test --with-pic                                 skipped (with-pic.at:39)

I've pushed a cygport working tree on my local machine [4] just after

  PATH=/usr/bin cygport libtool.cygport test

[4]: https://github.com/cygwin-lem/libtool-cygport/tree/n_2.4.6-9_tests

Could anyone help me?

Lem


      reply	other threads:[~2021-05-29  6:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-29  3:31 Lemures Lemniscati
2021-05-29  6:07 ` Lemures Lemniscati [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=20210529150735.5969.50F79699@gmail.com \
    --to=lemures.lemniscati@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).