Re: [Fink-users] Failed: phase compiling: libjasper.1-1.900.1-6 failed
Yup:( On Thu, 2 Jul 2015 06:59:02 -0700, David Lowe wrote: Did this get lost in the future-proof shuffle? > > On 2015 Jun 11, at 4:27 AM, David Lowe wrote: > > > On 2015 Jun 1, at 10:38 PM, Daniel Macks wrote: > > autoreconf -fi > /sw/bin/libtoolize: line 3601: /sw/bin/grep: No such file or directory > >> >> First sign of trouble is there...fink's libtoolize is > hardcoding fink's grep but then not finding it, so it will fail to > accomplish whatever sed actions it would do. What version of > "libtool2" do you have installed? > > > $ fink list libtool2 > > Information about 12297 packages read in 2 seconds. > > i libtool2 2.4.6-2 Shared library build helper, v2.x > > i libtool2-shlibs 2.4.6-2 Shared libraries for libtool, v2.x > > /bin/sh ../../../libtool --tag=CC --mode=compile gcc > -DHAVE_CONFIG_H -I. -I../../../src/libjasper/include/jasper > -I../../../src/libjasper/include -I/sw/include -g -O2 -MT > jas_debug.lo -MD -MP -MF .deps/jas_debug.Tpo -c -o jas_debug.lo > jas_debug.c > ../../../libtool: line 917: X--tag=CC: command not found > ../../../libtool: line 917: X--tag=CC: command not found > ../../../libtool: line 950: libtool: ignoring unknown tag : > command not found > ../../../libtool: line 917: X--mode=compile: command not found > ../../../libtool: line 950: libtool: ignoring unknown tag : > command not found > ../../../libtool: line 917: X--mode=compile: command not found > >> >> This is all a symptom of the autoconf/libtool toolchain not > getting created properly, which seems like it would be consistent > with it failing to sed. Does installing fink's "sed" package resolve > it? That only hides the fact that your libtoolize is looking for it, > but at least would get you moving forward. > > > I already have it [4.2.2-1]. Looks like it's an uncontrolled use of fink's grep command. Installing the "grep" package, or rebuilding libtool2 without it installed, should solve it. It's a packaging bug in libtool2, maintainer notified, that probably would affect many packages. dan -- Daniel Macks dma...@netspace.org -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ Fink-users mailing list Fink-users@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.macosx.fink.user Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-users
Re: [Fink-users] Failed: phase compiling: libjasper.1-1.900.1-6 failed
Did this get lost in the future-proof shuffle? On 2015 Jun 11, at 4:27 AM, David Lowe wrote: > On 2015 Jun 1, at 10:38 PM, Daniel Macks wrote: > autoreconf -fi /sw/bin/libtoolize: line 3601: /sw/bin/grep: No such file or directory >> >> First sign of trouble is there...fink's libtoolize is hardcoding fink's grep >> but then not finding it, so it will fail to accomplish whatever sed actions >> it would do. What version of "libtool2" do you have installed? > > $ fink list libtool2 > Information about 12297 packages read in 2 seconds. > i libtool22.4.6-2Shared library build helper, v2.x > i libtool2-shlibs 2.4.6-2Shared libraries for libtool, v2.x > /bin/sh ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../../src/libjasper/include/jasper -I../../../src/libjasper/include -I/sw/include -g -O2 -MT jas_debug.lo -MD -MP -MF .deps/jas_debug.Tpo -c -o jas_debug.lo jas_debug.c ../../../libtool: line 917: X--tag=CC: command not found ../../../libtool: line 917: X--tag=CC: command not found ../../../libtool: line 950: libtool: ignoring unknown tag : command not found ../../../libtool: line 917: X--mode=compile: command not found ../../../libtool: line 950: libtool: ignoring unknown tag : command not found ../../../libtool: line 917: X--mode=compile: command not found >> >> This is all a symptom of the autoconf/libtool toolchain not getting created >> properly, which seems like it would be consistent with it failing to sed. >> Does installing fink's "sed" package resolve it? That only hides the fact >> that your libtoolize is looking for it, but at least would get you moving >> forward. > > I already have it [4.2.2-1]. sent from Mountain Lion Wash: "Curse your sudden but inevitable betrayal!" -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ Fink-users mailing list Fink-users@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.macosx.fink.user Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-users
Re: [Fink-users] Failed: phase compiling: libjasper.1-1.900.1-6 failed
On 2015 Jun 1, at 10:38 PM, Daniel Macks wrote: >>> autoreconf -fi >>> /sw/bin/libtoolize: line 3601: /sw/bin/grep: No such file or directory > > First sign of trouble is there...fink's libtoolize is hardcoding fink's grep > but then not finding it, so it will fail to accomplish whatever sed actions > it would do. What version of "libtool2" do you have installed? $ fink list libtool2 Information about 12297 packages read in 2 seconds. i libtool22.4.6-2Shared library build helper, v2.x i libtool2-shlibs 2.4.6-2Shared libraries for libtool, v2.x >>> /bin/sh ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. >>> -I../../../src/libjasper/include/jasper -I../../../src/libjasper/include >>> -I/sw/include -g -O2 -MT jas_debug.lo -MD -MP -MF .deps/jas_debug.Tpo -c -o >>> jas_debug.lo jas_debug.c >>> ../../../libtool: line 917: X--tag=CC: command not found >>> ../../../libtool: line 917: X--tag=CC: command not found >>> ../../../libtool: line 950: libtool: ignoring unknown tag : command not >>> found >>> ../../../libtool: line 917: X--mode=compile: command not found >>> ../../../libtool: line 950: libtool: ignoring unknown tag : command not >>> found >>> ../../../libtool: line 917: X--mode=compile: command not found > > This is all a symptom of the autoconf/libtool toolchain not getting created > properly, which seems like it would be consistent with it failing to sed. > Does installing fink's "sed" package resolve it? That only hides the fact > that your libtoolize is looking for it, but at least would get you moving > forward. I already have it [4.2.2-1]. sent from Mountain Lion Mal: "Jayne, your mouth is talking. You might wanna look to that." -- ___ Fink-users mailing list Fink-users@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.macosx.fink.user Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-users
Re: [Fink-users] Failed: phase compiling: libjasper.1-1.900.1-6 failed
Well, my laptop got wet, so i'm leaving it off the next few days. I'll check the versions then. On Monday, June 1, 2015 10:38 PM, Daniel Macks wrote: On Mon, 1 Jun 2015 07:53:42 -0700, David Lowe wrote: I'm getting the following with Fink 0.38.5 on OS 10.8.5. The relevant error seems to be "libtool: compile: cannot determine name of library object from `': command not found", but i didn't see anything immediately useful in a web search. I'm posting everything after the unpacking just in case. > > > autoreconf -fi > > /sw/bin/libtoolize: line 3601: /sw/bin/grep: No such file or directory First sign of trouble is there...fink's libtoolize is hardcoding fink's grep but then not finding it, so it will fail to accomplish whatever sed actions it would do. What version of "libtool2" do you have installed? > > /bin/sh ../../../libtool --tag=CC --mode=compile gcc > -DHAVE_CONFIG_H -I. -I../../../src/libjasper/include/jasper > -I../../../src/libjasper/include -I/sw/include -g -O2 -MT > jas_debug.lo -MD -MP -MF .deps/jas_debug.Tpo -c -o jas_debug.lo > jas_debug.c > > ../../../libtool: line 917: X--tag=CC: command not found > > ../../../libtool: line 917: X--tag=CC: command not found > > ../../../libtool: line 950: libtool: ignoring unknown tag : command > not found > > ../../../libtool: line 917: X--mode=compile: command not found > > ../../../libtool: line 950: libtool: ignoring unknown tag : command > not found > > ../../../libtool: line 917: X--mode=compile: command not found This is all a symptom of the autoconf/libtool toolchain not getting created properly, which seems like it would be consistent with it failing to sed. Does installing fink's "sed" package resolve it? That only hides the fact that your libtoolize is looking for it, but at least would get you moving forward. dan -- Daniel Macks dma...@netspace.org -- ___ Fink-users mailing list Fink-users@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.macosx.fink.user Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-users
Re: [Fink-users] Failed: phase compiling: libjasper.1-1.900.1-6 failed
On Mon, 1 Jun 2015 07:53:42 -0700, David Lowe wrote: I'm getting the following with Fink 0.38.5 on OS 10.8.5. The relevant error seems to be "libtool: compile: cannot determine name of library object from `': command not found", but i didn't see anything immediately useful in a web search. I'm posting everything after the unpacking just in case. > > > autoreconf -fi > > /sw/bin/libtoolize: line 3601: /sw/bin/grep: No such file or directory First sign of trouble is there...fink's libtoolize is hardcoding fink's grep but then not finding it, so it will fail to accomplish whatever sed actions it would do. What version of "libtool2" do you have installed? > > /bin/sh ../../../libtool --tag=CC --mode=compile gcc > -DHAVE_CONFIG_H -I. -I../../../src/libjasper/include/jasper > -I../../../src/libjasper/include -I/sw/include -g -O2 -MT > jas_debug.lo -MD -MP -MF .deps/jas_debug.Tpo -c -o jas_debug.lo > jas_debug.c > > ../../../libtool: line 917: X--tag=CC: command not found > > ../../../libtool: line 917: X--tag=CC: command not found > > ../../../libtool: line 950: libtool: ignoring unknown tag : command > not found > > ../../../libtool: line 917: X--mode=compile: command not found > > ../../../libtool: line 950: libtool: ignoring unknown tag : command > not found > > ../../../libtool: line 917: X--mode=compile: command not found This is all a symptom of the autoconf/libtool toolchain not getting created properly, which seems like it would be consistent with it failing to sed. Does installing fink's "sed" package resolve it? That only hides the fact that your libtoolize is looking for it, but at least would get you moving forward. dan -- Daniel Macks dma...@netspace.org -- ___ Fink-users mailing list Fink-users@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.macosx.fink.user Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-users
[Fink-users] Failed: phase compiling: libjasper.1-1.900.1-6 failed
I'm getting the following with Fink 0.38.5 on OS 10.8.5. The relevant error seems to be "libtool: compile: cannot determine name of library object from `': command not found", but i didn't see anything immediately useful in a web search. I'm posting everything after the unpacking just in case. > sudo -u fink-bld [ENV] sh -c /tmp/fink.WmwYe > env LANG=C LC_ALL=C /sw/bin/tar --no-same-owner --no-same-permissions -xf > /sw/src/jasper_1.900.1-debian1-2.4.debian.tar.xz > sudo -u fink-bld [ENV] sh -c /tmp/fink.v6cNS > /tmp/fink.SjhIL > #!/bin/sh -ev > for file in \ > 01-misc-fixes.patch \ > 02-fix-filename-buffer-overflow.patch \ > 03-CVE-2011-4516-and-CVE-2011-4517.patch \ > 04-CVE-2014-9029.patch \ > 05-CVE-2014-8137.patch \ > 06-CVE-2014-8138.patch \ > 07-CVE-2014-8157.patch \ > 08-CVE-2014-8158.patch \ > ; do > echo "applying $file" > patch -p1 < ../debian/patches/$file > done > applying 01-misc-fixes.patch > patching file src/libjasper/jpc/jpc_t2cod.c > patching file src/libjasper/jpc/jpc_util.c > patching file src/libjasper/jpc/jpc_dec.c > patching file src/libjasper/jpc/jpc_tagtree.c > patching file src/libjasper/jpc/jpc_mqdec.c > patching file src/libjasper/jpc/jpc_t2enc.c > patching file src/libjasper/jpc/jpc_mqenc.c > patching file src/libjasper/jpc/jpc_enc.c > patching file src/libjasper/jpc/jpc_t1enc.c > patching file src/libjasper/jpc/jpc_t2dec.c > patching file src/libjasper/jpc/jpc_qmfb.c > patching file src/libjasper/jpc/jpc_cs.c > patching file src/libjasper/bmp/bmp_dec.c > patching file src/libjasper/include/jasper/jas_malloc.h > patching file src/libjasper/base/jas_seq.c > patching file src/libjasper/base/jas_image.c > patching file src/libjasper/base/jas_icc.c > patching file src/libjasper/base/jas_malloc.c > patching file src/libjasper/base/jas_stream.c > patching file src/libjasper/base/jas_cm.c > patching file src/libjasper/jp2/jp2_enc.c > patching file src/libjasper/jp2/jp2_dec.c > patching file src/libjasper/jp2/jp2_cod.c > patching file src/libjasper/jp2/jp2_cod.h > patching file src/libjasper/mif/mif_cod.c > patching file acaux/config.sub > patching file acaux/config.guess > applying 02-fix-filename-buffer-overflow.patch > patching file src/libjasper/include/jasper/jas_stream.h > applying 03-CVE-2011-4516-and-CVE-2011-4517.patch > patching file src/libjasper/jpc/jpc_cs.c > applying 04-CVE-2014-9029.patch > patching file src/libjasper/jpc/jpc_dec.c > applying 05-CVE-2014-8137.patch > patching file src/libjasper/base/jas_icc.c > patching file src/libjasper/jp2/jp2_dec.c > applying 06-CVE-2014-8138.patch > patching file src/libjasper/jp2/jp2_dec.c > applying 07-CVE-2014-8157.patch > patching file src/libjasper/jpc/jpc_dec.c > applying 08-CVE-2014-8158.patch > patching file src/libjasper/jpc/jpc_qmfb.c > sudo -u fink-bld [ENV] sh -c /tmp/fink.H9Twi > autoreconf -fi > /sw/bin/libtoolize: line 3601: /sw/bin/grep: No such file or directory > libtoolize: putting auxiliary files in '.'. > libtoolize: copying file './ltmain.sh' > configure.ac:148: installing 'acaux/compile' > Makefile.am:59: warning: support for distribution archives compressed with > legacy program 'compress' is deprecated. > Makefile.am:59: It will be removed in Automake 2.0 > src/appl/Makefile.am:81: warning: 'INCLUDES' is the old name for > 'AM_CPPFLAGS' (or '*_CPPFLAGS') > src/libjasper/base/Makefile.am:76: warning: 'INCLUDES' is the old name for > 'AM_CPPFLAGS' (or '*_CPPFLAGS') > src/libjasper/bmp/Makefile.am:67: warning: 'INCLUDES' is the old name for > 'AM_CPPFLAGS' (or '*_CPPFLAGS') > src/libjasper/jp2/Makefile.am:67: warning: 'INCLUDES' is the old name for > 'AM_CPPFLAGS' (or '*_CPPFLAGS') > src/libjasper/jpc/Makefile.am:105: warning: 'INCLUDES' is the old name for > 'AM_CPPFLAGS' (or '*_CPPFLAGS') > src/libjasper/jpg/Makefile.am:79: warning: 'INCLUDES' is the old name for > 'AM_CPPFLAGS' (or '*_CPPFLAGS') > src/libjasper/mif/Makefile.am:66: warning: 'INCLUDES' is the old name for > 'AM_CPPFLAGS' (or '*_CPPFLAGS') > src/libjasper/pgx/Makefile.am:67: warning: 'INCLUDES' is the old name for > 'AM_CPPFLAGS' (or '*_CPPFLAGS') > src/libjasper/pnm/Makefile.am:67: warning: 'INCLUDES' is the old name for > 'AM_CPPFLAGS' (or '*_CPPFLAGS') > src/libjasper/ras/Makefile.am:67: warning: 'INCLUDES' is the old name for > 'AM_CPPFLAGS' (or '*_CPPFLAGS') > ./configure --prefix=/sw --enable-shared --disable-static > --enable-dependency-tracking --mandir=/sw/share/man > checking build system type... x86_64-apple-darwin12.6.0 > checking host system type... x86_64-apple-darwin12.6.0 > checking target system type... x86_64-apple-darwin12.6.0 > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... acaux/install-sh -c -d > checking for gawk... gawk > checking
