Regression help please

A Nonny Moose · Post by **A Nonny Moose** » Thu Feb 09, 2012 4:06 pm

I have run the regression procedure from the wiki page and when I did the install command I got this:

Can I continue the regression, or is something really wrong?

This is my reported software environment.

Description: Linux Mint 11 Katya
Release: 11
wine1.3:
Installed: 1.4~rc2-0ubuntu1~ppa1~natty1
Candidate: 1.4~rc2-0ubuntu1~ppa1~natty1
Version table:
*** 1.4~rc2-0ubuntu1~ppa1~natty1 0
500 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu/ natty/main amd64 Packages
100 /var/lib/dpkg/status
1.3.15-0ubuntu5 0
500 http://archive.ubuntu.com/ubuntu/ natty/universe amd64 Packages

Mint is a Ubuntu derivative.

Das Letzte Einhorn · Post by **Das Letzte Einhorn** » Thu Feb 09, 2012 4:40 pm

You should compile wine from source if you are to do regression testing. Read http://wiki.winehq.org/GitWine for instructions.

Post by **dimesio** » Thu Feb 09, 2012 5:28 pm

A Nonny Moose wrote:I have run the regression procedure from the wiki page and when I did the install command I got this:

You don't install when doing a regression test; run it from the build directory.

A Nonny Moose · Post by **A Nonny Moose** » Fri Feb 10, 2012 7:38 am

sorry, somewhere in there my console log got lost.

This is what actually happened. Must have stepped on my clipboard

john@john-Mint-test ~/wine-git $ ./wine program.install.exe
wine: cannot find L"C:\\windows\\system32\\program.install.exe"

Is this a symptom of a missing library (ia32 perhaps)?

Post by **dimesio** » Fri Feb 10, 2012 7:44 am

A Nonny Moose wrote:sorry, somewhere in there my console log got lost.

This is what actually happened. Must have stepped on my clipboard

john@john-Mint-test ~/wine-git $ ./wine program.install.exe
wine: cannot find L"C:\\windows\\system32\\program.install.exe"

Is this a symptom of a missing library (ia32 perhaps)?

No, it's a symptom of the installer not being in the wine-git directory. You need to use the full path.
http://wiki.winehq.org/FAQ#head-3b297df ... b8edc21619

A Nonny Moose · Post by **A Nonny Moose** » Fri Feb 10, 2012 7:53 am

Odd. I was in the /home/john/wine-get directory as you can see from the log. I had just finished the make and wanted to install. Is there something wrong with the instructions in the wiki page?

Post by **dimesio** » Fri Feb 10, 2012 8:05 am

A Nonny Moose wrote:Odd. I was in the /home/john/wine-get directory as you can see from the log. I had just finished the make and wanted to install. Is there something wrong with the instructions in the wiki page?

You still aren't getting it: unless you copied the installer.exe to the wine-git directory, Wine has no way of knowing where it is unless you tell it, and that means using the full path to the installer.

Read the section of the FAQ I linked you to.

A Nonny Moose · Post by **A Nonny Moose** » Fri Feb 10, 2012 8:17 am

Now I really am confused. I was following the script at:
http://wiki.winehq.org/RegressionTestin ... 2a8e547b12

Specifically:

Once Wine's compiled, test for the bug. To be safe, we want to test with a clean .wine directory.

mv ~/.wine ~/.wine-backup

Install the application from scratch:

./wine program_install.exe <----------------

And if this is incorrect, I really am at a loss.

Post by **dimesio** » Fri Feb 10, 2012 8:34 am

A Nonny Moose wrote: ./wine program_install.exe <----------------

And if this is incorrect, I really am at a loss.

You have to substitute the actual path to the installer for your app for program_install.exe.

This is basic command line usage. If you don't specify the full path, Wine looks for the installer in whatever directory you're in. In this case, you're in the wine-git directory, so that's where Wine is looking for the program installer.

You could copy the installer to the wine-git directory so you don't have to specify the full path, but you will still have to specify the real name of the installer file in the command.

