On 07/03/18 14:15, Arnaud Charlet wrote:
The $(GNATLIBCFLAGS) are already included in $(GNATLIBCFLAGS_FOR_C).
We must call the C compiler with the right machine flags. So, add
$(GNATLIBCFLAGS_FOR_C) to $(OSCONS_EXTRACT). For example, on a
bi-arch
compiler supporting 32-bit and 64-bit instructi
> >>The $(GNATLIBCFLAGS) are already included in $(GNATLIBCFLAGS_FOR_C).
> >>
> >>We must call the C compiler with the right machine flags. So, add
> >>$(GNATLIBCFLAGS_FOR_C) to $(OSCONS_EXTRACT). For example, on a
> >>bi-arch
> >>compiler supporting 32-bit and 64-bit instruction sets we pick
> >
On 07/03/18 11:33, Arnaud Charlet wrote:
The $(GNATLIBCFLAGS) are already included in $(GNATLIBCFLAGS_FOR_C).
We must call the C compiler with the right machine flags. So, add
$(GNATLIBCFLAGS_FOR_C) to $(OSCONS_EXTRACT). For example, on a bi-arch
compiler supporting 32-bit and 64-bit instructi
> The $(GNATLIBCFLAGS) are already included in $(GNATLIBCFLAGS_FOR_C).
>
> We must call the C compiler with the right machine flags. So, add
> $(GNATLIBCFLAGS_FOR_C) to $(OSCONS_EXTRACT). For example, on a bi-arch
> compiler supporting 32-bit and 64-bit instruction sets we pick otherwise
> only
The $(GNATLIBCFLAGS) are already included in $(GNATLIBCFLAGS_FOR_C).
We must call the C compiler with the right machine flags. So, add
$(GNATLIBCFLAGS_FOR_C) to $(OSCONS_EXTRACT). For example, on a bi-arch
compiler supporting 32-bit and 64-bit instruction sets we pick otherwise
only one variant