I’m not a programmer or sys-admin , i’m just a newby that got tired of my Windows OS being hacked and hacked…So i switched to Linux
I downloaded SUSE Leap 42.2 and installed and installed…
I went onto Yast > software manager and typed GCC and it and its set to get GCC 32bit… i downloaded and no programs would compile , (missing cc and other probs)
So i clicked each box and downloaded everything related to GCC and now its compiling okay… ( you guys (coders) need to be sure to include everything you need to compile)
I downloaded Audacity and its missing an mp3 lib called libmp3lame.so.o , so i downloaded the source (only available in source form) , for lame and it finally compiled and installed okay…(with all the GCC megabytes of compilers downloaded)
I downloaded a program called “Nulloy” to play mp3’s and out of the box its missing some kind of GStreamer plugin , so i typed Gstreamer in to the software mgr and clicked on everything and now it’s working okay…
I thought of making my own Linux distro… Where every program goes into its own dir
So GCC 6 would go in
/GCC 6
/GCC 6 /bin
/GCC 6 /etc ( where the config files go…)
/GCC 6 /lib
/GCC 6 /doc ( for docs)
etc…
Then you could run different versions of apps side by side, one login might run version 2 and another login might use version 4…or you might have two versions running at the same time on the same desktop…
Someone told me there’s a distribution called “GOBO Linux” that already does this??
You would have to be a good programmer to accomplish it , because most source codes are full of hardcoded dirs…you’d have to alter the sources…
Then you get rid of the PATH , and use a search engine to find the bin dirs and list out the different versions to launch…
Then all the dependencies could be found under the working dir.
If a program uses a different programs libs then it would create softlinks the the prog-name/lib dir…
Thank you , just telling you about the problems of a newby…
You say you are not a programmer. nevertheless you want to have cc and it’s environment installed.
Use YaST > Software > Software Manager. Then from the View menu (somewhere up-left) choose Patterns. Scroll down to Developments and check at least Basic Development and C/CC++ Development for installation. It will give you good start.
I do not understand your story about Audacity. When it is not already installed, you should install it using YaST > Software > Software Management. But after that it is important to start using the Packman repo. There are several sticky threads at the Multimedia section here on the forums that explain it.
To add the Packman repo:
YaST > Software > Repositories Management. Then the Add button below. Choose Community Repositories in the next screen and click Next. Select Packman from the list shown and click OK. The Packman repo will now be added to your list of subscribed repositories.
To do the Vendor switch:
YaST > Software Management, then from the View menu choose Repositories. Then in the list of repos, select Packman. At right, above the list of Packages there is a line saying something like: Switch system packages to … Click on the underlined part and continue low-right.
I got Lame compiled , ./configure , make , make install… Now Audacity is exporting to MP3 format…
It won’t load MP3’s though. They say you have to compile the source to include mp3 support.
And i can’t figure out all the dependencies, it uses WX-widgets and a bunch of other dependancies , and it says it can’t find a lib with “dlopen” in it.
So i can’t compile the Audacity source…, So i just open the mp3’s in “Nulloy” to play them back…
On Tue, 28 Mar 2017 19:36:01 +0000, Albert Redditt wrote:
> Thank you…
>
> I got Lame compiled , ./configure , make , make install… Now Audacity
> is exporting to MP3 format…
>
> It won’t load MP3’s though. They say you have to compile the source to
> include mp3 support.
> And i can’t figure out all the dependencies, it uses WX-widgets and a
> bunch of other dependancies , and it says it can’t find a lib with
> “dlopen” in it.
> So i can’t compile the Audacity source…, So i just open the mp3’s in
> “Nulloy” to play them back…
I followed your advice and outline and got the packman repository and got Audacity and its working with mp3’s now , thank you…(its loading mp3’s) no need to compile source.
The SUSE coders need to install a base linux system on a testbed computer , and then load 1 program at a time (or source code of 1 prog at a time) , and check dependencies. ( see if it runs or compiles.) and what libs or other progs it needs.
Then it would be easy to install a complete SUSE system from CD/DVD without need for downloading except for new prog version releases…
Good idea for SUSE 43
Thank you for the info!!
Whats the difference between Packman and the default SUSE repositories ??
openSUSE never has (and never will ) ship with closed source / patented software. Full multimedia support is easily obtained in openSUSE by following the sticky guide in the Multimedia section of these forums. Should really be the first point of call following a new install. https://forums.opensuse.org/showthread.php/521016-Multimedia-Guide-for-openSUSE-Leap-42-2
no need to compile audacity or lame or most other multimedia requirements . . . it’s all there in packman
Note the name openSUSE. It only ships with open source MP3 is patent encumbered so openSUSE will never ship with proprietary software. If you want or need proprietary codecs then you need to get them from packman. You do not have to compile anything just do the vender change and all is good.
openSUSE is a community project if you would like to contribute maybe do some testing of the next version;)
You currently can install a ‘complete OpenSuse’ by downloading the dvd. It takes a while as it contains 4.7 gig of software. There is a panel shown during install that allows additional software items over a basic install to be selected. I usually install that way as it’s quicker. Even if lots of additional software is installed it’s still a quick process.
When you add software with yast or the dvd only supported software is available. While application names between different distributions may be the same the software needed to make them run differs. It takes time for the people who produce the distro’s to get them to work correctly so generally supported applications wont be the latest greatest. They are usually varying degrees of release behind. Often newer versions wont be offered in a release that are also supported. If they are installed they may interfere with the dependencies of the supported software or simply can’t run with the supported software set up.
This does allow more recent releases of packages to be installed often the latest. It offers those in unsupported versions along with a warning. Results vary and they can cause problems. Pretty serious ones. Worse still there is often several potential sources of the same package. I do use a couple as they have been reliable long term. One thing I never do is leave the repo active. They can be made inactive in yast unset enable and refresh. I don’t leave packman enabled now as I have had 2 update problems that are down to using it. One probably due to my set up which needed a newer release of vlc. Previously I have obtained codec from a site called opensuse community. No idea if that is still ok.
Sounds like you have already compiled. I do sometimes but I feel there is more risk now than in the past. Often when ./configure is entered lots of files will seem to be missing. Often that’s just the devel version which are the headers to allow other software to make use of them. If a library is missing yast can usually find it. If not best forget it. Some apps will use cmake too rather than the old way.
On Tue, 28 Mar 2017 23:56:01 +0000, Albert Redditt wrote:
> Hello Sir;
>
> I followed your advice and outline and got the packman repository and
> got Audacity and its working with mp3’s now , thank you…(its loading
> mp3’s) no need to compile source.
>
> The SUSE coders need to install a base linux system on a testbed
> computer , and then load 1 program at a time (or source code of 1 prog
> at a time) , and check dependencies. ( see if it runs or compiles.) and
> what libs or other progs it needs.
openSUSE uses the openQA framework (which SUSE created, as I recall) to
do testing. Lots of stuff is tested, and yes, lots of dependency
checking goes on.
But it’s all package based, because packages are what users are expected
to use rather than building from source. Building software from source
is an advanced topic, and it’s expected that you know or are learning how
to resolve dependencies because there are countless ways in which
dependencies are met.
That’s part of software development in general. Also remember that the
“SUSE coders” are not a team of coders at SUSE who write every line of
code on the system you’re using - the packages come from thousands upon
thousands of developers around the world. Each software package is
generally an independent group of people ‘scratching their particular
itch’ to solve a particular problem or to implement something they find
interesting.
When it comes to the openSUSE Project, the “SUSE coders” are members of
the community.
> Then it would be easy to install a complete SUSE system from CD/DVD
> without need for downloading except for new prog version releases…
>
> Good idea for SUSE 43
>
> Thank you for the info!!
>
> Whats the difference between Packman and the default SUSE repositories
> ??
Packman is additional software - it’s got things that are not, as others
have noted, “open” (by open source software definitions).