A Nonny Moose · Post by **A Nonny Moose** » Fri Feb 10, 2012 8:47 am

It may seem bone-headed of me, but I think that line should contain an obvious non-terminal. Anyone reading it would take it verbatim, as I did. Stuff like that should look like this:

./wine <program_install.exe>

So, the next question involves needed libraries.

If I have created a new wineprefix per the instructions can I just use winetricks to install the libraries I need or do I have to do further handsprings?

I've done one of these about a year ago, and it didn't seem to be a problem then.

doh123 · Post by **doh123** » Fri Feb 10, 2012 9:14 am

A Nonny Moose wrote:It may seem bone-headed of me, but I think that line should contain an obvious non-terminal. Anyone reading it would take it verbatim, as I did. Stuff like that should look like this:

./wine <program_install.exe>

So, the next question involves needed libraries.

If I have created a new wineprefix per the instructions can I just use winetricks to install the libraries I need or do I have to do further handsprings?

I've done one of these about a year ago, and it didn't seem to be a problem then.

I think its telling you what you need to know without teaching you how to use a command line... assuming people trying to use this already know command line basics.

normally in Wine you'd cd into the folder containing the exe file, so it will be able to find it because it looks at the current folder. If your running in a different folder using ./wine so it doesn't use the wine command in your path, your not in the folder where the exe file is.

me, I'd usually just alter my $PATH for that one terminal session...
export PATH="<full path to wine build where wine executable is>:$PATH"
which would put that folder earlier in the path than where your normal installed wine is. so when you just type "wine" it would find it first in your build folder where your doing the testing. then you could use the wine command normally, and it would run the one in the build folder... at least for that terminal session.

Post by **dimesio** » Fri Feb 10, 2012 9:17 am

A Nonny Moose wrote: If I have created a new wineprefix per the instructions can I just use winetricks to install the libraries I need or do I have to do further handsprings?

You can use winetricks, but you will have to tell it to use the Wine you compiled yourself or it will use the one installed on your system:

Code: Select all

WINEPREFIX=/path/to/wineprefix WINE=/path/to/wine-git/wine sh winetricks whatever

