Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
From: "Ralf Habacker" <Ralf DOT Habacker AT saght DOT tessag DOT com>
To: <cygwin-apps AT cygwin DOT com>
Subject: AW: ask for delivering kde 1.1.2
Date: Fri, 22 Jun 2001 08:37:53 +0200
Message-ID: <002201c0fae5$dd67b530$651c440a@BRAMSCHE>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
In-Reply-To: <20010621112535.G6318@redhat.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400

>
> On Thu, Jun 21, 2001 at 09:44:26AM +0200, Ralf Habacker wrote:
> >or delivering kde 1.1.2
> >>
> >> On Wed, Jun 20, 2001 at 01:39:50PM +0200, Ralf Habacker wrote:
> >> >Hi,
> >> >
> >> >I think some of you you have already noticed, that the socket
> problem in
> >> >relating to kde 1.1.2 was found and that Egor has send me a
> >> patch for this.
> >> >
> >> >I have applied this patch and it seems to work. Thank egor
> for providing
> >> >this.
> >> >
> >> >But now I have a question concerning the pending kde beta
> >> release. How do I
> >> >distribute this patched cygwin. Do we 1) should build an building an
> >> >experimental version of cygwin (perhaps a modified 1.3.2-1
> >> release) and to
> >> >distribute it with the cygwin setup or 2) should this be
> >> integrated in the
> >> >next regular cygwin release ?
> >> >
> >> >For 2) I think there is additional work needed to make this
> >> release stable,
> >> >as I recognized several problem with the recent cvs version
> (yesterday)
> >> >
> >> >1. libc uses a symbol _cygwin_istext_for_stdio, which was not
> exported by
> >> >cygwin (cygwin.din)
> >>
> >> You SHOULD NOT be linking with a libc.a build in newlib.  This
> file is not
> >> intended to be used by applications.  You should never include -lc on
> >> your command line.
> >>
> >As I understood building cygwin I have to checkout the whole winsup dir,
> >create a
> >build dir, enter this dir and call configure from the top src dir.
> >Then I have to call make in the build dir and the whole cygwin will be
> >compiled.
> >then I have to install 'libiberty newlib cygwin utils' into a
> tempory dir (I
> >have figured out that from the /etc/setup/cygwin.lst.gz) and
> build a tar or
> >bz2 archive. Then this could be installed with the setup.exe if
> setup.ini is
> >updated with this package after closing all running cygwin apps.
> Does I have
> >understood something wrong ?
> >I have done this with the cygwin 1.3.2-1 source too and there
> was no error
> >in this way.
>
> What I said was true.  You do not use any of the libraries in newlib.
>
Isn't this ensured through the Makefile in the newlib dir ?

> >> >3. I have created scripts for short calling windows apps in the
> >> background
> >> >like
> >> >   /usr/local/bin/vc:
> >> >      # call visual c++
> >> >      /cygdrive/c/programme..../msvc.exe `cygpath -aw $1` &
> >> >
> >> >   The "sending in background" doesn't work.
> >> >
> >> >   In cygwin 1.3.2-1 I have called
> >> >
> >> >        vc xyz.c
> >> >
> >> >   with this snapshot I have to call
> >> >
> >> >       vc xyz.c &
> >> >
> >> >   for the first time.
> >>
> >...  otherwise I can't enter any more command in the bash shell because
> >vc blocks it.
> >
> >>I'm sorry but I don't know what "sending in the background" means.
> >
> >I mean the '&' which I have added to the script, which will not work
> >
> >>saying that the `cygpath ...` doesn't work?  Or are you saying that
> >>typing "vc xyz.c" doesn't work?
> >
> >If not WHAT IS THE ERROR?  PLEASE!
> >
> >>Think about this as if we are not inside your mind or peering over your
> >>shoulder while you type.
> >>
> >>If you can't provide details then we can't fix the problem.  It's that
> >>simple.
> >
> >Of course, but I think the difference of calling "vc xyz" or vc xyz &"
> >is clear.  To avoid the second sample i have placed the '&' into the
> >script and this functionality does not work.
>
> Are you saying that vc is accepting input from stdin when you run it
> from bash?  Or is bash not detecting the exit of msvc perhaps?
>
vc is a native windows application like the the cygwin installer setup.exe,
frontpage or something else. If you start setup.exe on the bash shell, it
will block the shell unless you are "send it into the background" as I call
with '&'.
Because I don't like to add '&' to every command I have placed this into the
script and this doesn't work.

An example for setup.exe

/usr/local/bin/se
	..../setup.exe <params> &

call
	$ se

should be start setup.exe and allow entering additional command into the
bash shell.
In the error case the bash shell is blocked.

regards
Ralf


> cgf
>