![]() |
Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
Jerry Feldman wrote: >> So you might check to make sure all the binutils (like 'as') for the 3.3.3 are >> in the right place. > > The way the company has things set up, they have an exported directory > that has all the gcc bits for all the platforms they support. Since I > can run this script on a nearly identical system in Toronto essentially > points to not having all the bits that I need from that export. While I > hate to do it, what I might do is import the original tools directory > from Toronto (I hate NFS across the Internet), but for the single > compile it would tell me that either we failed to copy all the bits we > needed, or that somehow we may be missing some packages from the > distro. Try running this on both the good Toronto system and one of the bad ones, and compare the output: strace -v -f make 2>&1 | grep "exec..(.*) = 0" That will tell you all the sub-programs that are being used (with their full path). You might add " | cut -b -80" to the end of that command to make it more human readable. Finally, if you're using ccache, you might want to clear the cache (either 'ccache -C' or 'rm -rf ~/.ccache') in case that's somehow fudging things up. Matt -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
![]() |
|
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |