[Bug regression/40516] New: using --with-cloog and --with-ppl without specifying a location with = causes configuration errors

[Bug regression/40516] New: using --with-cloog and --with-ppl without specifying a location with = causes configuration errors

[xenofears at gmail dot com]

results in:

(all from config.log)

configure:5144: checking for version 0.10 of PPL
configure:5166: gcc -c -I/usr/system64/include -L/usr/system64/lib
-L/usr/system64/lib64 -Iyes/include    -I/usr/system64/include
-L/usr/system64/lib -L/usr/system64/lib64 conftest.c >&5
configure:5172: $? = 0

configure:5265: checking for correct version of CLooG
configure:5287: gcc -c -I/usr/system64/include -L/usr/system64/lib
-L/usr/system64/lib64 -Iyes/include -DCLOOG_PPL_BACKEND    -Iyes/include 
-I/usr/system64/include -L/usr/system64/lib -L/usr/system64/lib64 conftest.c
>&5
configure:5293: $? = 0

LIBS='-Lyes/lib -lcloog -Lyes/lib -lppl_c -lppl -lgmpxx  '

clooginc='-Iyes/include -DCLOOG_PPL_BACKEND '
clooglibs='-Lyes/lib -lcloog'

As of recent with gcc 4.5.0, to use the CLOOG_PPL_BACKEND, --with-cloog and
--with-ppl must be specified in the command line, making this more notable.


-- 
           Summary: using --with-cloog and --with-ppl without specifying a
                    location with = causes configuration errors
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: regression
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: xenofears at gmail dot com
 GCC build triplet: x86_64-w64-mingw32, i686-pc-mingw32, i686-pc-cygwin
  GCC host triplet: x86_64-w64-mingw32
GCC target triplet: x86_64-w64-mingw32


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40516

[Bug regression/40516] using --with-cloog and --with-ppl without specifying a location with = causes configuration errors

[nightstrike at gmail dot com]

------- Comment #1 from nightstrike at gmail dot com  2009-06-25 13:58 -------
I imagine this applies to any target, not just win64 targets.  I can't change
that setting, though.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40516

[Bug regression/40516] using --with-cloog and --with-ppl without specifying a location with = causes configuration errors

[xenofears at gmail dot com]

------- Comment #2 from xenofears at gmail dot com  2009-06-25 20:44 -------
(In reply to comment #1)
> I imagine this applies to any target, not just win64 targets.  I can't change
> that setting, though.

I am quite sure it applies to any target, but I am unable to test any target.
Feel free to post verifications of other targets. I should have listed the
other ones I know it applies to - like I did for build - and updated that.

This bug needs to be confirmed.


-- 

xenofears at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 GCC target triplet|x86_64-w64-mingw32          |x86_64-w64-mingw32, i686-pc-
                   |                            |cygwin,i686-pc-
                   |                            |mingw32,x86_64-unknow


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40516

[Bug bootstrap/40516] --without-mpc, --without-ppl, --without-cloog does the same thing. No turning off mpc via configure.

[xenofears at gmail dot com]

------- Comment #3 from xenofears at gmail dot com  2009-06-30 07:38 -------
I have now, in an attempt at a testcase, have found this bug to have further
implications. Trying to turn off mpc, ppl, and/or cloog has the same behavior,
i.e. --without-mpc causes:

gmpinc: '-I/no/include'
gmplibs: '-L/no/lib -lmpc -lmpfr -lgmp'

This is more serious now as mpc cannot be turned off without manual hacking. I
am surprized this has not yet been confirmed. I can also now say that target
x86_64-linux-unknown-gnu produces the same problem. It is safe to say it is
fairly target indescriminate.


-- 

xenofears at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|using --with-cloog and --   |--without-mpc, --without-
                   |with-ppl without specifying |ppl, --without-cloog does
                   |a location with = causes    |the same thing. No turning
                   |configuration errors        |off mpc via configure.


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40516

[Bug bootstrap/40516] --without-mpc, --without-ppl, --without-cloog does the same thing. No turning off mpc via configure.

[xenofears at gmail dot com]

------- Comment #4 from xenofears at gmail dot com  2009-07-22 04:57 -------
How come this is still sitting unconfirmed? This is something that involves
Linux et. al. Using --without-cloog, ppl, or mpc doesn't work right as per
previous post, so it is more than just cosmetic. 

I don't really care personally, just trying to help gcc.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40516

[Bug bootstrap/40516] --without-mpc, --without-ppl, --without-cloog does the same thing. No turning off mpc via configure.

[manu at gcc dot gnu dot org]

------- Comment #5 from manu at gcc dot gnu dot org  2009-07-22 05:19 -------
(In reply to comment #4)
> How come this is still sitting unconfirmed? This is something that involves
> Linux et. al. Using --without-cloog, ppl, or mpc doesn't work right as per
> previous post, so it is more than just cosmetic. 

Presumably, because GCC devs haven't had time to look at this in detail and it
is not a priority compared to other issues. Note that at this moment there are
1288 unconfirmed bugs.

> I don't really care personally, just trying to help gcc.

Thanks, any help is greatly appreciated.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40516