>>If I did that, I'd be doing you a disservice. You don't want to mix and
>>match stuff from VC++ and gcc/g++. That's just asking for trouble. I'd
>>recommend just changing the reference to "stdio.h" and using gcc's. If
>>you simply *must* have 'cstdio', you can install the Boost package (see
patrickinminneapolis wrote:
> example_wrap.c includes , but gcc can't find it, can you tell me
> how to tell gcc to look in c:\Program Files\Microsoft Visual Studio
> 8\VC\include\ for it?
Setting aside for a moment the fact that you're trying to do something
totally wrong and broken, the reason
patrickinminneapolis wrote:
'-I' is for finding headers named in an #include directive. But
'>>example_wrap.c' is a source file, not a header, so do this:
gcc -c example.c /cygdrive/c/example_wrap.c
example_wrap.c includes , but gcc can't find it, can you tell me
how to tell gcc to look in c:
On 9/20/07, Corinna Vinschen <[EMAIL PROTECTED]> wrote:
>
> ...which isn't that tricky. In the Disk Management tool (for instance
> right click "My Computer" -> "Manage" to get there via the "Computer
> Management" admin tool) disks are numbered "Disk 0", "Disk 1", etc.
> This order corresponds wi
>>'-I' is for finding headers named in an #include directive. But
'>>example_wrap.c' is a source file, not a header, so do this:
>>gcc -c example.c /cygdrive/c/example_wrap.c
example_wrap.c includes , but gcc can't find it, can you tell me
how to tell gcc to look in c:\Program Files\Microsoft Vi
On 2007-09-20 22:25Z, patrickinminneapolis wrote:
>
> This works fine :
> gcc -c -fpic example.c example_wrap.c
I thought that'd give a (harmless) warning about '-fpic', but anyway...
> But I want to include files in a different directory, so just to test, I
> moved example_wrap.c to c:\ , i te
I'm trying to get the CSharp Swig Callback example to work with Cygwin.
I'm just stuck on an include header problem.
This works fine :
gcc -c -fpic example.c example_wrap.c
But I want to include files in a different directory, so just to test, I
moved example_wrap.c to c:\ , i tested
gcc -c
When exiting any of several common programs, the backgound color of
the console is changed. This has been reported several times,
including as recently as 2006, but no cause has been isolated. Here
is a reproducible sequence of events that will lead to the failure and
hopefully the solution. Usi
chris ortman gmail.com> writes:
>
> That said, my .git folder looks like
> drwxr-xr-x+ and the user is my user name and group is mkgroup-l-d
You should probably fix that, although I don't know if it will affect your
problem.
http://cygwin.com/faq/faq.using.html#faq.using.chmod
> git commit it
I am currently on git 1.5.2.2 that came with cygwin.
I'm not sure what permissions are required, and also don't really understand how
setting permissions in cygwin corresponds with XP.
That said, my .git folder looks like
drwxr-xr-x+ and the user is my user name and group is mkgroup-l-d
I used fi
chris ortman gmail.com> writes:
>
> I just upgraded my cygwin git package to 1.5.3 and how when I try to commit
and
> allow git to launch vim to enter a commit message i have problems.
>
> The commit message normally has some content already in it, but it is now
blank
> and won't let me save
I just upgraded my cygwin git package to 1.5.3 and how when I try to commit and
allow git to launch vim to enter a commit message i have problems.
The commit message normally has some content already in it, but it is now blank
and won't let me save because it says the file can not be opened for wr
From: Brian Dessent [mailto:[EMAIL PROTECTED]
>
> That would be up to the base-files package maintainer,
> however I don't think it's necessary. As I said the current
> DLL code already normalizes symlink targets so if you use a
> snapshot you will see those links in POSIX form with "ls -l"
"Matt Seitz (matseitz)" wrote:
> I appreciate your taking the time to read my suggestion and respond so
> quickly with such a complete clear and complete explanation.
>
> As an alternative suggestion, how about using forward slashes instead of
> backwards slashes ("C:/windows/system32/drivers/etc
From: Brian Dessent [mailto:[EMAIL PROTECTED]
>
> Yes, those symlinks in /etc are explicitly created with Win32
> paths by the base-files postinstall script. I think the
> reasoning here is that if a POSIX path were used for the
> target of the symlink then it would have to be updated if the
On 20 September 2007 10:09, Warren Young wrote:
> Will Parsons wrote:
>> why would cygwin be less secure?
> Just one way it could fail is if there is a buffer overflow in the
> implementation of one of Cygwin's interfaces, and your "100% secure"
> program calls it. It's then only a matter of tim
On Thu, 20 Sep 2007, Christopher Faylor wrote:
> On Thu, Sep 20, 2007 at 03:08:55AM -0600, Warren Young wrote:
> >Will Parsons wrote:
> >>why would cygwin be less secure?
> >
> >The more moving parts, the more things there are to break.
> >
> >Postulate that you have a program that's been audited
> I wrote:
> Jonathan C Allen writes:
>> PACKAGE DESCRIPTION
>> ===
>> ncftp - An improved FTP client
> A diff between the package listing of the last version and the new
> version shows that all the documentation and man pages are missing.
> It l
> Christopher Faylor writes:
> I've made a new version of 'mutt' available for installation. Mutt is a
> text mode mail user agent. This version uses the shared version of
> libiconv which reduces the size of mutt.exe dramatically. More
> importantly, it fixes the problems t
Ronald Fischer wrote:
I configured my system so that it automatically starts Cygwin
during boot time via the Windows autostart feature, by using
startxwin and Cygwin/X to start several xterm and rxvt terminals,
and also to start one bash shell in plain Cygwin (outside X).
Occasionally, one or tw
On Thu, Sep 20, 2007 at 03:08:55AM -0600, Warren Young wrote:
>Will Parsons wrote:
>>why would cygwin be less secure?
>
>The more moving parts, the more things there are to break.
>
>Postulate that you have a program that's been audited to the point that
>you're absolutely certain it's 100% secure
A CVS compile error; FYI:
../../../../cygwin/winsup/cygwin/path.cc: In member function `int
symlink_info::check(char*, const suffix_info*, unsigned int)':
../../../../cygwin/winsup/cygwin/path.cc:3549: error:
`STATUS_OBJECT_NAME_INVALID' undeclared (first use this function)
--
Brian Ford
Lead Re
On Sep 20 10:14, Scalzott, Todd wrote:
> Thank you for the correction on coreutils.
>
> Yes, I am using cmd.exe. The quotes are necessary (try it) or dd goes
> off searching for an UNC.
>
> I have no problem using /dev/sdb, etc., but others that need to know
> how to do a simple image burn do.
On 20 September 2007 07:23, Mike MacFerrin wrote:
> I'm a grad student in a Compiler Tools course, and (as part of the course)
> we're compiling a subset of the Python language down to C, and from there
> to x86 Assmebly. Our code has to pass a lengthy series of test-suites for
> correctness (com
Thank you for the correction on coreutils.
Yes, I am using cmd.exe. The quotes are necessary (try it) or dd goes
off searching for an UNC.
I have no problem using /dev/sdb, etc., but others that need to know
how to do a simple image burn do. So believe it or not, the physical
drive mapping is
A couple of months ago
http://www.cygwin.com/ml/cygwin/2007-07/msg00313.html
I wondered whether a user could use "if [ -w " branching in Cygwin to
distinguish a locked stick from an unlocked stick. Apparently the answer
was No but Corinna identified an easy fix
http://www.cygwin.com/ml/c
PACKAGE DESCRIPTION
===
Homepage: http://packages.debian.org/sid/flip
License : GPL
Flip converts line endings of text files between MS-DOS and
**IX formats. It detects binary files in a nearly foolproof way and
leaves them alone unless you override this. It will also leave files
On 19 September 2007 23:28, James Adams wrote:
> I fixed the problem by installing into another directory other than
> C:\cygwin. I have no idea why this fixes the problem, but probably it has
> something to do with security packages installed on the computer (it's a new
> work laptop which appea
Will Parsons wrote:
why would cygwin be less secure?
The more moving parts, the more things there are to break.
Postulate that you have a program that's been audited to the point that
you're absolutely certain it's 100% secure when run on Linux.
Then you port it to Cygwin. Is it secure? T
I configured my system so that it automatically starts Cygwin
during boot time via the Windows autostart feature, by using
startxwin and Cygwin/X to start several xterm and rxvt terminals,
and also to start one bash shell in plain Cygwin (outside X).
Occasionally, one or two of the shells started
On Sep 19 19:30, BJ wrote:
> I have a file locking problem that is solved under Mac and Linux using
> fcntl:
> int lockRepFile (int fd, char lock, size_t from, size_t length) {
> struct flock fl;
>
> fl.l_start = from;
> fl.l_len = length;
> fl.l_pid = 0;
>
> if (lock == '
maybe this is my same problem...
http://www.paul.sladen.org/vserver/archives/200303/0186.html
anyone know how can i solve it?
Thank you
Daniele
--
View this message in context:
http://www.nabble.com/NFS-mount-problem%3A-portmap-error-tf4465246.html#a12792695
Sent from the Cygwin Users mailin
On Sep 19 14:53, DePriest, Jason R. wrote:
> On 9/19/07, Eric Blake <> wrote:
> > Scalzott, Todd <> writes:
> > > I've discovered what I believe to be a problem with "dd" on several
> > > different XP SP2 systems with Cygwin installed involving the usage of
> > > Windows' \\.\PhysicalDrive nomencla
The cygwin gsl package (GNU Scientific Library) has been updated
to 1.10-1. This is a new upstream release.
For the announcement of gsl version 1.10 see:
http://sources.redhat.com/ml/gsl-announce/2007/msg1.html
The homepage for the GSL is http://www.gnu.org/software/gsl/
The gsl package co
34 matches
Mail list logo
