Peter A. Castro writes:
> Ah. You are making the assumption I'm running my little project
> (Cygwin Time Machine) on Windows? No. This is run on a Linux server
> I use (heresy, I know :-), mostly using automated scripts and cron
> jobs.
I just wanted to avoid folks asking for those "new" versio
On Wed, 16 Apr 2014, Achim Gratz wrote:
Peter A. Castro writes:
I've just built a newer version of upx (and ucl, etc) and now I will start
archiving setup, x86 & x86_64, (again). Need to update my webpage
automation to generate an access list, but atleast I'm grabbing and
archiving them (again
Peter A. Castro fruitbat.org> writes:
> I've just built a newer version of upx (and ucl, etc) and now I will start
> archiving setup, x86 & x86_64, (again). Need to update my webpage
> automation to generate an access list, but atleast I'm grabbing and
> archiving them (again).
Not that I wan
On Mon, 7 Apr 2014, Larry Hall (Cygwin) wrote:
On 4/7/2014 9:50 PM, Christopher Faylor wrote:
On Mon, Apr 07, 2014 at 09:28:29PM -0400, Larry Hall (Cygwin) wrote:
2) Packaging changes of setup.exe have made extracting the version string
impossible, save for actually running setup, whi
Larry Hall (Cygwin cygwin.com> writes:
>
> On 4/7/2014 5:09 PM, Colin wrote:
>
>
>
> >> Indeed. And if your path under bash doesn't include /usr/bin, then
I'll
> >> wager your postinstall scripts didn't run or at least
> > completely/correctly.
> >> See /etc/postinstall for the scripts. If
On Mon, 7 Apr 2014, Christopher Faylor wrote:
Greetings, Chris,
On Mon, Apr 07, 2014 at 09:28:29PM -0400, Larry Hall (Cygwin) wrote:
On 4/7/2014 6:41 PM, Peter A. Castro wrote:
Geetings, Larry,
Some comments about this (sorry if this is off-tipic):
Since you're providing this Cygwin serv
On 4/7/2014 9:50 PM, Christopher Faylor wrote:
On Mon, Apr 07, 2014 at 09:28:29PM -0400, Larry Hall (Cygwin) wrote:
2) Packaging changes of setup.exe have made extracting the version string
impossible, save for actually running setup, which isn't something I'm
going to do on a dail
On Mon, Apr 07, 2014 at 09:28:29PM -0400, Larry Hall (Cygwin) wrote:
>On 4/7/2014 6:41 PM, Peter A. Castro wrote:
>
>
>> Geetings, Larry,
>>
>> Some comments about this (sorry if this is off-tipic):
>
>Since you're providing this Cygwin service, I don't consider information
>about this service to b
On 4/7/2014 6:41 PM, Peter A. Castro wrote:
Geetings, Larry,
Some comments about this (sorry if this is off-tipic):
Since you're providing this Cygwin service, I don't consider information
about this service to be off-topic. And, of course, if *I* don't consider
it off-topic, it certainly c
On Mon, Apr 07, 2014 at 06:12:56PM -0400, Larry Hall (Cygwin) wrote:
> On 4/7/2014 5:09 PM, Colin wrote:
>
>
>
> >>Indeed. And if your path under bash doesn't include /usr/bin, then I'll
> >>wager your postinstall scripts didn't run or at least
> >completely/correctly.
> >>See /etc/postinstall fo
On Mon, 7 Apr 2014, Larry Hall (Cygwin) wrote:
On 4/7/2014 5:09 PM, Colin wrote:
Indeed. And if your path under bash doesn't include /usr/bin, then I'll
wager your postinstall scripts didn't run or at least
completely/correctly.
See /etc/postinstall for the scripts. If you aren't able to
On 4/7/2014 5:09 PM, Colin wrote:
Indeed. And if your path under bash doesn't include /usr/bin, then I'll
wager your postinstall scripts didn't run or at least
completely/correctly.
See /etc/postinstall for the scripts. If you aren't able to figure out
what didn't run properly, you can eit
Larry Hall (Cygwin cygwin.com> writes:
>>>
> >>
> >> Cygwin 1.5.25 seems like a good option. So I downloaded setup-
legacy.exe
> >> from fruitbat and ran it on an XP machine which has not previously
seen
> >> Cygwin. Initially I installed just the base Cygwin files. The process
ran
> >> as exp
On 4/7/2014 7:23 AM, Corinna Vinschen wrote:
On Apr 7 11:08, Colin wrote:
Corinna Vinschen cygwin.com> writes:
On Apr 4 09:44, Colin wrote:
Corinna Vinschen cygwin.com> writes:
Alternatively, even though I hate to point people to older versions
of Cygwin, you could try the old Cygwin
On Apr 7 11:08, Colin wrote:
> Corinna Vinschen cygwin.com> writes:
>
> >
> > On Apr 4 09:44, Colin wrote:
> > > Corinna Vinschen cygwin.com> writes:
> > >
> >
> > Alternatively, even though I hate to point people to older versions
> > of Cygwin, you could try the old Cygwin 1.5.25. I'm no
Corinna Vinschen cygwin.com> writes:
>
> On Apr 4 09:44, Colin wrote:
> > Corinna Vinschen cygwin.com> writes:
> >
>
> Alternatively, even though I hate to point people to older versions
> of Cygwin, you could try the old Cygwin 1.5.25. I'm not quite sure,
> but I think it was compiled for
On Apr 4 09:44, Colin wrote:
> Corinna Vinschen cygwin.com> writes:
>
> > > In discussing this with the embedded PC supplier, he suggests that the
> > > cygwin1.dll is exiting because it doesn't recognise the CPU. Is this
> > > explanation plausible? And if it is, is there a solution available
Yaakov (Cygwin/X users.sourceforge.net> writes:
>
> Therefore, in order to even attempt to make this work, you would have to
> recompile gcc for -march=i586 default, then rebuild *everything* with
> that gcc; but I can't guarantee that there won't be other issues as well.
>
> Yaakov
>
> [1]
Corinna Vinschen cygwin.com> writes:
> > In discussing this with the embedded PC supplier, he suggests that the
> > cygwin1.dll is exiting because it doesn't recognise the CPU. Is this
> > explanation plausible? And if it is, is there a solution available, or
> > must I give up on using cygwin
On 2014-04-02 18:03, Colin wrote:
The problem I have can be reduced to this: I compile a simple "Hello
World" console mode c program. I copy the .exe file and cygwin1.dll onto
an embedded PC, open a console window, and run the program. The program
runs, and returns immediately to the command prom
On Apr 2 23:03, Colin wrote:
> Hi Team,
>
> I'm new here, but have dabbled in Cygwin for a few years. I hope someone
> more knowledgeable than myself can help with with this issue which is
> quite frankly baffling me for the past few weeks.
>
> The problem I have can be reduced to this: I comp
René Berber computer.org> writes:
>
> What you usually do on those cases:
>
> 1. On the build host, run ldd (or cygcheck) on the program, see the full
> list of dynamic libraries used.
>
> 2. Try to do the same on the target host. Yes, ldd does depend on
> cygwin1.dll, so it may not run.
On 4/2/2014 5:03 PM, Colin wrote:
> Hi Team,
Team? This is a user's forum.
[snip]
> The problem I have can be reduced to this: I compile a simple "Hello
> World" console mode c program. I copy the .exe file and cygwin1.dll onto
> an embedded PC, open a console window, and run the program. The
Hi Team,
I'm new here, but have dabbled in Cygwin for a few years. I hope someone
more knowledgeable than myself can help with with this issue which is
quite frankly baffling me for the past few weeks.
The problem I have can be reduced to this: I compile a simple "Hello
World" console mode c p
24 matches
Mail list logo
