I’m trying to compile the program WinFF from source.
I used this application all the time with openSUSE 11.2, and Ubuntu but Packman has no package for 11.3
I know I could ask for it to be repackaged and someone would probably do it but I would like to take the opportunity to try something new. (for me anyway)
I found some useful step by step instructions and read some sticky posts by Oldcpu and gave it a go. I didn’t get very far.
As you can see in my posting below when I unpacked the tar ball and went to run the configure command and there I hit a snag.
Once you have downloaded either one of them (depending on your computer architecture) install it. For example for 64-bit (become root first by doing su -):
cd /location/where/the/winff/rpm/file/is
zypper in winff-1.3.0-0.pm.1.2.x86_64.rpm
Thanks for the reply. It installs but when i try to run it I get an error window that says “Access violation press ok to risk data corruption or cancel to kill program”
I’m using 32 bit. Perhaps that’s where the difference is
While I do not want to interfere in your discussion, I want to point out that the compilation is NOT sometthing to be done as root. You should do the unpacking, the configure and the make steps as a normal user. Only the instal step should be done as root.
linuxminded wrote:
> Could that be causing my problems with trying to compile the
> program or install the rpm from 11.2?
anything done which does not comply with standard practices can
(more likely will) cause problems, instability, insecurity, system
failure etc etc etc…
i may have missed one, but so far i have never seen a competently
written README which instructed the user to become root for configure
or make…on the other hand i’ll bet several thousand how-to-compile
guides clearly say to never run configure or make as root, ever!
note: It is far easier to read, understand and follow the instructions
than to undo the problems caused by not.
–
DenverD
CAVEAT: http://is.gd/bpoMD [posted via NNTP w/openSUSE 10.3]
Be it ever so humble, there is no place like 127.0.0.1.
I realy do not know. When you do this as root it means to me that you are doing more as root. Where do you have all sorts of files you downloaded, interneiaite results, etc.? Those should all be within a user owned environment (most probably inside your home directory), but when you are more or less loged in as root a long time, it is very easy to put files on places where they should not be, or remove thiings by accident, etc.
I agree. I read all the ReadMe files and none included instructions etc. They only had program descriptions like are displayed in Yast to tell what it does.
Anyway, I’m still stuck with not being able to run the configure comand either as normal or root.
Oh and just to clarify. I don’t make it a habit to go mucking around as Root. I switched over after the command failed as normal user the first time.
I also tried to convert the old RPM using the “rpm --rebuilddb” command and got the same error when I started the program as when I tried to install the old RPM.
Maybe it’s time to say **** on it and learn how to run FFmpeg from the command line. Seems like the easiest solution.
I only posted because you were using root where not needed and the others did not comment on that. I did not read your post thouroughly. I now tried, but I am hampered by the fact that you did not post computer output between CODE tags (Posting in Code Tags - A Guide).
But I see that you used cd to go to a directory (where all the unpacked stuff is), then an ls there to show what is there (the same things that were allready shown by the tar output). As you can see there is no configure there, thus doing ./configure is not a sensible thing to do. But there is a README.txt. Does it say you must do the ./configure?
And then of course, please move the whole bunch there to a directory within your home directory. It should not be in /usr/local because you are not root when handling this.