Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#81 autoconf problem with mingw-runtime.

closed
nobody
Other (9)
5
2006-07-18
2006-06-16
oiaohm
No

All of the provided configure and sh script. Have a
defect on linux #! /bin/sh does not work. These have
to be #!/bin/sh to work.

Now this would not be a large problem. If you autoconf
rebuild the configure files. You cannot build the
mingw without a binary copy. Yet the other ones do.
This could be a autoconf version thing.

With gcc 4.1.1-mingw on Linux
./configure --enable-langunges=c --disable-libssp
--target=i386-mingw32
Will give a working C complier. So really if
mingw-runtime builds from source as w32api does now.
There is no need for binarys to start a mingw tree off.
Perfectly clean tree.

Only thing that is prevent it is the autoconf system
problem.

Discussion

  • Earnie Boyd
    Earnie Boyd
    2006-06-16

    Logged In: YES
    user_id=15438

    Since this is a request for help and not a bug report then
    I'm moving this to "Support Request".

     
  • Earnie Boyd
    Earnie Boyd
    2006-06-16

    • labels: 104601 -->
     
  • Earnie Boyd
    Earnie Boyd
    2006-06-16

    Logged In: YES
    user_id=15438

    If your shell doesn't support ``#! /bin/sh'' then your shell
    is broken. We do not control the support of your shell, so
    obviously you need to go to the support maintainers for that
    shell. I thought the standard shell for Linux was Bash
    which is what we use for MSYS.

    Or am I missing the point of what you're trying to say?

     
  • Earnie Boyd
    Earnie Boyd
    2006-06-16

    • milestone: --> Waiting_user_response
    • labels: --> Other
    • status: open --> pending
     
  • oiaohm
    oiaohm
    2006-06-17

    Logged In: YES
    user_id=997947

    Shell is not broken. Standard sh and alot of forms of it
    forbid space after the #!.

    Windows Versions of bash are excepting of a incorrect data
    here.

    Note on Linux #!/bin/sh lot of the time not bash its more
    often a shell called ash that obeys standard sh rules as
    well as 20 other shells that could also be in that location.
    If you are really after bash alone the thing should be
    #!/bin/bash. Note ash is faster smaller on ram. It
    improved the performance of the linux init scripts. The
    all important boot speed perforance bash is far to slow.
    /bin/sh will be swaped quite commonly just to tweek linux
    boot times all you can allow on is standard sh features.

    All #!/bin/sh is asking for is a sh compad shell. Lets play
    random pot luck on features. The space after #! is a bash
    non standard feature and realy should not be used when
    calling #!/bin/sh. If you wish to keep on using the space
    you should swap all of them to #! /bin/bash. Ie something
    has to be changed one way or the other. I think remove the
    spaces would be simpler.

    I used Autoconf to rebuild the configure in mingw-runtime
    after configure not working due to defect. For some reason
    after rebuild its demarding that mingw gcc is fully
    operational so will not make the makefiles. This is point
    less when building from source alone. I will be looking to
    why this is happening.

    w32api I fix it autoconf rebuild works pefectly.

    This is 2 bugs in report. Move it back. Due to lack of
    information on linux/unix shell systems as earnie has shown
    explains how the first error sneeked in.

     
  • oiaohm
    oiaohm
    2006-06-17

    • status: pending --> open
     
  • Earnie Boyd
    Earnie Boyd
    2006-06-17

    Logged In: YES
    user_id=15438

    Point me to a shell standards document that states that
    space following the shebang isn't legal and I'll consider
    moving it back as a bug. Otherwise it isn't a bug and your
    precious ash has an issue. I code scripts on HP-UX and Sun
    and have never had a problem with a space following the shebang.

    To work around your ash problem:
    sh configure --prefix=/usr/local

    This should be a clue to ash to ignore the shebang line.

     
  • Earnie Boyd
    Earnie Boyd
    2006-06-17

    • status: open --> pending
     
  • Logged In: YES
    user_id=1312539

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 30 days (the time period specified by
    the administrator of this Tracker).

     
    • status: pending --> closed