[Bug bootstrap/50049] bootstrap fails if libcloog in unusual spot, even with --with-cloog= set

2011-08-11 Thread rbrt.somerville at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50049

--- Comment #1 from robert somerville rbrt.somerville at gmail dot com 
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] bootstrap fails if libcloog in unusual spot, even with --with-cloog= set

2011-08-11 Thread pinskia at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50049

Andrew Pinski pinskia at gcc dot gnu.org changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||WONTFIX

--- Comment #2 from Andrew Pinski pinskia at gcc dot gnu.org 2011-08-11 
19:26:26 UTC ---
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.


[Bug bootstrap/50049] bootstrap fails if libcloog in unusual spot, even with --with-cloog= set

2011-08-11 Thread rbrt.somerville at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50049

--- Comment #3 from robert somerville rbrt.somerville at gmail dot com 
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

2011-08-11 Thread pinskia at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50049

--- Comment #4 from Andrew Pinski pinskia at gcc dot gnu.org 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.


[Bug bootstrap/50049] bootstrap fails if libcloog in unusual spot, even with --with-cloog= set

2011-08-11 Thread rbrt.somerville at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50049

--- Comment #5 from robert somerville rbrt.somerville at gmail dot com 
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 pinskia at gcc dot gnu.org 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

2011-08-11 Thread rbrt.somerville at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50049

--- Comment #6 from robert somerville rbrt.somerville at gmail dot com 
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

2011-08-11 Thread rbrt.somerville at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50049

--- Comment #7 from robert somerville rbrt.somerville at gmail dot com 
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 )