Yellow Dog Linux

Hello everyone
I want Thanks All of for the nice knowledge of How YDL to compile now i an easily compile application ,After try two time finally my application compile properly, so Thanks again all of you

ldconfig doesn't seem to be a command any more in ydl 6.2.
I complied glib 2.15.6 successfully in attempts to get pango 1.21.2 to compile but the configure script still errors out on me saying: configure: error:*** Glib 2.14.0 or better is required. I figure the libs are not being found because I could not ldconfig after installing. Has ydl 6.2 changed this command?

edit: ok I needed to put /sbin/ldconfig in and it worked but pango still cant find glib. Not sure whats going on yet.

does the location of glib-2.15.6 come before the location of the standard glib in ld.so.conf?

For example, if glib-2.15.6 is in /usr/local/lib,is /usr/local/lib before /usr/lib

hello all... i did the yum groupinstall 'development tools' and it says no packages in any requested group available to install or update.... dopws that mean i have everything????

otakusupreme wrote:hello all... i did the yum groupinstall 'development tools' and it says no packages in any requested group available to install or update.... dopws that mean i have everything????

Maybe. Did you type development tools or Development Tools?

Unlike Windows, Linux is case sensitive. It might not make a difference here - but it might.

Be sure you try this exactly as written:

Code: Select all

yum groupinstall 'Development Tools'

An alternative way to tell is to use the which command to see if the C compiler binary gcc is present. Then, you can ask gcc what version it is. The two commands are:

which gcc
gcc --version

You should see an output similar to the following, if the development libraries are installed.

Code: Select all

[paulp@yurie ~]$ which gcc
/usr/bin/gcc
[paulp@yurie ~]$ gcc --version
gcc (GCC) 4.1.2 20071124 (Red Hat 4.1.2-42)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[paulp@yurie ~]$

Cheers,
Paul

juanito wrote:does the location of glib-2.15.6 come before the location of the standard glib in ld.so.conf?

For example, if glib-2.15.6 is in /usr/local/lib,is /usr/local/lib before /usr/lib

Yes. You'll need /usr/local/lib first.

Ron Rogers Jr. (CronoCloud)

I pasted exactly as above
yum groupinstall 'Development Tools'

I am getting

Code: Select all

Loading "installonlyn" plugin
Loading "protectbase" plugin
Setting up Group Process
Warning: Group Development Tools does not exist.
No packages in any requested group available to install or update

No ideas?

pablo wrote:No ideas?

What's your repo list look like?

Cheers,
Paul

Hi Paul,
It has been a while but it is whatever you Billb asked us to update it to in /etc/yum.repos.d/livna-stable.repo &
/etc/yum.repos.d/dribble.repo

I will check these two and report back. Is there anything I should be looking for to make sure I have the correct repos?

pablo wrote:Hi Paul,
It has been a while but it is whatever you Billb asked us to update it to in /etc/yum.repos.d/livna-stable.repo &
/etc/yum.repos.d/dribble.repo

I will check these two and report back. Is there anything I should be looking for to make sure I have the correct repos?

Not so much those two - but Yellow Dog Updates and Yellow Dog Base. That's where it's going to load the build tools from. If you're running YDL 6.2, Yellow Dog Extras should be disabled.

Cheers,
Paul

Nope, I am still running 6.1
I will do a yum repolist and report back, I will also check the contents to make sure they are OK.

I also have a problem with

Code: Select all

./configure

It simply doesnt work. It spits out an error message

Code: Select all

no such file or directory

or sth like (translating). There is really no such a dir there.

Any ideas how to solve? Tried on 2 diff src pkgs of completely independent programs.

Silgrin4D wrote:I also have a problem with

Code: Select all

./configure

It simply doesnt work. It spits out an error message

Code: Select all

no such file or directory

or sth like (translating). There is really no such a dir there.

Any ideas how to solve? Tried on 2 diff src pkgs of completely independent programs.

Did you expand the package first?

If you did, did you cd into the resultant directory? Also - not all src packages use autoconf - i.e. configure - although most do.

When in doubt, always check to see if there's any documentation included. There's usually a README file in the archive that explains how to build it.

Cheers,
Paul