I tried using the command "yum whatprovides stddef.h" to locate the include library last night. Yum when through its process and came up with nothing in a fairly short order.
Am I not using the command correctly?
Jeff
Try 'yum provides *stddef.h'
On 6/30/07, Jeffrey Ross jeff@bubble.org wrote:
I tried using the command "yum whatprovides stddef.h" to locate the include library last night. Yum when through its process and came up with nothing in a fairly short order.
Am I not using the command correctly?
Jeff
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Around 02:48pm on Saturday, June 30, 2007 (UK time), Michael H. Semcheski scrawled:
Try 'yum provides *stddef.h'
Though 'yum provides stddef.h' should work, and even yum whatprovides stddef.h' works for me on FC6.
Steve
For me, I have to use the wildcard in FC7. Which is kind of annoying.
Mike
On 6/30/07, Steve Searle steve@stevesearle.com wrote:
Around 02:48pm on Saturday, June 30, 2007 (UK time), Michael H. Semcheski scrawled:
Try 'yum provides *stddef.h'
Though 'yum provides stddef.h' should work, and even yum whatprovides stddef.h' works for me on FC6.
Steve
--
Play Champions - my free football predictions game at: http://www.stevesearle.com/champs/about.html
15:37:30 up 4 days, 19:17, 0 users, load average: 0.01, 0.02, 0.00
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Jeff, You must supply the path to the command to succeed: yum whatprovides /usr/lib/bcc/include/stddef.h ----- dev86-0.16.17-2.2 -----
Regards --- Jeffrey Ross jeff@bubble.org wrote:
I tried using the command "yum whatprovides stddef.h" to locate the include library last night. Yum when through its process and came up with nothing in a fairly short order.
Am I not using the command correctly?
Jeff
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Linux user number 433512 "Free as in Freedom": http://counter.li.org
____________________________________________________________________________________ Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=list&sid=396545469
On Sat, 2007-06-30 at 13:46 -0700, Ed Landaveri wrote:
Jeff, You must supply the path to the command to succeed: yum whatprovides /usr/lib/bcc/include/stddef.h
dev86-0.16.17-2.2
If that was true there wold be no need for whatprovides. The output you indicate could be gotten from: rpm -qf /usr/lib/bcc/include/stddef.h
-- ======================================================================= Better late than never. -- Titus Livius (Livy) ======================================================================= Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@sbcglobal.net
On 6/30/07, Aaron Konstam akonstam@sbcglobal.net wrote:
On Sat, 2007-06-30 at 13:46 -0700, Ed Landaveri wrote:
Jeff, You must supply the path to the command to succeed: yum whatprovides /usr/lib/bcc/include/stddef.h
dev86-0.16.17-2.2
If that was true there wold be no need for whatprovides. The output you indicate could be gotten from: rpm -qf /usr/lib/bcc/include/stddef.h
If you have the package installed. The purpose of yum whatprovides is that you know what package to install to get a certain file.
Andras
On Sat, 2007-06-30 at 23:05 +0200, Andras Simon wrote:
On 6/30/07, Aaron Konstam akonstam@sbcglobal.net wrote:
On Sat, 2007-06-30 at 13:46 -0700, Ed Landaveri wrote:
Jeff, You must supply the path to the command to succeed: yum whatprovides /usr/lib/bcc/include/stddef.h
dev86-0.16.17-2.2
If that was true there wold be no need for whatprovides. The output you indicate could be gotten from: rpm -qf /usr/lib/bcc/include/stddef.h
If you have the package installed. The purpose of yum whatprovides is that you know what package to install to get a certain file.
Andras
I was being too obscure. If stdef.h was not installed you would not know that it should be installed in usr/lib/bcc/include/stddef.h -- ======================================================================= Honesty is the best policy, but insanity is a better defense. ======================================================================= Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@sbcglobal.net
Jeffrey Ross wrote:
I tried using the command "yum whatprovides stddef.h" to locate the include library last night. Yum when through its process and came up with nothing in a fairly short order.
Am I not using the command correctly?
Jeff
Is it possible you were not running the command while you were logged in as root ?
~~R
"JR" == Jeffrey Ross jeff@bubble.org writes:
JR> I tried using the command "yum whatprovides stddef.h" to locate JR> the include library last night. Yum when through its process and JR> came up with nothing in a fairly short order.
Which is not surprising since there is no package which provides "state's.h". However, the kernel-headers package provides /usr/include/linux/stddef.h; you simply need to give a full path to the file you're trying to find.
- J<
At 6:09 PM -0500 6/30/07, Jason L Tibbitts III wrote:
"JR" == Jeffrey Ross jeff@bubble.org writes:
JR> I tried using the command "yum whatprovides stddef.h" to locate JR> the include library last night. Yum when through its process and JR> came up with nothing in a fairly short order.
Which is not surprising since there is no package which provides "state's.h".
What does "'states.h'" have to do with "stddef.h"?
However, the kernel-headers package provides /usr/include/linux/stddef.h; you simply need to give a full path to the file you're trying to find.
I've seen this wrong answer twice now, and also the correct answer that one does not need to provide a full path. If only the filename is given, all the packages that provide stddef.h in any location are found; if the full path, only packages that provide it exactly there are found. This is on FC6; some report that on F7 it is necessary to say '*stddef.h'.
If yum is providing the answer quickly, it may well be that you ran it as a normal user (as suggested by another), and thus from the cache. Run it as root and yum will be able to download the filelist info.