I am directing this inquiry to the LXDE folks, since this is where I'm having my problem/issue.  Please indulge me for a moment while I explain (being a fellow SW developer, I understand the importance of details).

 -  I'm running 2 VirtualBox Virtual Machines:  One is the "stock" FedoraCore 21 release, the other is an LXDE Spin of the same release.

 -  The HOST OS for this is Mac OS X 10.10 Yosemite.  (15" MacBook Pro Retina w/16GB RAM, 512GB SSD)

 -  Both Virtual Machines are setup IDENTICALLY with respect to the # of CPU's (2), and the allocated Memory (8GB).  

 -  Both VM's share the same "shared folder" on disk.

 -  Storage for the VDI images is on a USB3 external HDD (slow I know, but works OK)

 -  The kernel version is:  {same on BOTH VM's}

[sbeckwith@localhost ~]$ uname -a

Linux localhost.localdomain 3.17.4-301.fc21.x86_64 #1 SMP Thu Nov 27 19:09:10 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

[sbeckwith@localhost ~]$ 

 -  I'm building test software that is comprised of a Linux kernel (older 2.6.32 vintage) with an RFS containing the necessary drivers/utilities/libraries and test applications for running diagnostics on an X86_64 CPU.  

 -  When I built the software on the FC21 machine, it runs fine, to completion.  

 -  When I build the EXACT SAME software in the LXDE version, I get a failure.  

Where the problem is a linking issue when trying to link the PCI library (libpci.so.3.3.0) with the application.  LD reports it can't find the -lpci library.  

Since this is building a stand-alone application, I was able to execute the build command on the command line to generate the attached "verbose" output, without the need of the top level build stuff.

 -  Attached are 2 text files:

FC21-Bld.txt - the verbose output from the command line command to build this application.   As shown in the "ls-l" at the bottom, the "pcix" application was successfully built.

FC-LXDE-Bld.txt - the verbose output from the command line command to build this application on the LXDE VM.  Here, it generates an error.  

BldDiff-1.txt - the difference between the two files (from DiffMerge) - 

The ONLY difference I can see (other than the order of the command line parameters, which should not be an issue) are the temporary files generated.  The -L switches in BOTH cases are the same, and will point to the /lib64 where this library resides.  

So. . .   Why does one work and the other one doesn't?  Given that I can reproduce this on the command line in my mind rules out any sort of race condition between the builds.   It would point to some underlying issue with how the link paths are handled somehow, so that in once case it works, and the other it does not.  

In my 30+ years of "embedded" software development, I've see some interesting build issues, but this one takes the cake.  

Any suggestions/pointers/hints would be GREATLY appreciated.  I'm at my whits end here. . .

Warmest Regards,

Stephen Beckwith