I can't imagine any one actually working in the real world even caring about
any of this. I joined this mailing list a couple of days ago. I thought it
would be interesting ... but this ... it's just painful.
On 4 Apr 2013, at 10:45 PM, Christopher Faylor wrote:
> On Fri, Apr 05, 2013 at 0
On Fri, Apr 05, 2013 at 02:37:11PM +0900, wynfi...@gmail.com wrote:
>Christopher Faylor wrote:
>> On Thu, Apr 04, 2013 at 02:59:01PM -0400, Eliot Moss wrote:
>> >On 4/4/2013 2:40 PM, Eliot Moss wrote:
>> snipped
>> If you have to enter MinGW land to perform what the OP wants then that
>> is a r
Comments inlined.
Christopher Faylor wrote:
> On Thu, Apr 04, 2013 at 02:59:01PM -0400, Eliot Moss wrote:
> >On 4/4/2013 2:40 PM, Eliot Moss wrote:
> snipped
> If you have to enter MinGW land to perform what the OP wants then that
> is a really clear indication that this is off-topic.
That i
Christopher Faylor wrote:
> On Thu, Apr 04, 2013 at 02:59:01PM -0400, Eliot Moss wrote:
> >On 4/4/2013 2:40 PM, Eliot Moss wrote:
> snipped
> If you have to enter MinGW land to perform what the OP wants then that
> is a really clear indication that this is off-topic.
That is illogical, just b
Another great idea. I'll give it go. Thank you.
Eliot Moss wrote:
> It sounds as if what you need to know is the calling
> convention for gcc on the x86. Maybe the easiest
> thing is simply to write and compile some C programs
> and then use gdb to disassemble them (or request
> assembly code o
Comments below:
Christopher Faylor wrote:
> If you're asking how to call cygwin entry points to use Cygwin I/O from
> an assembly language program then you are on-topic for the mailing list.
That's exactly what I asked.
> It is possible to write a raw assembly language program which does this
>
Greetings, Corinna Vinschen!
>> > It shows this error message:
>> > winln: you don't permission to create symbolic links. Run, as
>> > administrator,
>> > winln: editrights -a SeCreateSymbolicLinkPrivilege -a $YOUR_USER
>> > which should be fixed somehow like this:
>> > You don't have permission
On 4/4/2013 5:05 PM, Christopher Faylor wrote:
On Thu, Apr 04, 2013 at 02:59:01PM -0400, Eliot Moss wrote:
If you have to enter MinGW land to perform what the OP wants then that
is a really clear indication that this is off-topic.
Agreed ... we have now directed him to at least two useful
pl
On Thu, Apr 04, 2013 at 02:59:01PM -0400, Eliot Moss wrote:
>On 4/4/2013 2:40 PM, Eliot Moss wrote:
>>It occurred to me to mention to the OP that the mingw package (minimal
>>Gnu for Windows is what I think it stands for) is a lighter weight
>>version of the gcc stuff for Windows. It does not try
On 4/4/2013 2:40 PM, Eliot Moss wrote:
It occurred to me to mention to the OP that the
mingw package (minimal Gnu for Windows is what I think
it stands for) is a lighter weight version of the gcc
stuff for Windows. It does not try to "fake" a Linux
environment to the extent that cygwin does, so
It occurred to me to mention to the OP that the
mingw package (minimal Gnu for Windows is what I think
it stands for) is a lighter weight version of the gcc
stuff for Windows. It does not try to "fake" a Linux
environment to the extent that cygwin does, so it is
simpler and smaller, as I understa
On Thu, 04 Apr 2013 17:46:12 +0200, Frank Farance
wrote:
[snip]
Now, for whatever reason, a different set of calculations are needed and
assembler is the best software engineering solution (for whatever
reason). As a programmer, I can think of several ways that will cause a
visual image
On Apr 4 12:23, Jeffrey Altman wrote:
> On 4/4/2013 11:48 AM, Thomas Wolff wrote:
> > It shows this error message:
> > winln: you don't permission to create symbolic links. Run, as
> > administrator,
> > winln: editrights -a SeCreateSymbolicLinkPrivilege -a $YOUR_USER
> > which should be fixed s
Am 04.04.2013 18:23, schrieb Jeffrey Altman:
On 4/4/2013 11:48 AM, Thomas Wolff wrote:
It shows this error message:
winln: you don't permission to create symbolic links. Run, as
administrator,
winln: editrights -a SeCreateSymbolicLinkPrivilege -a $YOUR_USER
which should be fixed somehow like t
On 4/4/2013 11:48 AM, Thomas Wolff wrote:
> It shows this error message:
> winln: you don't permission to create symbolic links. Run, as
> administrator,
> winln: editrights -a SeCreateSymbolicLinkPrivilege -a $YOUR_USER
> which should be fixed somehow like this:
> You don't have permission to cr
Am 03.04.2013 10:08, schrieb Daniel Colascione:
On 4/3/2013 1:01 AM, Thomas Wolff wrote:
Am 03.04.2013 09:15, schrieb Daniel Colascione:
In light of the recent discussion on the developers list about native symlinks,
I'd like to suggest including my winln program (which I posted a while ago on
On 2013-04-04 09:15, Earnie Boyd wrote:
On Thu, Apr 4, 2013 at 8:57 AM, Frank Farance wrote:
I haven't posted in a long while, but the question seems reasonable and
relevant to cygwin. If one were writing assembler code to be compatible
with cygwin, one would need the answer to the question or
A C program is going to want to pull in at least a C run-time
(crt0 is one common name for that link file). Consider this
minimal C program:
extern void exit(int);
void main (int argc, char **argv) {
exit(0);
}
It is 73 bytes as a .c file and 408 bytes in a .o.
It I link it, doing what gcc d
On Thu, Apr 04, 2013 at 11:04:29PM +0900, wynfield wrote:
>No Earnie. It wasn't about programming. Read and try to comprehend.
>cygwin seems to have a missing api in it or one it should have is
>missing. The cygwin.dll or possibly another cygwin dll shuffles i/o
>betwwen cygwin programs and MSWi
Hi
Finally new versions of 'uw-imap/uw-imap-imapd/uw-imap-util/c-client' have
been uploaded to a server near you.
o Update to latest upstream version
o Build for cygwin 1.7.17 with gcc-4.5.3 (first version for cygwin 1.7.x)
o Uses cygport-0.11.3 for .hint files generation
o debuginfo package
No Earnie. It wasn't about programming. Read and try to comprehend.
cygwin seems to have a missing api in it or one it should have is missing.
The cygwin.dll or possibly another cygwin dll shuffles i/o betwwen cygwin
programs and MSWindows is not open to linkage (or is it) by assembly language
On Thu, Apr 4, 2013 at 8:57 AM, Frank Farance wrote:
>
> I haven't posted in a long while, but the question seems reasonable and
> relevant to cygwin. If one were writing assembler code to be compatible
> with cygwin, one would need the answer to the question originally posed. I
> don't see this
On 2013-04-04 04:55, Corinna Vinschen wrote:
On Apr 4 17:05, wynfi...@gmail.com wrote:
It is a cygwin related question to me. It involves using cygwin and
programs built using cygwin. You are wrong to suggest that it doesn't
related to cygwin. Additionally it involves using cygwin as a
lear
On 04/04/2013 7:03 AM, wynfi...@gmail.com wrote:
I did not ask for native widows programming advice any more than cygwin uses
win32-api.
cygwin distributes the header files and I simply asked about linking, which is
exactly what cygwin built programs do.
I appreciate Corinna's providing a url
Please don't top post.
On 2013-04-04 13:03, wynfi...@gmail.com wrote:
> I did not ask for native widows programming advice any more than cygwin uses
> win32-api.
> cygwin distributes the header files and I simply asked about linking, which
> is exactly what cygwin built programs do.
>
> I appr
I did not ask for native widows programming advice any more than cygwin uses
win32-api.
cygwin distributes the header files and I simply asked about linking, which is
exactly what cygwin built programs do.
I appreciate Corinna's providing a url to a possible point of source and which
did resp
On Apr 4 17:05, wynfi...@gmail.com wrote:
>
> It is a cygwin related question to me. It involves using cygwin and
> programs built using cygwin. You are wrong to suggest that it doesn't
> related to cygwin. Additionally it involves using cygwin as a
> learning and buiding tool. You should con
It is a cygwin related question to me. It involves using cygwin and programs
built using cygwin. You are wrong to suggest that it doesn't related to
cygwin. Additionally it involves using cygwin as a learning and buiding tool.
You should consider a more constructive response that would be h
28 matches
Mail list logo