wine can't find regedit.exe.so when it is not on the path

[Andriy Palamarchuk]

wineinstall fails because wine can't find
regedit.exe.so.
Obviously, the wine source directory does not exist in
path of just created config file.
After the wineistall failure .wine directory with
config file are created. I get the same errors when I
try to run regedit manually, even with using full
path:

$ /prj/wine/programs/regedit/regedit
Could not stat /mnt/fd0 (No such file or directory),
ignoring drive A:
Could not stat /cdrom (No such file or directory),
ignoring drive D:
Warning: could not find wine config [Drive x] entry
for current working directory /mnt/buf/prj/wine;
starting in windows directory.
Warning: /prj/wine/programs/regedit/regedit.exe.so not
accessible from a configured DOS drive
Warning: /prj/wine/programs/regedit/regedit.exe.so not
accessible from a configured DOS drive
/prj/wine/miscemu/wine: cannot find
'/prj/wine/programs/regedit/regedit.exe.so'

$ file /prj/wine/programs/regedit/regedit.exe.so
/prj/wine/programs/regedit/regedit.exe.so: ELF 32-bit
LSB shared object, Intel 80386, version 1, not
stripped

$ ls -l programs/regedit/regedit
lrwxrwxrwx    1 apalamar apalamar       23 May 30
06:53 programs/regedit/regedit ->
../../tools/winewrapper

Andriy

__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

[Dustin Navea]

--- Andriy Palamarchuk  wrote:
> wineinstall fails because wine can't find
> regedit.exe.so.
> Obviously, the wine source directory does not exist
> in
> path of just created config file.
> After the wineistall failure .wine directory with
> config file are created. I get the same errors when
> I
> try to run regedit manually, even with using full
> path:
>
> $ /prj/wine/programs/regedit/regedit
> Could not stat /mnt/fd0 (No such file or directory),
> ignoring drive A:
> Could not stat /cdrom (No such file or directory),
> ignoring drive D:
> Warning: could not find wine config [Drive x] entry
> for current working directory /mnt/buf/prj/wine;
> starting in windows directory.
> Warning: /prj/wine/programs/regedit/regedit.exe.so
> not
> accessible from a configured DOS drive
> Warning: /prj/wine/programs/regedit/regedit.exe.so
> not
> accessible from a configured DOS drive
> /prj/wine/miscemu/wine: cannot find
> '/prj/wine/programs/regedit/regedit.exe.so'
>
> $ file /prj/wine/programs/regedit/regedit.exe.so
> /prj/wine/programs/regedit/regedit.exe.so: ELF
> 32-bit
> LSB shared object, Intel 80386, version 1, not
> stripped
>
> $ ls -l programs/regedit/regedit
> lrwxrwxrwx    1 apalamar apalamar       23 May 30
> 06:53 programs/regedit/regedit ->
> ../../tools/winewrapper
>
> Andriy

I do believe that you are running the wrong regedit...
 is /prj/wine your wine install dir or did you install
to the default wine install dir (/usr/local/bin)?  If
you installed to the default winr install dir, run
that one...  I also ran into the problem of "not
accessible from a configured dos drive" for the wine
progs, so I added a symlink to the .exe and the
.exe.so in my fake c drive windows directory and
everything worked like a charm...

-Dustin

P.S. maybe I should put that symlink creation into the
makefile or wineinstall?  I would think the makefile
would be the better place for it as not everyone runs
wineinstall, and therefore may not get the symlinks if
i put it there...

__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

[Andriy Palamarchuk]

--- Dustin Navea  wrote:
<skipped>
> I do believe that you are running the wrong
> regedit...
>  is /prj/wine your wine install dir or did you
> install
> to the default wine install dir (/usr/local/bin)?

No, this is not wine install dir - this is wine source
dir. And wineinstall runs not the installed regedit,
it runs the one, compiled in the source three.
This is how regedit path is defined in wineinstall:

REGEDIT=programs/regedit/regedit

I don't think there are other options of interpreting
location of regedit.
> If
> you installed to the default winr install dir, run
> that one...  I also ran into the problem of "not
> accessible from a configured dos drive" for the wine
> progs, so I added a symlink to the .exe and the
> .exe.so in my fake c drive windows directory and
> everything worked like a charm...

wineinstall script should run regedit from the source
tree succesfully or it should be changed to run it
from /usr/local/bin directory.

Andriy

__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

[Dustin Navea]

--- Andriy Palamarchuk  wrote:
> --- Dustin Navea  wrote:
>
> <skipped>
> > I do believe that you are running the wrong
> > regedit...
> >  is /prj/wine your wine install dir or did you
> > install
> > to the default wine install dir (/usr/local/bin)?
>
> No, this is not wine install dir - this is wine
> source
> dir. And wineinstall runs not the installed regedit,
> it runs the one, compiled in the source three.
> This is how regedit path is defined in wineinstall:
>
> REGEDIT=programs/regedit/regedit
>
> I don't think there are other options of
> interpreting
> location of regedit.

I did forget that wineinstall runs regedit from the
source wine directory...
> > If
> > you installed to the default winr install dir, run
> > that one...  I also ran into the problem of "not
> > accessible from a configured dos drive" for the
>
> wine
> > progs, so I added a symlink to the .exe and the
> > .exe.so in my fake c drive windows directory and
> > everything worked like a charm...
>
> wineinstall script should run regedit from the
> source
> tree succesfully or it should be changed to run it
> from /usr/local/bin directory.

Agreed, I would say that probably it would be better
to go ahead and call it from the wine installed dir
(maybe not always /usr/local/bin) since regedit isnt
called until way after make install, so the binary is
guaranteed to be already installed...

-Dustin

__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

[Alexandre Julliard]

Andriy Palamarchuk  writes:
> wineinstall fails because wine can't find
> regedit.exe.so.
> Obviously, the wine source directory does not exist in
> path of just created config file.

I'd say that wineinstall should run the installed wine binaries, not
the ones from the source dir.

[Rob Browning]

Alexandre Julliard  writes:
> > wineinstall fails because wine can't find
> > regedit.exe.so.
> > Obviously, the wine source directory does not exist in
> > path of just created config file.
>
> I'd say that wineinstall should run the installed wine binaries, not
> the ones from the source dir.

I recently tried the newish build infrastructure (using wineinstall),
and overall I liked it, but I wasn't able to use it without some
modifications.  That's because I install wine into
/usr/local/opt/wine, I never install it as root, and I don't want it
tinkering with my ld.so.conf.  I want to handle getting the right bits
in my PATH and LD_LIBRARY_PATH myself.  However, I *would* like to let
wineinstall handle all the rest.

So I was wondering if there would be any interest in a patch to
wineinstall that would allow this kind of install as an option.
Perhaps something like this:

tools/wineinstall --not-root --prefix=/usr/local/opt/wine

Even easier would be to just allow envt var overrides rather than
coding for command line options.  i.e.

WINEINSTALL_SU=no WINEINSTALL_PREFIX=/usr/local/opt/wine tools/wineinstall

I could also output a final message would be output when anyone
specifies a prefix that says something like

You have used a prefix other than the default.  You will need to
  make sure your PATH includes ... and your LD_LIBRARY_PATH includes
  ...  If you don't want to have to do this, please don't specify
  WINEINSTALL_PREFIX.

Thanks