Unable to run x86-mingw32-build.sh on ubuntu

[Bryan White]

I have downloaded x86-mingw32-build-1.0-sh.tar.bz2 (dated 2009-03-16 12:41Z) from https://sourceforge.net/projects/mingw/files/Installer/

The file x86-mingw32-build.sh is 7478 bytes and dated 2009-03-16 12:28:22

When I run x86-mingw32-build.sh I get an error:

$ sh x86-mingw32-build.sh i586-pc-mingw32

x86-mingw32-build.sh: 130: /[XXX]/x86-mingw32-build-1.0/x86-mingw32-build.sh.functions: Syntax error: Bad function name

Lines 126-32 of x86-mingw32-build.sh.functions seem to be ... :

# Some of the following functions can use the `local' built in command,

# if it is available; make sure we have a fall back, if it isn't ...

#

test -z "`exec 2>/dev/null; try(){ local x; }; try || echo no`" || \

local()

# ... by making it a function equivalent to the `null' command.

{ :; }

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
MinGW-users mailing list
[hidden email]

This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.  Disregard for the list etiquette may cause your account to be moderated.

_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users
Also: mailto:[hidden email]?subject=unsubscribe

[Paul Hentschel]

>When I run x86-mingw32-build.sh I get an error:
>$ sh x86-mingw32-build.sh i586-pc-mingw32
>x86-mingw32-build.sh: 130: /[XXX]/x86-mingw32-build-1.0/x86-mingw32-build.sh.functions:
>Syntax error: Bad function name

Check and see if /bin/sh is a symbolic link to dash instead of bash. If it is, try changing
it to point to bash instead.

Paul



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
MinGW-users mailing list
[hidden email]

This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.  Disregard for the list etiquette may cause your account to be moderated.

_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users
Also: mailto:[hidden email]?subject=unsubscribe

[Bryan White]

On 28 July 2017 at 05:32, Paul Hentschel <[hidden email]> wrote:

>When I run x86-mingw32-build.sh I get an error:
>$ sh x86-mingw32-build.sh i586-pc-mingw32
>x86-mingw32-build.sh: 130: /[XXX]/x86-mingw32-build-1.0/x86-mingw32-build.sh.functions:
>Syntax error: Bad function name

Check and see if /bin/sh is a symbolic link to dash instead of bash. If it is, try changing
it to point to bash instead.

Paul

This is indeed the case - /bin/sh does (correctly, apparently) point to dash.

And taking into account that 

The Debian policy manual has long mandated that "shell scripts specifying '/bin/sh' as interpreter must only use POSIX features"(https://wiki.ubuntu.com/DashAsBinSh) 

then IMO, because the mingw32 script seems to break the rules, changing where /bin/sh points is The Wrong Fix(R).

To me it makes sense to change the mingw32 scripts to use bash, rather than risking any of my other scripts behaving unexpectedly. You see, I do not intend for my computer to become a single-use cross-compiler; I want a general purpose computer that will continue working with my existing applications.

So, I will change x86-mingw32-build.sh & x86-mingw32-build.sh.version to start '#!/bin/bash' rather than '#!/bin/sh' and see how it goes.

If you know of problems taking this approach, please advise, so I can consider building a separate environment to do the cross compiling. 

Then again, if I'm going to create another environment, I may as well just use Windows itself and save having to cross-compile (which somewhat defeats the purpose of what mingw32 is trying to achieve). 

Brewmanz

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
MinGW-users mailing list
[hidden email]

This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.  Disregard for the list etiquette may cause your account to be moderated.

_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users
Also: mailto:[hidden email]?subject=unsubscribe

[Paul Hentschel]

On 7/27/2017 6:24 PM, Bryan White wrote:
> then IMO, because the mingw32 script seems to break the rules, changing
> where /bin/sh points is *The Wrong Fix(R)*.
> To me it makes sense to change the mingw32 scripts to use bash, rather
> than risking any of my other scripts behaving unexpectedly.

Nobody said you couldn't change it back when you were done building the
compiler. You're free to fix it however you choose. I was merely
pointing out the likely cause of the error.

Paul



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
MinGW-users mailing list
[hidden email]

This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.  Disregard for the list etiquette may cause your account to be moderated.

_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users
Also: mailto:[hidden email]?subject=unsubscribe

[MinGW - User mailing list]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 27/07/17 23:24, Bryan White wrote:
> So, *I will change x86-mingw32-build.sh &
> x86-mingw32-build.sh.version to start '#!/bin/bash' rather than
> '#!/bin/sh'* and see how it goes.

Good luck with that.  These scripts are obsolete, no longer maintained,
and unsuitable for building anything more recent than GCC-3.4.5.  Please
look in the archives of the MinGW-Dvlpr list; I described the procedure I
now use, for building GCC-4.x, GCC-5.x, and GCC-6.x cross-compilers, in
https://sourceforge.net/p/mingw/mailman/message/35591449/

- --
Regards,
Keith.

Public key available from keys.gnupg.net
Key fingerprint: C19E C018 1547 DE50 E1D4 8F53 C0AD 36C6 347E 5A3F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iQIcBAEBAgAGBQJZe6E9AAoJEMCtNsY0flo/YmEP/1gG+lox+/p3vx1zQpxpSEZc
uXtXMJ/BIFc6k9cAr3aZKs8N9DSZ9PTw5ZwDJM4ttiXAYwpmG9iWXDonYX4toa4C
P9+tNx1Qp9mvvBlJXdAvfp7341o4t1Lr+WFPw6Ic5bOQBjzRQNse+ly093gBcYE9
2uej+48Kd0i+caXISrA1YDYko6iJX2VVr+YVdwUNlJXXc/ntuXE7qPrpJvXfq8l4
+t6SPmQ6hj2jNmdWZ0WxOPlTkqYIlkHGhFyjI1/kGyj7gOmUY3xVaIKC3z1z2eDB
KAajjVijh2HDrUhhzJ+8bbKtKfeAmsaYQ2PY1rothpdFhL8WQPY/NQ5dpSwq05P7
b5pCbeot/fMLKP0vbI9+uZLj6hRE+YVSp4OHDkxktdyydUYkk91xLGXOnbmtBw8C
s763ChHJQFPwzGEAXrbXeP4PxjpnhHa3KqCBkWb+YyLHdwS5EXKhh0Mtft7AvkRW
2JKarqgSJJoNh04WZck/tEXwX42TF22TO6f87shz1QHWZ1AifPPwDJKstS7PzpuR
+NmKbpR/1hHKbSJtdR7oLOfYJc2xZUQvKdKGiYac1HtdCTLCEv+v07tvw9FUkpJQ
lLbz1kBaGsEYXl23ZNNOPvL5ZqLAaJ5czjjFjTpQQspjSauXtPpcNjPVixqiPfb7
l4U2w/W4aDyNd31wVTrw
=BXAA
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
MinGW-users mailing list
[hidden email]

This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.  Disregard for the list etiquette may cause your account to be moderated.

_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users
Also: mailto:[hidden email]?subject=unsubscribe