[Bug 50345] New: `wine` always loads executable from $WINEPREFIX/windows instead of given path if filenames match

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50345

Bug ID: 50345
           Summary: `wine` always loads executable from
                    $WINEPREFIX/windows instead of given path if filenames
                    match
           Product: Wine
           Version: 5.22
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: wineserver
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

I was working on a modification to Wine Notepad, and ran into the following
oddity when trying to test my changes:

`wine ./notepad.exe` does not run the correct executable. Instead of the newly
built executable in the current directory, it ran
`$WINEPREFIX/windows/notepad.exe` instead.

Even when specifying the absolute path, `$PWD/notepad.exe`, it still ran the
wrong one.

The only way to run the correct executable was to rename it.

Furthermore, I observed the following:

$ wine ./notepad.exe
<wrong notepad opens>
$ rm ./notepad.exe
$ wine ./notepad.exe
wine: cannot find L"./notepad.exe"
$

[Bug 50345] `wine` always loads executable from $WINEPREFIX/windows instead of given path if filenames match

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50345

Alexandre Julliard  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #1 from Alexandre Julliard  ---
That's expected behavior if the binary is marked as Wine builtin. If you don't
want that, you should build it without the -Wl,--wine-builtin flag.

[Bug 50345] `wine` always loads executable from $WINEPREFIX/windows instead of given path if filenames match

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50345

--- Comment #2 from [e-mail] ---
(In reply to Alexandre Julliard from comment #1)
> That's expected behavior if the binary is marked as Wine builtin. If you
> don't want that, you should build it without the -Wl,--wine-builtin flag.

Is this documented anywhere? I know the Winelib user guide mentions 'conflicts'
but does not elaborate on this, nor does it give any other way to avoid
conflict.

[Bug 50345] `wine` always loads executable from $WINEPREFIX/windows instead of given path if filenames match

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50345

--- Comment #3 from Austin English  ---
Closing.

[Bug 50345] `wine` always loads executable from $WINEPREFIX/windows instead of given path if filenames match

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50345

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #4 from Austin English  ---
Closing.