The FreeType Project - Bugs: bug #28153, Hiding compiler warnings.
You are not allowed to post comments on this tracker with your current authentication level.
bug #28153: Hiding compiler warnings.
Submitter: | Dr. David Kirkby <drkirkby> | ||
Submitted: | Thu 03 Dec 2009 04:22:48 AM UTC | ||
Severity: | 3 - Normal | Item Group: | Hack required |
Status: | Invalid | Privacy: | Public |
Assigned to: | wl | Open/Closed: | Closed |
Planned Release: | None |
Thu 03 Dec 2009 05:03:39 AM UTC, comment #1: |
Werner LEMBERG <wl> |
Thu 03 Dec 2009 04:22:48 AM UTC, original submission:
I must admit to not having checked this in the latest release, but last time I looked, freetype was hiding compiler warnings by redirecting them to /dev/null.
|
Dr. David Kirkby <drkirkby> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
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.
Follow 4 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2009-12-03 | wl | Open/Closed | Open | Closed | |
Assigned to | None | wl | |||
Status | None | Invalid | |||
2009-12-03 | drkirkby | Carbon-Copy | - | Added -email is unavailable- |
Powered by Savane 3.13-02a9.
Corresponding source code
What you experience is a special feature of libtool,
the auxiliary package used to create the libraries. Since
libtool normally builds both a static library and a shared
version, it hides the compiler warnings during the second
call. Reason is that for the second call all compiler options
are exactly the same except the flags which make the compiler
create position independent code (PIC), and it rather confuses
the user if she sees all warnings twice.
I don't know whether this behaviour can be changed (honestly,
I can't see an immediate reason to do so); this would be a
question for the libtool people.