1. I cannot access Dropbox from work, so cannot see the offending output.

2. I've no idea what the SVN version of crypto++ looks like. I stay with
v5.6.2, and it probably would be the best place to start if there are build
issues.

3. I would *not* mess with things like "stdlib=". You seem to have enough
trouble as is.

4. In my experience "-std=c++11" is *not* necessary. I've put it in only as
an attempt to get compatibility between GCC-built library and
Clang-compiled application (which failed, by the way).

5. While system-native (from Xcode) clang should work (I think I've built a
version with it successfully, but dropped it because it did not deal nicely
with AESNI instruction set, and was not very fast either), I'd recommend
using gcc48 or clang-3.4.

My gcc48 is the standard Macports gcc48 (4.8.2). My clang (both 3.3 and
3.4) are the standard Macports clang ports. I just "sudo port install
clang-3.4" and such. Without seeing the output, I'm very surprised you're
having problems...



On Thu, Jan 23, 2014 at 9:56 AM, Tim Burgess <[email protected]> wrote:

> I'm afraid I'm still not getting anywhere. Here's what I've tried:
>
> 1 - Uninstalled GCC4.8 using MacPorts;
>
>
>
> 2 - Uninstalled XCode;
>
>
>
> 3 - Repaired all disk permissions;
>
>
>
> 4 - Installed XCode 5.02 with all updates and command-line tools;
>
>
>
> 5 - .bash_profile:
>
>
>
> # Set clang to be the default compiler for c/c++
>
> export CXX=/usr/bin/clang++ ;
>
> export CC=/usr/bin/clang ;
>
> export CXXFLAGS=-std=c++11
>
>
>
> 6 - Downloaded latest Crypto++ from SVN;
>
>
>
> 7 -  - Build command:
>
>
>
> make -stdlib=libc++
>
>
> 8 - All .o files are 0 bytes, as is .a file;
>
>
>
>
>
> 9 - make clean
>
> 10 - Replaced gnumakefile with version from Mobile Mouse, but same result.
>
>
>
> Build output can be found at:
>
> https://dl.dropboxusercontent.com/u/29578720/Crypto.txt
>
>
>
> This style of output differs greatly from what I'd get when I don't
> specify the standard c++ library and doesn't appear to offer any really
> useful information about the build process - is there any way I can get
> more information about the errors that are obviously happening during my
> build attempts, please?
>
> Cheers.
>
> Tim
>
>
>  --
> --
> You received this message because you are subscribed to the "Crypto++
> Users" Google Group.
> To unsubscribe, send an email to
> [email protected].
> More information about Crypto++ and this group is available at
> http://www.cryptopp.com.
> ---
> You received this message because you are subscribed to the Google Groups
> "Crypto++ Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 
Regards,
Mouse

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to [email protected].
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to