Cannot install networks 2.6.2.1 on Windows 64 bits with 32 bits installer about minghc HOT 9 CLOSED

Additional I tried this

• cabal install network (instead of cabal install http). No difference.

• cabal install network as administrator. No difference.

• cabal unpack network
  cd network-2.6.2.1
  cabal configure
  in a editor I opend configure. At line 4876 ...
  if test $ac_delim_n = $ac_delim_num; then
  break
  elif $ac_last_try; then
  as_fn_error $? "could not make $CONFIG_STATUS" "$LINENO" 5
  else ....

  This seems bash to me. I can't see an error (I know almost nothing about bash)

Kees

from minghc.

You can see my configure file at:
http://www.tbsoftware.nl/configureNetwork/configure

Kees

from minghc.

In configure I've added the line
echo $ac_delim_n
The extra line it prints was: 62 lines match

I've added this line:
....
echo $ac_subst_vars
ac_delim_num=echo "$ac_subst_vars" | grep -c '^'
....
This was the output:
LTLIBOBJS LIBOBJS EXTRA_SRCS EXTRA_LIBS EXTRA_CPPFLAGS CALLCONV EGREP GREP CPP OBJEXT EXEEXT ac_ct_CC CPPFLAGS LDFLAGS CFLAGS CC host_os host_vendor host_cpu host build_os build_vendor build_cpu build target_alias host_alias build_alias LIBS ECHO_T ECHO_N ECHO_C DEFS mandir localedir libdir psdir pdfdir dvidir htmldir infodir docdir oldincludedir includedir localstatedir sharedstatedir sysconfdir datadir datarootdir libexecdir sbindir bindir program_transform_name prefix exec_prefix PACKAGE_URL PACKAGE_BUGREPORT PACKAGE_STRING PACKAGE_VERSION PACKAGE_TARNAME PACKAGE_NAME PATH_SEPARATOR SHELL
This line contains 62 words.
It looks like this script exceeds the limits of 'test'.

from minghc.

I've found the solution.
Cabal uses the wrong grep. The grep it uses was from Delphi (which came earlier in the path)

from minghc.

Glad you found it. I figured it was something wrong with the PATH ordering. @ndmitchell @snoyberg Would it make sense to add a sanity check after install to see if there are other tools shadowing MinGHC's? I'm not sure of another way to fix this generally.

from minghc.

It would be very difficult to guess all of the tools that need to be available and determine that the version the user has is different than the one we need. We may want to start a real conversation about the interaction between MinGHC and stack here; stack solves this problem by modifying the PATH at the time of calling external tools to force its version of msys to take precedence. We can't do that with cabal.

Or perhaps we need to tell users with stack that they must use the switcher script to ensure things work perfectly.

from minghc.

I had the exact same thoughts. :)

from minghc.

stack is a much better experience for Windows because it controls GHC installations and PATH messiness internally.

from minghc.

Perhaps this should be a separate issue, but I'll dive in here anyway...

I clearly consider MinGHC+cabal-install an inferior solution (as I am biased), since I think stack > cabal-install. The question then becomes: what does MinGHC offer over plain stack? As I see it:

• Easier installation procedure
• Includes the big downloads (GHC and msys) in the initial download, which is very useful if you're going to install the toolchain on multiple systems

The advantage of downloading plain stack is:

• Quicker initial install
• Doesn't require any registry changes
• Will grab the best version of GHC for you, instead of whatever one happens to be available

Those are my thoughts, what does everyone else think?

from minghc.