On 5/14/19 2:15 PM, Osipov, Michael wrote:
>> configure:68559: checking whether this system supports stdbuf
>> configure:68586: /opt/aCC/bin/aCC -AC99 -o conftest +z -g
>> -I/opt/ports/coreutils/include -D_INCLUDE_STDC__SOURCE_199901 -b
>> -L/opt/ports/coreutils/lib/hpux32 conftest.c >&5
>>
On 5/15/19 2:30 AM, Osipov, Michael wrote:
>
> I don't know how to solve this differently for now, but to disable
> include_next in configure.ac if the compiler is aCC.
Better yet, let's stop using the -include option as it's not portable.
The -include option was used only to attempt to keep
let's examine #include_next first:
Am 2019-05-14 um 18:26 schrieb Paul Eggert:
On 5/14/19 6:52 AM, Osipov, Michael wrote:
aCC does not exit with non-zero, it just prints a warning.
OK, I installed the attached patch to try to fix this problem with
'configure'. Please give it a try. We may
getacl, aclsort:
Am 2019-05-14 um 18:26 schrieb Paul Eggert:
On 5/14/19 6:52 AM, Osipov, Michael wrote:
aCC does not exit with non-zero, it just prints a warning.
OK, I installed the attached patch to try to fix this problem with
'configure'. Please give it a try. We may need some more
sys/bitypes.h:
Am 2019-05-14 um 18:26 schrieb Paul Eggert:
On 5/14/19 6:52 AM, Osipov, Michael wrote:
aCC does not exit with non-zero, it just prints a warning.
OK, I installed the attached patch to try to fix this problem with
'configure'. Please give it a try. We may need some more
On (info "(coreutils) cut invocation")
with no examples for
‘-f FIELD-LIST’
‘--fields=FIELD-LIST’
Select for printing only the fields listed in FIELD-LIST. Fields
are separated by a TAB character by default. Also print any line
that contains no delimiter
Oh, I see, it is mentioned above it.
Sure wish "(see above)" was there.
merge 35747 35748
tag 35748 notabug
thanks
On 5/15/19 8:38 AM, 積丹尼 Dan Jacobson wrote:
> Oh, I see, it is mentioned above it.
> Sure wish "(see above)" was there.
No need to open a second bug to tell us that the first was not a problem
after all. I'm merging the two bugs in the database, and
> "EB" == Eric Blake writes:
EB> No need to open a second bug to tell us that the first was not a problem
EB> after all. I'm merging the two bugs in the database, and marking the
EB> issue closed.
It takes several minutes before the bug number is created, so there is a
tradeoff between
