Re: cygport build injecting /usr/lib/gcc/x86_64-pc-cygwin/7.4.0/ paths
On 2021-11-15 06:09, Achim Gratz wrote: Brian Inglis writes: 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: I've pushed a different fix. If you can get libtool to build and update that would be great. I tried and failed there - configure failed to even generate a Makefile for me, trying a number of measures, including a clean setup. -- 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.] -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: cygport build injecting /usr/lib/gcc/x86_64-pc-cygwin/7.4.0/ paths
Brian Inglis writes: > 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: I've pushed a different fix. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: cygport build injecting /usr/lib/gcc/x86_64-pc-cygwin/7.4.0/ paths
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.] -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: cygport build injecting /usr/lib/gcc/x86_64-pc-cygwin/7.4.0/ paths
On 2021-11-12 16:42, Duncan Roe wrote: On Fri, Nov 12, 2021 at 01:25:48PM -0700, Brian Inglis wrote: Now should I patch /usr/bin/libtool, libtoolize the sources, cygautoreconf, or upgrade libtool? >> Anyone have any ideas for the best approach? Or just go for it and try each in turn in case something works? autoreconf -fi Tried cygport autotools.cygclass function cygautoreconf which does that but breaks the build. rm -Rf autom4te.cache (taken from autogen.sh in various netfilter prokects) No such file in use. Thanks for the suggestion! -- 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.] -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: cygport build injecting /usr/lib/gcc/x86_64-pc-cygwin/7.4.0/ paths
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. -- 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.] -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: cygport build injecting /usr/lib/gcc/x86_64-pc-cygwin/7.4.0/ paths
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. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: cygport build injecting /usr/lib/gcc/x86_64-pc-cygwin/7.4.0/ paths
On Fri, Nov 12, 2021 at 01:25:48PM -0700, Brian Inglis wrote: > On 2021-11-12 12:18, Ken Brown via Cygwin wrote: [...] > Now should I patch /usr/bin/libtool, libtoolize the sources, cygautoreconf, > or upgrade libtool? > Anyone have any ideas for the best approach? > Or just go for it and try each in turn in case something works? > autoreconf -fi rm -Rf autom4te.cache (taken from autogen.sh in various netfilter prokects) Cheers ... Duncan. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: cygport build injecting /usr/lib/gcc/x86_64-pc-cygwin/7.4.0/ paths
On 2021-11-12 12:18, Ken Brown via Cygwin wrote: On 11/12/2021 12:50 PM, Brian Inglis wrote: 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 Those paths come from /usr/bin/libtool. There's some discussion of this issue in https://mingw-users.narkive.com/Mx8FQPRf/libtool-hard-coded-paths , which even mentions the ncurses problem. I don't know enough about libtool to suggest the best solution, but probably others on the list do. Thanks Ken, That's the source of the symptom indeed! The package ncurses is pre-auto-tooled in that it appears to have everything setup so that configure reconfigs everything and generates the expected outputs. Now should I patch /usr/bin/libtool, libtoolize the sources, cygautoreconf, or upgrade libtool? Anyone have any ideas for the best approach? Or just go for it and try each in turn in case something works? -- 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.] -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: cygport build injecting /usr/lib/gcc/x86_64-pc-cygwin/7.4.0/ paths
On 11/12/2021 12:50 PM, Brian Inglis wrote: 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 Those paths come from /usr/bin/libtool. There's some discussion of this issue in https://mingw-users.narkive.com/Mx8FQPRf/libtool-hard-coded-paths , which even mentions the ncurses problem. I don't know enough about libtool to suggest the best solution, but probably others on the list do. Ken -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: cygport build injecting /usr/lib/gcc/x86_64-pc-cygwin/7.4.0/ paths
On Fri, Nov 12, 2021 at 10:50:41AM -0700, Brian Inglis wrote: > 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.] > Try env | grep -E 7\.4\.0 I had a kind-of similar problem from having LIBS in the environment. Otherwise on a freshly restored tarball before even running ./configure: find . -type f|xargs grep -E 7\.4\.0 find . -name '*7.4.0*' btw fgrep and egrep are retired at GNU grep 3.7
cygport build injecting /usr/lib/gcc/x86_64-pc-cygwin/7.4.0/ paths
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.] -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
