-
Notifications
You must be signed in to change notification settings - Fork 9
/
NEWS
155 lines (120 loc) · 5.33 KB
/
NEWS
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
portage-bashrc-mv-23.0
----------------------
- Support flag parameters to have parameters by extending FLAG_ARGS_WITH_PARAMS
interpretation and apply it for '-Xclang -mllvm'
https://github.com/vaeth/portage-bashrc-mv/issues/40
portage-bashrc-mv-22.2
----------------------
- Update more flags supported by GNU/NON_GNU. Thanks to blackteahamburger. See
https://github.com/vaeth/portage-bashrc-mv/pull/38
portage-bashrc-mv-22.1
----------------------
- Update some flags supported by GNU/NON_GNU. Thanks to Seryoga Leshii. See
https://github.com/vaeth/portage-bashrc-mv/issues/37
portage-bashrc-mv-22.0
----------------------
- Add support for RUSTFLAGS, particularly quote -C to subsequent parameter, see
https://github.com/vaeth/portage-bashrc-mv/issues/33
- Document rules for implicit quoting to subsequent parameter
- Do not implicitly quote for other VAR to subsequent parameter except
CFLAGS, CXXFLAGS, LDFLAGS
- Do not filter some flags supported by current clang, see
https://github.com/vaeth/portage-bashrc-mv/issues/34
portage-bashrc-mv-21.1
----------------------
- Enlarge the explicit list; thanks to Steven Newbury
https://github.com/sjnewbury for the contribution.
portage-bashrc-mv-21.0
----------------------
- Attempt to handle arguments with parameters using an explicit list, see
https://github.com/vaeth/portage-bashrc-mv/issues/10
portage-bashrc-mv-20.7
----------------------
- Filter -flto-odr-type-merging with USE_NONGNU=1
portage-bashrc-mv-20.6
----------------------
- Alessandro-Barbieri: Filter warnings not available in clang
portage-bashrc-mv-20.5
----------------------
- Jannik2099: filter LTO-requiring flags if LTO is not enabled on clang
- jiblime: Set USE_NONGNU=1 by default with active USE flag clang
portage-bashrc-mv-20.4
----------------------
- enable -fstack-clash-protection on clang
portage-bashrc-mv-20.3
----------------------
- Even more non-GNU
portage-bashrc-mv-20.2
----------------------
- More non-GNU
portage-bashrc-mv-20.1
----------------------
- SPDX-License-Identifier
portage-bashrc-mv-20.0
----------------------
- Backward-incompatible change:
/-foo/-bar will not add -bar if -foo cannot be found.
The previous behaviour can be achieved by /-foo/-bar -bar.
As a side-effect, do not unconditionally add -fstack-check for non-GNU.
- Output C++ and LD version.
portage-bashrc-mv-19.0
----------------------
Support F*FLAGS, and let *FLAGS= and *FLAGS+= include F*FLAGS.
You can use C*FLAGS=... LDFLAGS= OPTLDFLAGS= or C*FLAGS+=, respectively,
if you do not like the latter two.
portage-bashrc-mv-18.1
----------------------
Support QLOP_COUNT (default 3). Thanks to guitoo for the suggestion,
see https://github.com/vaeth/portage-bashrc-mv/issues/18
Also evaluate NOQLOP according to the usual true/false logic.
portage-bashrc-mv-18.0
----------------------
It is now possible to set NOQLOP to skip the qlop feature (e.g. for
comptability problems with old qlop versions). In addition, the FLAG feature
is now the first file parsed so that it /etc/portage/package.cflags can be
used to set this variable.
The AUTHORS file now finally contains the contributor to 17.3:
Sorry, I had changed it immediately but had forgotten to commit.
portage-bashrc-mv-17.0
----------------------
No longer work with <app-portage/portage-utils-0.74-r1, but support instead
>=app-portage/portage-utils-0.80_pre20190605.
portage-bashrc-mv-16.0
----------------------
New localepurge configuration; ignore that of app-admin/localepurge
portage-bashrc-mv-15.0
----------------------
Support MESONDEDUP:
>=meson-0.47 had the insane idea to forbid the user to specify flags
simultaneously in e.g. LDFLAGS and CFLAGS.
Although the same flags must necessarily be specified in some cases during
compile and link phase, meson insists to have the sole decision about this,
thus breaking with *FLAGS meant to be used also for other build systems.
As a workaround, portage-bashrc-mv now supports a variable MESONDEDUP:
If this variable is true then all flags from LDFLAGS which can occur
already in some other compile phase are removed.
portage-bashrc-mv-14.4
----------------------
unless CCACHE_HASHDIR is set to true, CCACHE_NOHASHDIR is now set.
This effectively means that the ccache default of that variable is inverted.
This should increase the number of ccache hits in average although in some
cases it might cause issues: Try setting CCACHE_HASHDIR=1 in case of
miscompilations with ccache.
portage-bashrc-mv-14.0
----------------------
Improve support/customization for filtering *FLAGS depending on the compiler.
portage-bashrc-mv-13.0
----------------------
Important!
If you use >=portage-2.2.15 and have previously used <portage-bashrc-mv-13
you will get problems, because <portage-bashrc-mv-13 modified EBUILD_PHASE
which has been declared readonly in >=portage-2.2.15, and thus modification
leads to an error abort of portage.
In this case you have to run once
fix-portage-2.2.15 [if you use prefix-portage, use your $EPREFIX as argument]
This command will fix the environment.bz2 files in ${1%/}/var/db/pkg
which were generated with <portage-bashrc-mv-13 and which are
incompatible with the mentioned change in portage-2.2.15
(Unfortunately, it is not possible to fix this in portage-bashrc-mv alone,
since environment.bz2 is used for unmerging, overriding portage-bashrc-mv.)
Execute fix-portage-2.2.15 as the first command after upgrading portage-2.2.15!