public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Empty include file on samba share
Date: Wed, 07 Jan 2009 18:05:00 -0000	[thread overview]
Message-ID: <4964E4BF.6050002@cygwin.com> (raw)
In-Reply-To: <5.2.0.9.1.20090107170800.01ebc130@localhost>

Fabian Cenedese wrote:
> Hi
> 
> I have a problem that may be cygwin or not. I'll just ask here if anybody knows
> something (or to show me some better place to go to).
> 
> We use a quite old cross-gcc (2.95.2), built with cygwin and running on various
> windows (since NT on to vista). The currently used cygwin is version
> 1.5.19-cr-0x5ef, but we have also worked with other versions. We have
> some projects that are C++ with header files and can be compiled with
> no problems on a local drive.
> 
> However if the whole C++ project is moved from the local drive to a
> share (samba, probably also windows) the compilation may fail with
> various errors. The main problem seems to be that include files are not
> read properly. They are found (gcc emits an error if the name is wrong)
> but the content seems not to be read. Even if such a problematic
> header file contains crap it is not mentioned by gcc. To make things
> worse is that on different computers the compilation may fail differently
> or even work without problems.
> 
> I don't know if there's anything I could change in cygwin to improve
> this (except updating, but I'd like to hear first, if this is known).
> 
> Has anybody ever experienced something similar? Or an idea what I
> could look into (from the cygwin side)? I have already asked on the
> gcc mailinglist, but it was unknown so far.

We're missing some information about your system configuration.  Please
read the problem reporting guidelines found at the link below, paying
particular attention to the part about the cygcheck output.  A STC might
also be warranted.

> Problem reports:       http://cygwin.com/problems.html

Absent the above, my WAG is that you need to add 'smbntsec' to your
CYGWIN environment variable.

<http://cygwin.com/cygwin-ug-net/using-cygwinenv.html>

Exit all Cygwin processes/services for good measure.

-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (508) 893-9889 - FAX
Holliston, MA 01746

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2009-01-07 17:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07 17:23 Fabian Cenedese
2009-01-07 18:05 ` Larry Hall (Cygwin) [this message]
2009-01-08 10:33   ` Fabian Cenedese
2009-01-09 20:49     ` Dave Korn
     [not found]   ` <2ca21dcc0901091134l682660fem1ebac27ee6afd69e@mail.gmail.co  m>
2009-01-16 12:24     ` Fabian Cenedese
2010-03-17  8:19     ` Fabian Cenedese
     [not found] ` <4966299F.9040300@cygwin.com>
2009-01-09 12:21   ` Fabian Cenedese
2009-01-09 17:55     ` Larry Hall (Cygwin)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4964E4BF.6050002@cygwin.com \
    --to=reply-to-list-only-lh@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).