Failed gcc link and targets
2 Davids, The output at the top of the compile after running: bjam "-sTOOLS=gcc" install > out.txt 2>&1 shows python errors followed by: ...found 13313 targets... ...updating 250 targets... And then throughout the compile there are a lot of link errors and FileClone operation not permitted errors. The the compile completes with a lot of skipped errors ending with: ....failed updating 110 targets... ...skipped 118 targets... ...updated 22 targets... So...the following list from the Boost site gave the order for compiling which I completed in order with my appended notes: 1. Download Boost http://boost.org/more/getting_started.html#step1. 2. Install Boost.Jamhttp://boost.org/more/getting_started.html#step2. ( I installed bjam to: /usr/local/bin/bjam) 3. Configure your compiler toolsethttp://boost.org/more/getting_started.html#step3. (This I did not do...I didn't know what they wanted me to do) 4. Go to Boost distribution directoryhttp://boost.org/more/getting_started.html#step4 . 5. Build and installhttp://boost.org/more/getting_started.html#step5 . Could some of this be the result of the fact that I didn't configure my compiler? Thanks guys... Douglas
Douglas,
FileClone operation not permitted errors.
Just out of curiosity, what kind of filesystem are you compiling boost on? FAT32 can't handle symbolic links and may produce that error message. That would explain why bjam can't find libraries to link to. Also I see preserving times Operation not Permitted, this would indicate a filesystem problem. If you are using a fat32 disk or partition to compile on, I would try using an ext3 partition as a test and see if you get the same results, or of boost compiles cleanly there. Hope this helps, - Dave On Sat, 2007-04-14 at 06:57 -0700, Douglas Linford wrote:
2 Davids,
The output at the top of the compile after running: bjam "-sTOOLS=gcc" install > out.txt 2>&1 shows python errors followed by:
...found 13313 targets... ...updating 250 targets...
And then throughout the compile there are a lot of link errors and FileClone operation not permitted errors.
The the compile completes with a lot of skipped errors ending with:
....failed updating 110 targets... ...skipped 118 targets... ...updated 22 targets...
So...the following list from the Boost site gave the order for compiling which I completed in order with my appended notes:
1. Download Boost. 2. Install Boost.Jam. ( I installed bjam to: /usr/local/bin/bjam) 3. Configure your compiler toolset. (This I did not do...I didn't know what they wanted me to do) 4. Go to Boost distribution directory. 5. Build and install. Could some of this be the result of the fact that I didn't configure my compiler?
Thanks guys... Douglas
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
David, Interesting observation....in actuality, I realized from your tip that I am compiling from a fat32 partition. I keep all of my data on an external USB drive that is partitioned half-n-half with a fat32 partition and a ext3 partition. And most of the data resides in the fat32 partition so that I can r/w my XP data from Zenwalk. And goofy me put the /MusicEditing/boost_1_33_1/ folder in the fat32 partition not thinking.... I will move all of the /MusicEditing/boost_1_33_1/ data over to the ext3 partition and try compiling from there. Thanks for the observation and tip...I'll let you know if that works. douglas
David, It looks like your idea and observation worked, at least in part. I moved my boost sources to the ext3 partition on my external drive and then I ran the following command from the boost_1_33_1 folder: bjam "-sTOOLS=gcc" install but...it looks like it compiled it and placed the header files in a boost folder that I was running it from and not in /usr/local where the default location should be. So when I run scons to compile ardour2, (a music editing program), it says the boost header files can not be found and are not installed. So....can I re-run the bjam command with the prefix option? bjam "-sTOOLS=gcc" --prefix=/usr/localinstall (would this be the correct syntax?) Or would that create other link problems since I already compiled it? douglas
Douglas Linford wrote:
So....can I re-run the bjam command with the prefix option?
bjam "-sTOOLS=gcc" --prefix=/usr/localinstall (would this be the correct syntax?)
Or would that create other link problems since I already compiled it?
You should be able to build as many times as you want. If there's nothing new to build it will just copy stuff to the new location. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
participants (3)
-
David Daeschler -
Douglas Linford -
Rene Rivera