On Sat, May 15, 2010 at 12:12 PM, Jim Michaels wrote:
> 1.
> I have noticed that for sezero and auto compilers, there averages
> 7-8 LONG directories for lib path totalling 284-328 characters
> 5 LONG directories for include path totalling 274-310 characters
> 1-2 directories for bin path.
>
> I s
gnu/java/security/jce/prng/natVMSecureRandom.cc: In static member
function 'static jint
gnu::java::security::jce::prng::VMSecureRandom::natGenerateSeed(JArray<__java_byte>*,
jint, jint)':
gnu/java/security/jce/prng/natVMSecureRandom.cc:29: error: expected
type-specifier
gnu/java/security/jce/prng/n
Hmmm I don't undertand the need for this.
The compiler is build with sysroot so the binaries find all the
related includes, libs etc magically. The paths are different such
that you can have multiple versions co-installed.
Right-click on my computer and adjust the path variable to include the
On 5/15/2010 12:12, Jim Michaels wrote:
> 1.
> I have noticed that for sezero and auto compilers, there averages
> 7-8 LONG directories for lib path totalling 284-328 characters
> 5 LONG directories for include path totalling 274-310 characters
> 1-2
> directories for bin path.
>
> I suggest at lea
On Sat, May 15, 2010 at 7:12 AM, Jim Michaels wrote:
> 1.
> I have noticed that for sezero and auto compilers, there averages
> 7-8 LONG directories for lib path totalling 284-328 characters
> 5 LONG directories for include path totalling 274-310 characters
> 1-2 directories for bin path.
>
> I su
I updated my custom w32/w64 native and cross-compiler build with gcc-4.4
with several backports and fixes from mainstream, and put them under the
mingw-w64 sf.net file release system under the subdirectories:
- Toolchain sources -> Personal Builds,
- Toolchains targetting Win32 -> Personal Builds
