| 1 |
On 15/04/2022 17.43, Yuan Liao (Leo) wrote: |
| 2 |
> noting is, unlike compilation of a C/C++ program, where each compiler |
| 3 |
> […] a single invocation of |
| 4 |
> javac usually involves putting _all_ Java source files' names into the |
| 5 |
> command-line arguments. |
| 6 |
|
| 7 |
We do use javac's @argfiles, e.g., @sources.lst, some places (probably |
| 8 |
not in all). Otherwise, where @argfiles are not used, I think it is more |
| 9 |
likely that you run into an exec() argument length issue with a large |
| 10 |
source file count before the emerge output becomes an issue. |
| 11 |
|
| 12 |
That said, I am sympathetic to the concerns you raised. Ideally the |
| 13 |
build.log should include the full command while only a shortened version |
| 14 |
is printed to the console. However, I am not aware that this is possible |
| 15 |
with portage. And if it is not (yet) possible, then I lean towards |
| 16 |
capturing the whole command line. |
| 17 |
|
| 18 |
- Flow |
Archives