#2004 Program output do not work without "../etc/inputrc"

MSYS
closed
nobody
rsync (1)
Support
self-service
User_Error
False
2013-07-23
2013-07-16
Arkadi
No

I am trying to repackage MinGW port of rsync to work as a stand along tool.
If I run "rsync --help", when it is copied aside (with relevant DLL's), I do not see stdout.

Observation:
If I add a file, even empty "../etc/inputrc", the tool works as expected.

Discussion

  • Keith Marshall
    Keith Marshall
    2013-07-16

    • status: unread --> pending
    • Type: Bug --> Support
    • Resolution: none --> self-service
    • Category: Unknown --> Waiting_User_Response
     
  • Keith Marshall
    Keith Marshall
    2013-07-16

    I'm having a hard time understanding how this might be construed as a MinGW bug; surely, it's an issue in your port, that rsync expects to find ../etc/inputrc? Seems to me that this would be your bug, (or rather, porting issue), to resolve.

    On this basis, I'm reclassifying as a support request, which requires your further attention.

     
  • Arkadi
    Arkadi
    2013-07-22

    I have not done any compiling by myself, let along real porting.

    The same is reproduced with "ls.exe":
    ls.exe, msys-1.0.dll, msys-intl-8.dll
    This three files along don't let me using "ls" - I have to put ../etc/inputrc.

    BTW: the path is relative to the exe (and not cwd/pwd)

     
  • Arkadi
    Arkadi
    2013-07-22

    Update: I tested "Hello World" with MinGW and the problem seems MSYS specific.
    Farther, my "hello.exe" is linked with libgcc_s_dw2-1.dll vs. ls.exe linked with msys-1.0.dll.
    Somehow, I do not find g++ in MSYS to try with.

     
  • Arkadi
    Arkadi
    2013-07-22

    After installing "msys-dvlpr" I confirm - it is MSYS specific bug.
    Reproduced on "Hello World".

     
  • Earnie Boyd
    Earnie Boyd
    2013-07-22

    • labels: --> rsync
    • status: pending --> closed
    • Category: Waiting_User_Response --> User_Error
     
  • Earnie Boyd
    Earnie Boyd
    2013-07-22

    As Keith said, this is your own issue to resolve. There is no bug in the efforts we provide since we provide a complete installation including dependencies. You are working to provide a package which distributes only msys-rsync. You alone need to resolve the dependency issues with your repackaged solution. We do not support others repackaging what we provide.

     
  • Keith Marshall
    Keith Marshall
    2013-07-22

    To clarify further, if any such clarification is required, it seems that you are trying to repackage our msys-rsync as a free-standing package? If this is the case, then you must provide at least a minimally complete MSYS runtime infrastructure. Your reference to ../etc/inputrc would seem to be a complete red herring; for me, MSYS' rsync.exe runs just fine, with no inputrc in my /etc directory. It is the existence of the /etc directory itself which is a fundamental requirement, (and yes, relative to rsync.exe, that is ../etc). This is by design; it is not an MSYS bug.

    I would also bring to your attention that distribution of MSYS is subject to the terms of the GNU General Public Licence, version 2; if you are creating this package for redistribution, then you must also make provision to distribute source, for all MSYS executables, DLLs, and other components which are needed to furnish the runtime infrastructure.

     
  • Arkadi
    Arkadi
    2013-07-23

    MSYS is subject to the terms of the GNU General Public Licence, version 2

    As long, as it is internal tool, I think I am fine with it.
    Anyway, I will consult our legal department once my scripts are ready.

    for me, MSYS' rsync.exe runs just fine, with no inputrc in my /etc directory

    Please, try moving the executable aside, not removing parts of your working MSYS.
    There are most be some other files that will be treated instead of ../etc/inputrc.

    It is the existence of the /etc directory itself which is a fundamental requirement

    In case of a complex tool like rsync I tend to accept your answer, even if it comes from some bug.
    However, you are ignoring the case of "Hello World". This one is not complex enough to require special treatment. I expect it to work if I supply msys-1.0.dll.

     
    Last edit: Arkadi 2013-07-23
    • Keith Marshall
      Keith Marshall
      2013-07-23

      However, you are ignoring the case of "Hello World".

      No, I am not. It is you who are ignoring...

      This one is not complex enough to require special treatment. I expect it to work if I supply msys-1.0.dll.

      You really should not be using the MSYS development suite, to compile such applications. If you do, then you must also provide the necessary infrastructure to support them. That infrastructure is not as simple as just providing msys-1.0.dll; you must also satisfy the dependency requirements of that DLL; one of these is that /etc must exist.

      I'll say it one last time; this is not an MSYS bug.