bugGNUstep - Bugs: bug #34752, compiling with clang gives...

Group
 
 

bug #34752: compiling with clang gives warnings about unsupported options

Submitter:  julian <julian_>
Submitted:  Sat 05 Nov 2011 09:11:36 PM UTC
   
 
Category:  Makefiles Severity:  3 - Normal
Item Group:  Bug Status:  Ready For Test
Privacy:  Public Assigned to:  CaS
Open/Closed:  In Test
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Tue 27 May 2014 08:28:39 PM UTC, comment #7: 

Looks like Richard already added the patch by Jean-Charles two years ago. Could somebody using clang please test, whether this is fully resolved?

Fred Kiefer <FredKiefer>
Group Member
Tue 27 May 2014 12:29:31 PM UTC, comment #6: 

the fix referenced on GNUstep doesn't seem to be available (anymore) ?
Nicola, what's your take?

Riccardo Mottola <rmottola>
Group Member
Sun 10 Feb 2013 10:06:21 AM UTC, comment #5: 

I have a fix for this bug: see <https://github.com/gnustep/gnustep-make/pull/1>

Jean-Charles BERTIN <jcbertin>
Tue 08 Nov 2011 09:05:34 AM UTC, comment #4: 

Changed the category to Makefiles to attract Nicola's attention.

Fred Kiefer <FredKiefer>
Group Member
Sun 06 Nov 2011 11:32:47 AM UTC, comment #3: 

adding -Qunused-arguments to the cflags solves the problem for me for the time being.

julian <julian_>
Sun 06 Nov 2011 11:19:38 AM UTC, comment #2: 

where do you have that from? i think they never said they would support all gcc options

. The Clang driver and language features are intentionally designed to be as compatible with the GNU GCC compiler as reasonably possible ...


as far as i know support for fexec-charset isn't planned by them.

the shared-libgcc warning isn't as annoying because it happens once at link time while the exec-charset happens for every compiled file.

julian <julian_>
Sun 06 Nov 2011 10:10:17 AM UTC, comment #1: 

This is a clang bug (clang is officially supposed to handle all gcc options) ... so should presumably be reported to the clang developers.

Richard Frith-Macdonald <CaS>
Group Member
Sat 05 Nov 2011 09:11:36 PM UTC, original submission:  

compiling gnustep or a gnustep-using project with clang gives the following warnings:

for every compiled file there is a warning that "-fexec-charset=UTF-8" is not supported

for every link there is a warning that "-shared-libgcc" is not supported


the warning about fexec-charset is quite new.


these options should probably be disabled on clang, since real warnings drown in these  messages.

i'd propose a patch but i don't know how to determine if clang is used from within base.make.in (for -fexec-charset=UTF-8) and common.make (for -shared-libgcc)

julian <julian_>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by rmottola (Posted a comment)
  • -email is unavailable- added by jcbertin (Posted a comment)
  • -email is unavailable- added by FredKiefer (Posted a comment)
  • -email is unavailable- added by CaS (Posted a comment)
  • -email is unavailable- added by julian_ (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2014-05-27 FredKiefer StatusNone Ready For Test
        Assigned toNone CaS
        Open/ClosedOpen In Test
    2011-11-08 FredKiefer CategoryBase/Foundation Makefiles

    Back to the top

    Powered by Savane 3.13-d3ae.
    Corresponding source code