Jeff Squyres wrote: ...
This happens despite the fact that the libaio RPM is installed (this is on FC2/FC3, btw). This RPM installs /usr/lib/libaio.so.1.0.0 and (IIRC) /usr/lib/libaio.so.1 (sym link to libaio.so.1.0.0). The problem here is that libaio.so is not found -- which is apparently what the linker is looking for. Taking this down to the simplest case, if you:gcc foo.c -o foo -laioit'll fail, because libaio.so is not there (even though libaio.so.* is there).
...
So it seems that none of them require libaio.so directly -- they all require libaio.so.something. So packman/depman is doing exactly the Right Thing in Bernard's case: it is finding the libaio RPM, which contains libaio.so.1.0.0. It is *not* finding the libaio-devel RPM (which contains libaio.so) because there is no requirement to do so.
This tells me there *should* be a requires for libaio.so in the package containing mpicc. That is, after all, what explicit dependencies are for--cases where the auto-dependency scanner fails.
-- David N. Lombard Rossmoor, Orange County, CA http://www.fourmilab.ch/cgi-bin/uncgi/Earth?imgsize=320&opt=-z&lat=33.8&ns=North&lon=118.08&ew=West&alt=7&img=learth.evif ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
