Help with New Port - M2VDownsizer
ryandesign at macports.org
Sat Aug 6 00:35:21 UTC 2022
On Aug 5, 2022, at 18:14, Robert Kennedy wrote:
> I have been playing around with CFLAGS += -Xarch_ppc -faltivec in my Makefile, as suggested by Josh.
> I noticed that if I include CFLAGS += -Xarch_ppc -faltivec in my Makefile, the output from the clang compiler gets garbled but the M2VDownsizerbinary appears to build fine.
> /opt/local/var/macports/build/_Users_grinch_Macports_ports_multimedia_M2VDownsizer/M2VDownsizer/work/compwrap/cc/usr/bin/clang -Os -arch x86_64 -Wall -g -Xarch_ppc -faltivec -Xarch_ppc64 -faltivec -I./ -Iutils -Iutils/altivec -Impeg2dec -Impeg2enc -I/System/Library/Frameworks/CoreServices.framework/Headers -c utils/mpegconsts.c -o obj/utils/mpegconsts.o
> clang: clang: clang: clang: warning: warning: warning: warning: argument unusedargument unusargument dured dur unused dinig ng compilation:uring '- coacompilXarchatmpilio_ppatiornn: gu:c -m''--faXXarletntciav rhch_ec_ppu'n
> usppc clang: warning: ar-faltedc guiv d-fmeecuralnt'
> ing compilatclang: warning: ioti uarn: '-Xarch_ppc -faltivec'
> clang: warning: argument unused during compilation: '-Xarch_ppc6nguvs4 uemece'
> d-faltivclang: nt decu'
> unriwarning: argument unused during compilation: '-Xarch_ppc64 -faltivec'
> ng compilation: '-Xarch_ppc64 -faltivec'
> used during compilation: '-Xarch_ppc64 -faltivec'
> I can avoid this garbled output if I turn off parallel builds by including the following in the Portfile:
> use_parallel_build no
> What is recommended in these circumstances considering that the garbled output does not appear to affect building the final binary? Should I turn off parallel builds in the Portfile?
No, you should leave parallel building on because it speeds up builds on multiprocessor machines. If bugs are reported against a port and the error messages in the log are too garbled to decipher due to parallel building, ask the user to rerun the build with parallel building disabled.
More information about the macports-dev