public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: cygport build injecting /usr/lib/gcc/x86_64-pc-cygwin/7.4.0/ paths
Date: Sun, 14 Nov 2021 15:07:45 -0700	[thread overview]
Message-ID: <ac00dcf4-dc8b-5522-06ad-19ca3b1ae00e@SystematicSw.ab.ca> (raw)
In-Reply-To: <47af4ee4-c63a-13b3-b6fa-2ee792b84120@SystematicSw.ab.ca>

On 2021-11-14 06:49, Brian Inglis wrote:
> On 2021-11-14 05:48, Achim Gratz wrote:
>> Brian Inglis writes:
>>> Got these errors trying to build latest ncurses on my system, so
>>> retried on scallywag and got same result, with no clue where that is
>>> coming from!
> 
>> Unless there is absolutely no other way and you know exactly what you're
>> doing, never skip the cygautoreconf in src_compile.
> 
> I always try to use the default src_compile autotools.cygclass function 
> where possible to ensure that is the case.
> Various GNU tool builds have that commented out by their previous 
> experienced maintainers, so I tread carefully.
> I do try to re-add the cygautoreconf function and comment out the 
> src_compile function override where possible even in those cases.
> I leave the commented out version in place to document the possibility 
> that re-trying a build without cygautoreconf may fix issues.
> 
> In this case, all such alternatives (cygautoreconf, libtoolize, lndirs) 
> tried either had no effect or broke the builds, which as I said, seem to 
> have all the autoconf and automake files pre-generated, so that cygconf 
> and cygmake should work, given a functional libtool.
> 
> I have also tried to rebuild libtool from sources to pick up updates, 
> but that cygport build no longer even generates a Makefile!
> However I notice that the tar contains a slew of .file temporaries that 
> may be messing up that build.

Only approach that worked was to write a script to update 
/usr/bin/libtool to latest /usr/lib/gcc/$HOSTTYPE-*-$OSTYPE/[0-9]* path, 
add to SRC_URI, and run at the start of src_compile:

https://cygwin.com/git/?p=git/cygwin-packages/ncurses.git;a=tree;hb=playground

https://cygwin.com/cgi-bin2/jobs.cgi?id=3533&srcpkg=ncurses&status=succeeded&user=Brian+Inglis

https://github.com/cygwin/scallywag/actions/runs/1459727318

https://github.com/cygwin/scallywag/suites/4351117248/logs?attempt=1

I will make this an ITA to update ncurses if there are no better 
alternatives suggested to the unconventional approach.
I will then look at how to build the mingw64-*86*-ncurses versions and 
ITA those.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

  reply	other threads:[~2021-11-14 22:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-12 17:50 Brian Inglis
2021-11-12 18:50 ` Duncan Roe
2021-11-12 19:18 ` Ken Brown
2021-11-12 20:25   ` Brian Inglis
2021-11-12 23:42     ` Duncan Roe
2021-11-14 14:18       ` Brian Inglis
2021-11-14 12:48 ` Achim Gratz
2021-11-14 13:49   ` Brian Inglis
2021-11-14 22:07     ` Brian Inglis [this message]
2021-11-15 13:09       ` Achim Gratz
2021-11-16  5:24         ` Brian Inglis

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=ac00dcf4-dc8b-5522-06ad-19ca3b1ae00e@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).