[Bug bootstrap/50049] bootstrap fails if libcloog in unusual spot, even with --with-cloog= set
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50049 --- Comment #7 from robert somerville 2011-08-11 19:57:18 UTC --- i believe that the build should use the static libcloog that exists, after all the build has no problems with MPC,MPFR,GMP, and PPL needing an LD_LIBRARY_PATH , which are also in a non-standard location ( the same as libcloog )
[Bug bootstrap/50049] bootstrap fails if libcloog in unusual spot, even with --with-cloog= set
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50049 --- Comment #6 from robert somerville 2011-08-11 19:56:06 UTC --- i believe that the build should use the static libcloog that exists, after all the build has no problems with MPC,MPFR,GMP, and PPL needing an LD_LIBRARY_PATH
[Bug bootstrap/50049] bootstrap fails if libcloog in unusual spot, even with --with-cloog= set
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50049 --- Comment #5 from robert somerville 2011-08-11 19:42:37 UTC --- i have a static cloog library in there .. is there a compiler/configure option i was supposed to use ??? On Thu, Aug 11, 2011 at 1:39 PM, pinskia at gcc dot gnu.org < gcc-bugzi...@gcc.gnu.org> wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50049 > > --- Comment #4 from Andrew Pinski 2011-08-11 > 19:39:04 UTC --- > (In reply to comment #3) > > "" In both cases --with-cloog configure option should be used if CLooG is > not > > installed in your default library search path. "" > > That is for built time library search path. If you use a shared library > rather > than a static archive then you also need to set up the runtime path. > > -- > Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email > --- You are receiving this mail because: --- > You reported the bug. >
[Bug bootstrap/50049] bootstrap fails if libcloog in unusual spot, even with --with-cloog= set
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50049 --- Comment #3 from robert somerville 2011-08-11 19:29:48 UTC --- (In reply to comment #2) > >i seem to have to have LD_LIBRARY_PATH set to point to libcloog library > > That is a standard non issue really as you are support to have the shared > libraries in a spot that can be found at runtime while building GCC. then why the --with-cloog= option ?? , see documentation for building . i quote: "" In both cases --with-cloog configure option should be used if CLooG is not installed in your default library search path. ""
[Bug bootstrap/50049] bootstrap fails if libcloog in unusual spot, even with --with-cloog= set
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50049 --- Comment #1 from robert somerville 2011-08-11 19:25:31 UTC --- Created attachment 24986 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24986 sorry, lost attachment first time config.log
[Bug bootstrap/50049] New: bootstrap fails if libcloog in unusual spot, even with --with-cloog= set
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50049 Bug #: 50049 Summary: bootstrap fails if libcloog in unusual spot, even with --with-cloog= set Classification: Unclassified Product: gcc Version: 4.6.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap AssignedTo: unassig...@gcc.gnu.org ReportedBy: rbrt.somervi...@gmail.com i seem to have to have LD_LIBRARY_PATH set to point to libcloog library directory ... --with-cloog= or --with-cloog-lib= is not enough . It fails when it goes into stage 1, it cannot find libcloog to complete a link. I am under impression i should not have to have LD_LIBRARY path set to do a bootstrap w.r.t. libcloog attaching: objdir/x86_64-unknown-linux-gnu/libgcc/config.log
