Re: [Duplicity-talk] Duplicity 1.0.1 Released

[Kenneth Loafman]

OK,

I could not remember what version of Python 3 you were running, so py3x meant for you to fill it in.  I'm guessing either py38 or py39 for Python 3.8 and Python 3.9 respectively.  Others follow the same model, py27,py35,...py310.

I am not sure why it's trying to build for anything but x86_64 if you have Intel silicone and not Apple silicone.

Here's what mine looks like for py38:

ken@dione:~/workspace/duplicity-origin$ python3.8 ./setup.py build_ext

Unable to get SCM version: defaulting to 1.0.1

running build_ext

Building extension for librsync...

building 'duplicity._librsync' extension

creating build/temp.macosx-12-x86_64-cpython-38

creating build/temp.macosx-12-x86_64-cpython-38/duplicity

clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk -I/usr/local/include -I/usr/local/opt/python@3.8/Frameworks/Python.framework/Versions/3.8/include/python3.8 -c duplicity/_librsyncmodule.c -o build/temp.macosx-12-x86_64-cpython-38/duplicity/_librsyncmodule.o

creating build/lib.macosx-12-x86_64-cpython-38

creating build/lib.macosx-12-x86_64-cpython-38/duplicity

clang -bundle -undefined dynamic_lookup -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk build/temp.macosx-12-x86_64-cpython-38/duplicity/_librsyncmodule.o -L/usr/local/lib -lrsync -o build/lib.macosx-12-x86_64-cpython-38/duplicity/_librsync.cpython-38-darwin.so

ld: warning: -undefined dynamic_lookup may not work with chained fixups

copying build/lib.macosx-12-x86_64-cpython-38/duplicity/_librsync.cpython-38-darwin.so -> duplicity

It looks like your xcode libs are out of date, and it also looks like you're not using the standard locations for software.  That's gonna complicate matters.

I'm on Monterey 12.6 with the current Xcode from Apple, all in standard places.

...Ken

On Thu, Oct 6, 2022 at 1:13 PM Scott Hannahs <sth@p-hall.net> wrote:

Ken,

I will leave fink out, but it should be doing exactly the same thing!  :-)

the following doesn’t even build duplicity correctly, so I don’t get to the tox command.

% tar xf duplicity-1.0.1.tar 

% cd duplicity-1.0.1 

% % C_INCLUDE_PATH=/opt/sw/include LIBRARY_PATH=/opt/sw/lib python3 ./setup.py build_ext > build.out.txt 2>&1

This gives the following output.

Unable to get SCM version: defaulting to 1.0.1

running build_ext

Building extension for librsync...

building 'duplicity._librsync' extension

clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders -iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers -arch arm64 -arch x86_64 -Werror=implicit-function-declaration -I/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/include/python3.9 -c duplicity/_librsyncmodule.c -o build/temp.macosx-10.9-universal2-3.9/duplicity/_librsyncmodule.o

clang -bundle -undefined dynamic_lookup -arch arm64 -arch x86_64 -Wl,-headerpad,0x1000 build/temp.macosx-10.9-universal2-3.9/duplicity/_librsyncmodule.o -lrsync -o build/lib.macosx-10.9-universal2-3.9/duplicity/_librsync.cpython-39-darwin.so

ld: warning: ignoring file /opt/sw/lib/librsync.dylib, building for macOS-arm64 but attempting to link with file built for macOS-x86_64

ld: warning: dylib (/opt/sw/lib/librsync.dylib) was built for newer macOS version (12.4) than being linked (10.9)

copying build/lib.macosx-10.9-universal2-3.9/duplicity/_librsync.cpython-39-darwin.so -> duplicity

I am building on an X86 machine and my libraries are x86 and I am not trying to build a universal arm 64 system.   But with warnings it tries to build.

tox does not like the py3x value

% tox -epy3 

py3 create: /Users/sth/Downloads/duplicity-1.0.1/.tox/py3

py3 installdeps: -rrequirements.txt

and I ran out of time this AM waiting for more output.

-Scott

On Oct 5, 2022, at 11:54 AM, Kenneth Loafman <kenneth@loafman.com> wrote:

Could you try just building and running the tests in a 'normal' user environment?  Leave Fink out of the picture.

do this:

1. $ tar xf duplicity-1.01.tar.gz
2. $ ./setup.py build_ext
3. $ tox -e py3x

...Thanks,

...Ken