[Bug build/20463] Compile error when configure using --param arg=value in CFLAGS

["carlos at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=20463

Carlos O'Donell <carlos at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #6 from Carlos O'Donell <carlos at redhat dot com> ---
This is bug 17248. That glibc sorts CFLAGs breaking --param ordering.

The "alternate" format which is Andreas' suggestion is discussed in the getopt
man page.
~~~
       A long option normally begins with '--' followed  by  the  long  option
       name.   If  the  option  has  a  required  argument,  it may be written
       directly after the long option name, separated by '=', or as  the  next
       argument  (i.e.  separated  by whitespace on the command line).  If the
       option has an optional argument, it must be written directly after  the
       long  option name, separated by '=', if present (if you add the '=' but
       nothing behind it, it is interpreted as if  no  argument  was  present;
       this  is a slight bug, see the BUGS).  Long options may be abbreviated,
       as long as the abbreviation is not ambiguous.
~~~

One more alternative is to set CC or CXX with the parameters you need e.g.
export CC="gcc -Wl,--build-id=none --param l1-cache-line-size=32" which works
because CC isn't sorted.

*** This bug has been marked as a duplicate of bug 17248 ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.