Error at end of app install: can't open builtin library for regsvr32.exe...

[Dan Kegel]

Hrm.  Haven't seen this one before.  At the end of installation
of IBM Homepage Builder 6.0 for Windows, I get

wine: cannot open builtin library for
L"C:\\windows\\system32\\regsvr32.exe":
/home/dank/wine/programs/regsvr32.exe.so: invalid ELF header

This is with 0.9.3 built on fc3.

Thanks,
Dan
--
Wine for Windows ISVs: http://kegel.com/wine/isv

[Vitaliy Margolen]

Thursday, December 15, 2005, 11:17:18 AM, Dan Kegel wrote:
> Hrm.  Haven't seen this one before.  At the end of installation
> of IBM Homepage Builder 6.0 for Windows, I get
> wine: cannot open builtin library for
> L"C:\\windows\\system32\\regsvr32.exe":
> /home/dank/wine/programs/regsvr32.exe.so: invalid ELF header
>
> This is with 0.9.3 built on fc3.

Looks like a case of overwritten regsvr32.exe with native copy (like what
IE6 installation will do...

Vitaliy

[Dan Kegel]

On 12/15/05, Vitaliy Margolen <wine-devel(a)kievinfo.com> wrote:
> > wine: cannot open builtin library for
> > L"C:\\windows\\system32\\regsvr32.exe":
> > /home/dank/wine/programs/regsvr32.exe.so: invalid ELF header
> >
> > This is with 0.9.3 built on fc3.
>
> Looks like a case of overwritten regsvr32.exe with native copy (like what
> IE6 installation will do...

Nice theory, but check this out: I can reproduce it without installing anything:

$ rm -rf .wine
$ wine/wine notepad.exe
/home/dank/.wine updated successfully.
$ find .wine -name regsvr32.exe -ls
4669487    0 lrwxrwxrwx   1 dank     dank           40 Dec 17 03:35
.wine/drive_c/windows/system32/regsvr32.exe ->
/home/dank/wine/programs/regsvr32.exe.so
$ wine/wine .wine/drive_c/windows/system32/regsvr32.exe
wine: cannot open builtin library for
L"Z:\\home\\dank\\.wine\\drive_c\\windows\\system32\\regsvr32.exe":
/home/dank/wine/programs/regsvr32.exe.so: invalid ELF header

And better yet, I *can* run regsvr32.exe.so if I avoid the symlink:

$ wine/wine wine/programs/regsvr32.exe.so
(works ok)

Or if I actually install wine:
$ wine .wine/drive_c/windows/system32/regsvr32.exe

Aha.  It looks like it might have been a clash between
the wine in the build directory and the old wine I had installed.

So I guess it's not safe to run from the build directory
if you have a copy of Wine installed on your system.
- Dan
--
Wine for Windows ISVs: http://kegel.com/wine/isv

[Vitaliy Margolen]

Friday, December 16, 2005, 9:08:19 PM, Dan Kegel wrote:
> On 12/15/05, Vitaliy Margolen <wine-devel(a)kievinfo.com> wrote:
> > > wine: cannot open builtin library for
> > > L"C:\\windows\\system32\\regsvr32.exe":
> > > /home/dank/wine/programs/regsvr32.exe.so: invalid ELF header
> > >
> > > This is with 0.9.3 built on fc3.
> >
> > Looks like a case of overwritten regsvr32.exe with native copy (like what
> > IE6 installation will do...
> Nice theory, but check this out: I can reproduce it without installing anything:
> Well it's not a theory, it's a fact <g>
> $ rm -rf .wine
> $ wine/wine notepad.exe
> /home/dank/.wine updated successfully.
> $ find .wine -name regsvr32.exe -ls
> 4669487    0 lrwxrwxrwx   1 dank     dank           40 Dec 17 03:35
> .wine/drive_c/windows/system32/regsvr32.exe ->
> /home/dank/wine/programs/regsvr32.exe.so
> Yup, exactly what I said. Run
> 'file /home/dank/wine/programs/regsvr32.exe.so' to see what I'm talking
> about.

Vitaliy

[Dan Kegel]

On 12/16/05, Vitaliy Margolen <wine-devel(a)kievinfo.com> wrote:
> > $ rm -rf .wine
> > $ wine/wine notepad.exe
> > /home/dank/.wine updated successfully.
> > $ find .wine -name regsvr32.exe -ls
> >   4669487    0 lrwxrwxrwx   1 dank     dank           40 Dec 17 03:35
> >   .wine/drive_c/windows/system32/regsvr32.exe ->
> >   /home/dank/wine/programs/regsvr32.exe.so
>
> Yup, exactly what I said.

? You were talking about something being overwritten with a
native copy by an installer, but you can see from the log
that no installer was run.
> Run
>   'file /home/dank/wine/programs/regsvr32.exe.so' to see what I'm talking
> about.

OK:

$ file /home/dank/wine/programs/regsvr32.exe.so
/home/dank/wine/programs/regsvr32.exe.so: symbolic link to
`regsvr32/regsvr32.exe.so'
$ file /home/dank/wine/programs/regsvr32/regsvr32.exe.so
/home/dank/wine/programs/regsvr32/regsvr32.exe.so: ELF 32-bit LSB
shared object, Intel 80386, version 1 (SYSV), not stripped

What does that tell you?  The file looks like a perfectly good
ELF file, as one would expect.  How do you explain the next line from the log,

$ wine/wine .wine/drive_c/windows/system32/regsvr32.exe
wine: cannot open builtin library for
L"Z:\\home\\dank\\.wine\\drive_c\\windows\\system32\\regsvr32.exe":
/home/dank/wine/programs/regsvr32.exe.so: invalid ELF header

?
- Dan

--
Wine for Windows ISVs: http://kegel.com/wine/isv

[Vitaliy Margolen]

Friday, December 16, 2005, 10:45:06 PM, Dan Kegel wrote:
> On 12/16/05, Vitaliy Margolen <wine-devel(a)kievinfo.com> wrote:
> > > $ rm -rf .wine
> > > $ wine/wine notepad.exe
> > > /home/dank/.wine updated successfully.
> > > $ find .wine -name regsvr32.exe -ls
> > >   4669487    0 lrwxrwxrwx   1 dank     dank           40 Dec 17 03:35
> > >   .wine/drive_c/windows/system32/regsvr32.exe ->
> > >   /home/dank/wine/programs/regsvr32.exe.so
> >
> > Yup, exactly what I said.
> > ? You were talking about something being overwritten with a
> > native copy by an installer, but you can see from the log
> > that no installer was run.
> > That file is not in your ~/.wine directory. When you removed it, you
> > haven't touched the actual "regsvr32.exe.so" file.
> > Run
> >   'file /home/dank/wine/programs/regsvr32.exe.so' to see what I'm talking
> > about.
> > OK:
> $ file /home/dank/wine/programs/regsvr32.exe.so
> /home/dank/wine/programs/regsvr32.exe.so: symbolic link to
> `regsvr32/regsvr32.exe.so'
> $ file /home/dank/wine/programs/regsvr32/regsvr32.exe.so
> /home/dank/wine/programs/regsvr32/regsvr32.exe.so: ELF 32-bit LSB
> shared object, Intel 80386, version 1 (SYSV), not stripped
> What does that tell you?  The file looks like a perfectly good
> ELF file, as one would expect.  How do you explain the next line from the log,
> $ wine/wine .wine/drive_c/windows/system32/regsvr32.exe
> wine: cannot open builtin library for
> L"Z:\\home\\dank\\.wine\\drive_c\\windows\\system32\\regsvr32.exe":
> /home/dank/wine/programs/regsvr32.exe.so: invalid ELF header

Yeah. The only time I have seen this message in relation to regsvr32.exe
is only when Wine's builtin regsvr32.exe.so was overwritten with native
PE executable. That could happen only of you have write access to the the
place where you installed wine, or if you running it from the source
tree.

In this case I don't know then what is going on. Could you follow all the
symlinks and verify that it is in fact ELF? Also can you remove this file
and remake it? If it is ELF it must be corrupted in some way.

Vitaliy.

[Dan Kegel]

On 12/16/05, Vitaliy Margolen <wine-devel(a)kievinfo.com> wrote:
> > $ wine/wine .wine/drive_c/windows/system32/regsvr32.exe
> > wine: cannot open builtin library for
> > L"Z:\\home\\dank\\.wine\\drive_c\\windows\\system32\\regsvr32.exe":
> > /home/dank/wine/programs/regsvr32.exe.so: invalid ELF header
>
> Yeah. The only time I have seen this message in relation to regsvr32.exe
> is only when Wine's builtin regsvr32.exe.so was overwritten with native
> PE executable.  ...
> In this case I don't know then what is going on. Could you follow all the
> symlinks and verify that it is in fact ELF? Also can you remove this file
> and remake it? If it is ELF it must be corrupted in some way.

No, it's ELF, and it's not corrupted.  As I wrote a few posts ago,
the problem was caused by having an old copy of wine installed
in /usr/local while running a new copy of wine from the build
directory.  Removing the old copy, and installing wine from the
build directory, fixes the problem; I can then run regsvr32 from
either the build directory or the installed copy without problems.

Nasty little troubleshooting problem.   I guess I have to be a lot
more careful, and make sure to uninstall all old copies of wine
before running new builds without installing.
- Dan

--
Wine for Windows ISVs: http://kegel.com/wine/isv

[Vitaliy Margolen]

Friday, December 16, 2005, 11:20:34 PM, Dan Kegel wrote:
> On 12/16/05, Vitaliy Margolen <wine-devel(a)kievinfo.com> wrote:
> > > $ wine/wine .wine/drive_c/windows/system32/regsvr32.exe
> > > wine: cannot open builtin library for
> > > L"Z:\\home\\dank\\.wine\\drive_c\\windows\\system32\\regsvr32.exe":
> > > /home/dank/wine/programs/regsvr32.exe.so: invalid ELF header
> >
> > Yeah. The only time I have seen this message in relation to regsvr32.exe
> > is only when Wine's builtin regsvr32.exe.so was overwritten with native
> > PE executable.  ...
> > In this case I don't know then what is going on. Could you follow all the
> > symlinks and verify that it is in fact ELF? Also can you remove this file
> > and remake it? If it is ELF it must be corrupted in some way.
> No, it's ELF, and it's not corrupted.  As I wrote a few posts ago,
> the problem was caused by having an old copy of wine installed
> in /usr/local while running a new copy of wine from the build
> directory.  Removing the old copy, and installing wine from the
> build directory, fixes the problem; I can then run regsvr32 from
> either the build directory or the installed copy without problems.

Ah I see. Will add this to the list of things to watch for then. Thank
you for taking time and figuring it out. The reason why I never seen this
before is because I don't have Wine installed. I'm running it from the
source tree. Saves me some some time and space on the hard-drive. And
extra log-in as root <g>

Vitaliy