On Tue, Nov 8, 2011 at 5:26 PM, JonY wrote:
> Other win64 exec packers are mentioned at the UPX forum
> https://sourceforge.net/projects/upx/forums/forum/6805/topic/1803140
PESpin x64 is a good program, but it does not offer LZMA compression.
--
On 11/9/2011 07:12, Steven Penny wrote:
> On Tue, Nov 8, 2011 at 4:57 PM, JonY wrote:
>> So, you were planning to compress 64-bit executables without TLS using
>> UPX, but it doesn't support it anyway.
>>
>> If you are using UPX on 32-bit executables they work.
>>
>> I guess you don't really want U
On Tue, Nov 8, 2011 at 4:57 PM, JonY wrote:
> So, you were planning to compress 64-bit executables without TLS using
> UPX, but it doesn't support it anyway.
>
> If you are using UPX on 32-bit executables they work.
>
> I guess you don't really want UPX.
Did you have any new information, or did yo
On 11/9/2011 02:48, Steven Penny wrote:
> On Tue, Nov 8, 2011 at 12:40 PM, Chris Sutcliffe wrote:
>> UPX supported TLS callbacks as of 3.06.
>
> UPX does not support Windows 64-bit executables.
>
So, you were planning to compress 64-bit executables without TLS using
UPX, but it doesn't support i
On Tue, Nov 8, 2011 at 12:40 PM, Chris Sutcliffe wrote:
> UPX supported TLS callbacks as of 3.06.
UPX does not support Windows 64-bit executables.
--
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net
On 8 November 2011 13:14, Kai Tietz wrote:
> 2011/11/8 Steven Penny:
>> Is there a way to buld with mingw-w64 without using TLS callbacks?
>> I would like to compress my executables with UPX, MPRESS, etc but
>> these do not support TLS callbacks?
>>
>> Alternatively if you know a program with will
On Tue, Nov 8, 2011 at 12:14 PM, Kai Tietz wrote:
> you can modify linker-spec file here to put TLS-block into different
> section. .data should be fine.
Does that mean using objcopy? Here is example
http://www.cygwin.com/ml/cygwin-apps/2010-03/msg00076.html
If there is a better way let me know
2011/11/8 Steven Penny :
> Is there a way to buld with mingw-w64 without using TLS callbacks?
> I would like to compress my executables with UPX, MPRESS, etc but
> these do not support TLS callbacks?
>
> Alternatively if you know a program with will compress win64 binaries
> with TLS callback suppo
Is there a way to buld with mingw-w64 without using TLS callbacks?
I would like to compress my executables with UPX, MPRESS, etc but
these do not support TLS callbacks?
Alternatively if you know a program with will compress win64 binaries
with TLS callback support that would work as well.
---
Thanks for the prompt help. I can confirm that today's snapshot of
binutils, labelled release 2.22.51 now compiles for me fine with
configure \
--prefix=$(TOP_PREFIX) \
--build=$(BUILDHOST) \
--target=$(BUILDHOST) \
--disable-multilib \
--disable-
On Tue, Nov 8, 2011 at 12:02 PM, Mark Dootson wrote:
> On 08/11/2011 09:26, Ozkan Sezer wrote:
>
>> That patch has not been reverted from v2.x, it is there.
>> If you reverted it on your own copies, we'd like to know
>> what problems it caused for you.
>
> My confusion. I am working with the 'stab
On Tue, Nov 8, 2011 at 11:02 AM, Mark Dootson wrote:
> I assume binutils just hasn't caught up with availability of LFS in
> mingw-w64.
I submitted a patch to binutils, which was applied to CVS HEAD a few
weeks ago, as JonY said.
mingw-w64 trunk + binutils HEAD build fine for me.
--
Pau Garci
On 08/11/2011 09:26, Ozkan Sezer wrote:
> That patch has not been reverted from v2.x, it is there.
> If you reverted it on your own copies, we'd like to know
> what problems it caused for you.
My confusion. I am working with the 'stable' branch - i.e.
http://mingw-w64.svn.sourceforge.net/viewvc/
On 11/8/2011 17:26, Ozkan Sezer wrote:
> On Tue, Nov 8, 2011 at 10:39 AM, Mark Dootson wrote:
>> Hi,
>>
>> I have been trying to compile binutils natively using
>> mingw-w64-stable-2.x-r4587. Original release 2.0 worked OK. After much
>> hair pulling, I realised the answer was the binutils code do
On Tue, Nov 8, 2011 at 10:39 AM, Mark Dootson wrote:
> Hi,
>
> I have been trying to compile binutils natively using
> mingw-w64-stable-2.x-r4587. Original release 2.0 worked OK. After much
> hair pulling, I realised the answer was the binutils code doesn't yet
> cope with availability of _FILE_OF
Hi,
I have been trying to compile binutils natively using
mingw-w64-stable-2.x-r4587. Original release 2.0 worked OK. After much
hair pulling, I realised the answer was the binutils code doesn't yet
cope with availability of _FILE_OFFEST_BITS on mingw so I just pass
--disable-largefile to conf
16 matches
Mail list logo
