On 2015 Jun 1, at 10:38 PM, Daniel Macks <dma...@netspace.org> 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].
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
