rsync friendly file encryption Activity
Brought to you by:
thesun
Activity for rsync friendly file encryption
-
Ryan Carsten Schmidt posted a comment on ticket #22
Well I'm not going to subscribe to a mailing list just to report this problem to you again somewhere else. :)
-
That'll work, thank you.
-
Shachar Shemesh posted a comment on ticket #21
I am going to solve bug #19 by removing precompiled headers altogether. As such, reopening this ticket is moot.
-
That is the wrong question. The right question is do you know for sure that all compilers support that command line? As for your other question: both clang of versions 6 and up (possibly earlier) and g++ of versions 6 and up (again, possibly earlier) do not need any special compilation flags to support C++11 features (specifically, unique_ptr). That flags was a transition period requirement. The only reason rsyncrypto was written to make it sound like it was optional was because, when written, std::map...
-
Homepage doesn't mention version 1.14
-
This is not a bug in the software. The mailing list is the place for this type of discussions.
-
Homepage doesn't mention version 1.14
-
I think at least one problem with the code in your configure.ac is that test "! -e a.out -a -f conftest.h.gch" does nothing useful. It's just testing a string. It'll give the same result as testing any other string, such as test "hello world". You probably meant to write it without the quotes: test ! -e a.out -a -f conftest.h.gch But that still doesn't fully fix the problem. One way to improve the situation is to use $CXXFLAGS when doing the conftest: if $CXX $CXXFLAGS -c conftest.h That way, when...
-
I tried building on a much older system running Mac OS X 10.4 and using the MacPorts version of Apple gcc 4.2.1. When not using -std=c++11 it failed with: /opt/local/bin/g++-apple-4.2 -DHAVE_CONFIG_H -I. -I/opt/local/include -pipe -Os -arch i386 -MT main.o -MD -MP -MF .deps/main.Tpo -c -o main.o main.cpp In file included from main.cpp:32: rsyncrypto.h:97: error: expected initializer before '<' token In file included from crypto.h:34, from main.cpp:34: crypt_key.h:54: error: ISO C++ forbids declaration...
-
I think this issue may end up being solved once #21 is solved.
-
I am building in a clean directory. I build tons of software with --disable-dependency-tracking and rsyncrypto 1.14 is the only one that fails this way. (Even rsyncrypto 1.12 didn't fail this way.) I think it is caused by this code in your Makefile.am: # If the compiler supports precompiled headers the GNU way, we need to add a few rules here if PRECOMPILED_HEADERS # Generate precompiled headers precomp.h.gch: precomp.h $(CXXCOMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.h.Tpo -c -o $@.comp $< mv -f $(DEPDIR)/$*.h.Tpo...
-
I think I better understand the problem you are describing. You are saying that rsyncrypto's use of precompiled headers conflicts with clang's multiarch support. Is that correct?
-
Build fails when dependency tracking is disabled
-
This problem did not reproduce on my system. Please make sure that you are building from a clean directory (run make distclean). If the problem persists, please report it as a bug on automake, as rsyncrypto uses that to track dependencies.
-
Do you know which compilers don't require -std=c++11 to compile this?
-
Adding that flag automatically is not as simple as it sounds. Not all compilers require it, and it is not guaranteed that all compiler will even know how to parse std=c++11. As such, having the user add it if needed is the only option that makes sense. With that said, it might be a good idea to add a test to configure to make sure the compiler support C++11 features, to make the failure clearer.
-
It seems from the error message that you are trying to build with compile flags that are not supported by clang. I fail to see how I can fix this issue.
-
Build fails when dependency tracking is disabled
-
Build fails unless using -std=c++11
-
cannot use 'precompiled-header' output with multiple -arch options
-
Fix infinite recursion on delete
-
rsync friendly file encryption released /rsyncrypto/1.14/rsyncrypto-1.14.tar.bz2.asc
-
-
Re-tag v1.14
-
V1.14 incorrectly released
-
Update version information
-
Spelling mistake
-
Shlomi Fish posted a comment on ticket #16
On Sun, 03 Sep 2017 18:35:13 +0000 "Shachar Shemesh" thesun@users.sf.net wrote: status: open --> closed-fixed Thanks for fixing it. [bugs:#16] Typo in README - "nees" instead of "needs" Status: closed-fixed Group: v1.14 Created: Tue Dec 20, 2011 07:43 PM UTC by Shlomi Fish Last Updated: Sun Sep 03, 2017 06:28 PM UTC Owner: Shachar Shemesh Hi, thanks for rsyncrypto! There's a small typo in the README - "nees" which should be "needs". I'm attaching a patch that fixes it, but it's not that necessary....
-
Version 1.14 of rsyncrypto has been released
-
-
-
Hard links support
-
Typo in README - "nees" instead of "needs"
-
Tag version 1.14
-
Mark version 1.14
-
orphaned files after interrupt with --name-encrypt
-
Sorry about the long time it took to look at your report. Option 2 seems the more likely, at this point. Another option is an external tool. Will have to think about it.
-
Typo in README - "nees" instead of "needs"
-
Typo in README (closes bug #16)
-
Fix --filelist with --trim
-
Fix spelling mistake
-
-
Version 1.13 has been released
-
Version 1.13 has been released
-
-
Tag release V1.13
-
Mark version 1.13
-
Proper transition to unique_ptr
-
Adapt to openssl 1.1.0
-
Missed (a few) spots
-
Auto_ptr => unique_ptr throughout
-
-1 to pointer casting problems on 64 bit
-
-
-
-
-
-
1
