Re: What might cause a difference in building using the ports system vs trying to build manually?

Yes

--
Sent from a phone, apologies for poor formatting.

On 12 December 2023 14:04:31 Matti Viljamaa <mavaviljggroup@gmail.com> wrote:
> It is part of the question in the sense that if the ports infrastructure is
> the "Tier 1" supported build system, then doing things manually serves no
> purpose on OpenBSD. So is the ports infrastructure the first in line build
> system?
>
> On Tue, Dec 12, 2023 at 3:55 PM Stuart Henderson <stu@spacehopper.org> wrote:
> Yes, you'd just need to figure out what's different about the commands and
> environment used to build it and apply that to a build outside of the ports
> framework. Maybe you'll get some clues from "make -n do-build" after "make
> configure". We're really just dealing with ports on this list though.
>
> --
> Sent from a phone, apologies for poor formatting.
>
>
> On 12 December 2023 13:03:36 Matti Viljamaa <mavaviljggroup@gmail.com> wrote:
>> Yes, the previous patch to use GCC does also build and passes the tests (it
>> also seems cleaner than the clang output which had some bits about
>> deprecated things or something).
>>
>> However, can the builds be replicated using manual commands instead of the
>> ports infrastructure?
>>
>> On Mon, Dec 11, 2023 at 10:57 PM Johannes Thyssen Tishman
>> <lists@thyssentishman.com> wrote:
>> 2023-12-11T12:33:51Z "Matti Viljamaa" <mavaviljggroup@gmail.com>:
>>> Yes, sounds reasonable. However, I was then originally misled, because the
>>> author of the working port claimed that it should work with GCC.
>>
>> I'm the author of the linked port and I'm able to compile and test
>> with gcc. Try the patch below, it should work as well. Why use
>> ports-gcc if you can use clang form base though?
>>
>> diff --git a/devel/pycxx/Makefile b/devel/pycxx/Makefile
>> index 6044762..dfdae55 100644
>> --- a/devel/pycxx/Makefile
>> +++ b/devel/pycxx/Makefile
>> @@ -18,6 +18,7 @@ MODPY_PYBUILD = setuptools
>> FLAVOR = python3
>> FLAVORS = python3
>>
>> +COMPILER = ports-gcc
>> TEST_DEPENDS = devel/gmake
>>
>> do-test:
>> diff --git a/devel/pycxx/patches/patch-setup_makefile_py
>> b/devel/pycxx/patches/patch-setup_makefile_py
>> index 177bd6c..5755793 100644
>> --- a/devel/pycxx/patches/patch-setup_makefile_py
>> +++ b/devel/pycxx/patches/patch-setup_makefile_py
>> @@ -7,8 +7,8 @@ Index: setup_makefile.py
>> CompilerGCC.__init__( self, setup )
>> - self._addVar( 'CCC', 'g++' )
>> - self._addVar( 'CC', 'gcc' )
>> -+ self._addVar( 'CCC', 'c++' )
>> -+ self._addVar( 'CC', 'cc' )
>> ++ self._addVar( 'CCC', 'eg++' )
>> ++ self._addVar( 'CC', 'egcc' )
>>
>> def setupPythonExtension( self ):
>> self._addVar( 'PYTHON', sys.executable )