Hi Ryan,
Ryan Schmidt wrote:
/usr/bin/gcc-4.2 -o pamtris pamtris.o boundaries.o framebuffer.o
input.o triangle.o utils.o -L/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_netpbm/netpbm/work/advanced-r3369/lib -lnetpbm
On Oct 9, 2018, at 03:54, Riccardo Mottola wrote:
> /usr/bin/gcc-4.2 -o pamtris pamtris.o boundaries.o framebuffer.o input.o
> triangle.o utils.o
>
On 2018-10-09, at 5:20 AM, Riccardo Mottola via macports-users wrote:
> Hi Chris,
>
>
> Chris Jones wrote:
>> The log snippet you post below is clearly showing neither of these two
>> compiler options is used. /usr/bin/gcc-4.2 is being used.
>>
>> Same comment as before. Please post trac
Hi Chris,
Chris Jones wrote:
The log snippet you post below is clearly showing neither of these two
compiler options is used. /usr/bin/gcc-4.2 is being used.
Same comment as before. Please post trac tickets at
https://trac.macports.org/
with *full* *clean* log files.
the log snipped is
On 09/10/18 09:54, Riccardo Mottola via macports-users wrote:
Hi!
with the latest update round, I have this new issue.
Any clues? Should I just try a different compiler? a dependency mssing?
I can open a ticket of course.
I tried configure.compiler=macports-gcc-6 but the issue persists
Hi!
with the latest update round, I have this new issue.
Any clues? Should I just try a different compiler? a dependency mssing?
I can open a ticket of course.
I tried configure.compiler=macports-gcc-6 but the issue persists
unchancged. I then tried macports-clang-3.9, but it doesn't help
