On Friday September 20 2019 18:27:49 Ryan Schmidt wrote:
>It would seem that making `port clean` delete the ccache caches would defeat
>all current use cases of it.
Not necessarily. AFAIK build commands under MacPorts almost always use full
paths to source files because of the way configure
On Sep 20, 2019, at 02:23, René J.V. Bertin wrote:
>> Storing a separate cache for each port would quickly eat up a lot of disk
>> space.
>
> Evidently, but
> - ccache doesn't use more space than needed
> - the ccache directory compresses extremely well with afsctool, a background
> cleanup
On Thursday September 19 2019 20:20:06 Ryan Schmidt wrote:
>
> You could increase the size of your cache.
>
>Storing a separate cache for each port would quickly eat up a lot of disk
>space.
Evidently, but
- ccache doesn't use more space than needed
- the ccache directory compresses extremely
On Sep 17, 2019, at 03:26, René J.V. Bertin wrote:
> On Monday September 16 2019 16:26:12 Ryan Schmidt wrote:
>
>> There should be no need for you to specify anything ccache-related on the
>> command line. You can enable ccache globally in macports.conf. Individual
>> ports can disable it
On Sep 17, 2019, at 03:08, René J.V. Bertin wrote:
> I continue to think that compiler choice and options should be something the
> user can set the default for, without having to replace the standard system
> compiler drivers (/usr/bin/clang{,++}) with wrapper scripts.
As you know, we
-Wl,-no_pie
Is the linker option you were looking for.
K
On Monday September 16 2019 16:26:12 Ryan Schmidt wrote:
>There should be no need for you to specify anything ccache-related on the
>command line. You can enable ccache globally in macports.conf. Individual
>ports can disable it if they are not compatible with it.
Yes, I realised that after
On Tuesday September 17 2019 11:49:11 Joshua Root wrote:
I continue to think that compiler choice and options should be something the
user can set the default for, without having to replace the standard system
compiler drivers (/usr/bin/clang{,++}) with wrapper scripts.
>machine. But
On 2019-9-17 07:26 , Ryan Schmidt wrote:
>> I cannot agree completely with that. What if you want to build all your
>> ports with maximum optimisation (including -march=native and
>> -mdynamic-no-pic)?
>
> There is no feature in MacPorts for that. Individual ports can offer a
> variant to do
I don't want to discuss this at great length, but I'll answer these questions:
On Sep 16, 2019, at 02:22, René J.V. Bertin wrote:
> On Sunday September 15 2019 20:25:59 Ryan Schmidt wrote:
>
>> Setting such options on the command line is intended as a debugging
>> technique only.
>
> I
On Sunday September 15 2019 20:25:59 Ryan Schmidt wrote:
>Setting such options on the command line is intended as a debugging technique
>only.
I cannot agree completely with that. What if you want to build all your ports
with maximum optimisation (including -march=native and
On Sep 12, 2019, at 03:46, René J.V. Bertin wrote:
> I hope I didn't ask this before:
>
> Is there a way to let command line options like the ones in the subject apply
> to all ports on the command line, instead of only to the one given just
> before of the option in question?
I would
Hi,
I hope I didn't ask this before:
Is there a way to let command line options like the ones in the subject apply
to all ports on the command line, instead of only to the one given just before
of the option in question?
Thanks,
R.
13 matches
Mail list logo