(substitute the actual paths and winetricks verb; if winetricks is installed from a distro package, you don't need the sh)

If you don't do that, Wine will update the wineprefix to your installed version when you run winetricks, then your wine-git Wine will update it again when you run the app using that version. That may not make a difference, but it does have the potential to cloud your test results.

A Nonny Moose · Post by **A Nonny Moose** » Fri Feb 10, 2012 9:26 am

Since my new wineprefix is at the ~ level (/home/john) created by simply moving the old one to .wine.backup per the instructions, I guess I am OK to just operate from the wine-git directory with normal commands because if the new version picks up the wineprefix by default it should be cool.

I am probably reading more into this than I should. Will post again if I fail.

jjmckenzie · Post by **jjmckenzie** » Fri Feb 10, 2012 11:05 am

On Fri, Feb 10, 2012 at 7:26 AM, A Nonny Moose
<[email protected]> wrote:

Since my new wineprefix is at the ~ level (/home/john) created by simply moving the old one to .wine.backup per the
instructions, I guess I am OK to just operate from the wine-git directory with normal commands because if the new
version picks up the wineprefix by default it should be cool.

A Nonny:

I use a script for building created by Ryan for OSX called
osxwinebuilder. Google for it and you should find it.

When it exits, it gives two lines for setting the PATH and the dynamic
library path. It should be editable to work with any version of
Linux.

This is what I use for building/testing given the short cycles for the
Release Candidates.

James

A Nonny Moose · Post by **A Nonny Moose** » Fri Feb 10, 2012 11:19 am

[quote="jjmckenzie"]On Fri, Feb 10, 2012 at 7:26 AM, A Nonny Moose
<[email protected]> wrote:
[quote]Since my new wineprefix is at the ~ level (/home/john) created by simply moving the old one to .wine.backup per the
instructions, I guess I am OK to just operate from the wine-git directory with normal commands because if the new
version picks up the wineprefix by default it should be cool.

[/quote]A Nonny:

I use a script for building created by Ryan for OSX called
osxwinebuilder. Google for it and you should find it.

When it exits, it gives two lines for setting the PATH and the dynamic
library path. It should be editable to work with any version of
Linux.

This is what I use for building/testing given the short cycles for the
Release Candidates.

James[/quote]

James, thanks. I am on Linux Lm11 currently and have fixed my path to place the wine-get directory at the top of the path list. Since I have other problems that are causing me to reboot occasionally, I was thinking of updating my profile to test for the directory and to it automatically.

Last test went fine once I straightened out some permissions. Crashed as expected, so I am now going on to bisection.

Thanks for the thoughts,

John.

A Nonny Moose · Post by **A Nonny Moose** » Fri Feb 10, 2012 2:13 pm

Finished bisecting between 1.4-rc1 and 1.4-rc2. All tests uniformly bad.

I wonder if I might have missed this in my tests of rc1?

Is it possible to create rc1 and test again?

There is also a possibility I found a bug in the app (SimCity 4 Deluxe), but I am active in the bugs forum on Stimtropolis and this would be a new one. This app has been unchanged by the vendor since 2003. Besides, it is not consistent so far as the app goes, but it does seem to be consistent in wine.

Should I just report this on Bugzilla and stop or can I continue hunting somehow?

Post by **dimesio** » Fri Feb 10, 2012 2:59 pm

A Nonny Moose wrote:Finished bisecting between 1.4-rc1 and 1.4-rc2. All tests uniformly bad.

I wonder if I might have missed this in my tests of rc1?

Is it possible to create rc1 and test again?

There is also a possibility I found a bug in the app (SimCity 4 Deluxe), but I am active in the bugs forum on Stimtropolis and this would be a new one. This app has been unchanged by the vendor since 2003. Besides, it is not consistent so far as the app goes, but it does seem to be consistent in wine.

Should I just report this on Bugzilla and stop or can I continue hunting somehow?

There are several possibilities, one of which is that the commit that caused this did occur earlier than 1.4-rc2 and you just didn't notice. To test that, do git bisect reset, and start over with git bisect bad set at 1.4-rc1 and git bisect good at 1.3.37 (or even earlier).

The other possibilities are that a change to something else in your system is causing the problem, or that a change in Wine (or something else on your system) has exposed a bug in the game (or something else on your system).

A Nonny Moose · Post by **A Nonny Moose** » Fri Feb 10, 2012 3:15 pm

Currently testing with rc2, and running fine. I guess I found a bug in the app that has been unreported. I'll post this on bugzills.

Well, it was an interesting learning experience.

For what it is worth, there are some .profile changes that might benefit other people doing this type of testing.

# set PATH so it includes user's wine-git if it exists
if [ -d "$HOME/wine-git" ] ; then
PATH="$HOME/wine-git:$PATH"
fi

# a convenience for long compiles
CC="ccache gcc"
export CC

These are for the /home/<user>.profile in Linux.

All you have to do is change the name of wine-git to something like wine-git.hold using the mv command and the default in the path reverts on the next login.

Post by **dimesio** » Fri Feb 10, 2012 4:30 pm

A Nonny Moose wrote:Currently testing with rc2, and running fine. I guess I found a bug in the app that has been unreported. I'll post this on bugzills.

You updated the wrong bug. Your bug is 29837, you left a comment in bug 7387.

A Nonny Moose · Post by **A Nonny Moose** » Fri Feb 10, 2012 4:49 pm

Damn. Can you fix it for me. I don't think I have edit power over there.

Post by **dimesio** » Fri Feb 10, 2012 5:39 pm

A Nonny Moose wrote:Damn. Can you fix it for me. I don't think I have edit power over there.

I can't delete comments in bugzilla. Just add a comment to the wrong bug that your previous comment was for a different bug and add a comment to your bug that the game is working now for you.

A Nonny Moose · Post by **A Nonny Moose** » Fri Feb 10, 2012 5:49 pm