From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: cygport build injecting /usr/lib/gcc/x86_64-pc-cygwin/7.4.0/ paths
Date: Fri, 12 Nov 2021 10:50:41 -0700 [thread overview]
Message-ID: <9b0f1bad-1fde-1ed0-a454-409be5c97c10@SystematicSw.ab.ca> (raw)
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!
There are no files in the tarball, repo, or build dirs containing 7.4.0
but it looks suspiciously like the package version 6.3.0 incremented!
Anyone ever seen these kinds of artifacts, or aware of any code doing
this kind of incrementing?
$ fgrep 7.4.0 scallywag/*86*/6_Build\ packages.log
scallywag/i686/6_Build packages.log:2021-11-12T09:54:57.1027256Z
libtool: link: g++ -shared -nostdlib
/usr/lib/gcc/i686-pc-cygwin/7.4.0/crtbeginS.o ../obj_lo/.libs/cursesf.o
../obj_lo/.libs/cursesm.o ../obj_lo/.libs/cursesw.o
../obj_lo/.libs/cursespad.o ../obj_lo/.libs/cursesp.o
../obj_lo/.libs/cursslk.o ../obj_lo/.libs/cursesapp.o
../obj_lo/.libs/cursesmain.o
-L/cygdrive/d/a/scallywag/ncurses/ncurses-6.3-1.20211106.i686/build/lib/.libs
-L../lib
/cygdrive/d/a/scallywag/ncurses/ncurses-6.3-1.20211106.i686/build/lib/.libs/libformw.dll.a
/cygdrive/d/a/scallywag/ncurses/ncurses-6.3-1.20211106.i686/build/lib/.libs/libmenuw.dll.a
/cygdrive/d/a/scallywag/ncurses/ncurses-6.3-1.20211106.i686/build/lib/.libs/libpanelw.dll.a
../lib/.libs/libformw.dll.a ../lib/.libs/libmenuw.dll.a
../lib/.libs/libpanelw.dll.a
/cygdrive/d/a/scallywag/ncurses/ncurses-6.3-1.20211106.i686/build/lib/.libs/libncursesw.dll.a
../lib/.libs/libncursesw.dll.a -lutil
-L/usr/lib/gcc/i686-pc-cygwin/7.4.0
-L/usr/lib/gcc/i686-pc-cygwin/7.4.0/../../../../i686-pc-cygwin/lib
-L/usr/lib/gcc/i686-pc-cygwin/7.4.0/../../.. -lstdc++ -lgcc_s -lgcc
-lcygwin -ladvapi32 -lshell32 -luser32 -lkernel32 -lgcc_s -lgcc
/usr/lib/gcc/i686-pc-cygwin/7.4.0/crtend.o -ggdb -O2
-fstack-protector-strong -o .libs/cygncurses++w-10.dll
-Wl,--enable-auto-image-base -Xlinker --out-implib -Xlinker
.libs/libncurses++w.dll.a
scallywag/i686/6_Build packages.log:2021-11-12T09:54:57.1848593Z
/usr/lib/gcc/i686-pc-cygwin/11/../../../../i686-pc-cygwin/bin/ld: cannot
find /usr/lib/gcc/i686-pc-cygwin/7.4.0/crtbeginS.o: No such file or
directory
scallywag/i686/6_Build packages.log:2021-11-12T09:54:57.3516554Z
/usr/lib/gcc/i686-pc-cygwin/11/../../../../i686-pc-cygwin/bin/ld: cannot
find /usr/lib/gcc/i686-pc-cygwin/7.4.0/crtend.o: No such file or directory
scallywag/x86_64/6_Build packages.log:2021-11-12T09:52:54.1343744Z
libtool: link: g++ -shared -nostdlib
/usr/lib/gcc/x86_64-pc-cygwin/7.4.0/crtbeginS.o
../obj_lo/.libs/cursesf.o ../obj_lo/.libs/cursesm.o
../obj_lo/.libs/cursesw.o ../obj_lo/.libs/cursespad.o
../obj_lo/.libs/cursesp.o ../obj_lo/.libs/cursslk.o
../obj_lo/.libs/cursesapp.o ../obj_lo/.libs/cursesmain.o
-L/cygdrive/d/a/scallywag/ncurses/ncurses-6.3-1.20211106.x86_64/build/lib/.libs
-L../lib
/cygdrive/d/a/scallywag/ncurses/ncurses-6.3-1.20211106.x86_64/build/lib/.libs/libformw.dll.a
/cygdrive/d/a/scallywag/ncurses/ncurses-6.3-1.20211106.x86_64/build/lib/.libs/libmenuw.dll.a
/cygdrive/d/a/scallywag/ncurses/ncurses-6.3-1.20211106.x86_64/build/lib/.libs/libpanelw.dll.a
../lib/.libs/libformw.dll.a ../lib/.libs/libmenuw.dll.a
../lib/.libs/libpanelw.dll.a
/cygdrive/d/a/scallywag/ncurses/ncurses-6.3-1.20211106.x86_64/build/lib/.libs/libncursesw.dll.a
../lib/.libs/libncursesw.dll.a -lutil
-L/usr/lib/gcc/x86_64-pc-cygwin/7.4.0
-L/usr/lib/gcc/x86_64-pc-cygwin/7.4.0/../../../../x86_64-pc-cygwin/lib/../lib
-L/usr/lib/gcc/x86_64-pc-cygwin/7.4.0/../../../../lib -L/lib/../lib
-L/usr/lib/../lib
-L/usr/lib/gcc/x86_64-pc-cygwin/7.4.0/../../../../x86_64-pc-cygwin/lib
-L/usr/lib/gcc/x86_64-pc-cygwin/7.4.0/../../.. -lstdc++ -lgcc_s -lgcc
-lcygwin -ladvapi32 -lshell32 -luser32 -lkernel32 -lgcc_s -lgcc
/usr/lib/gcc/x86_64-pc-cygwin/7.4.0/crtend.o -ggdb -O2
-fstack-protector-strong -o .libs/cygncurses++w-10.dll
-Wl,--enable-auto-image-base -Xlinker --out-implib -Xlinker
.libs/libncurses++w.dll.a
scallywag/x86_64/6_Build packages.log:2021-11-12T09:52:54.2146113Z
/usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld:
cannot find /usr/lib/gcc/x86_64-pc-cygwin/7.4.0/crtbeginS.o: No such
file or directory
scallywag/x86_64/6_Build packages.log:2021-11-12T09:52:54.4873238Z
/usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld:
cannot find /usr/lib/gcc/x86_64-pc-cygwin/7.4.0/crtend.o: No such file
or directory
--
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.]
next reply other threads:[~2021-11-12 17:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 17:50 Brian Inglis [this message]
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
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=9b0f1bad-1fde-1ed0-a454-409be5c97c10@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).