problem with cross-compilation i686-pc-mingw32

[#Cyrille37#]

Hello
I could not find how to setup cygwin to make cross compilation for host 
i686-pc-mingw32.


I've got packages like :
gcc  3.4.4-3
gcc-core 3.4.4-3
gcc-g++  3.4.4-3
gcc-mingw20040810-1
gcc-mingw-core   20050522-1
gcc-mingw-g++20050522-1

but when running the configure for GMPlib it could not find some tools :

$ ./configure --build=core2-pc-cygwin --host=i686-pc-mingw32 
--enable-cxx --disable-static --enable-shared

checking build system type... core2-pc-cygwin
checking host system type... i686-pc-mingw32
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for i686-pc-mingw32-strip... no
checking for strip... strip
checking whether to enable maintainer-specific portions of Makefiles... no
checking ABI=32
checking compiler i686-pc-mingw32-gcc -m32 -O2 -fomit-frame-pointer ... no
checking compiler i686-pc-mingw32-gcc -O2 -fomit-frame-pointer ... no
checking compiler gcc -m32 -O2 -fomit-frame-pointer ... yes
checking compiler gcc -m32 -O2 -fomit-frame-pointer has 
sizeof(long)==4... yes

...
checking for i686-pc-mingw32-g++... no
checking for i686-pc-mingw32-c++... no
checking for i686-pc-mingw32-gpp... no
checking for i686-pc-mingw32-aCC... no
checking for i686-pc-mingw32-CC... no
checking for i686-pc-mingw32-cxx... no
checking for i686-pc-mingw32-cc++... no
checking for i686-pc-mingw32-cl... no
checking for i686-pc-mingw32-FCC... no
checking for i686-pc-mingw32-KCC... no
checking for i686-pc-mingw32-RCC... no
checking for i686-pc-mingw32-xlC_r... no
checking for i686-pc-mingw32-xlC... no
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
...

Do you know which packages are missing in my cygwin installation ?

Thanks
Cyrille


--
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/

Re: [Packaging error] Singular

[Oliver Wienand]

Hi,

2008/3/19, Dr. Volker Zell:
>  Missing file: /usr/share/doc/Singular-3.0.3/COPYING from package 
> singular-help
>  Missing file: /usr/share/doc/Singular-3.0.3/GPL from package singular-help
>  Missing file: /usr/share/doc/Singular-3.0.3/INSTALL from package 
> singular-help
>  Missing file: /usr/share/doc/Singular-3.0.3/NEWS from package singular-help
>  Missing file: /usr/share/doc/Singular-3.0.3/README from package singular-help
>  singular-help3.0.3-1 Incomplete

I added the license documentation to singular-help. Should I provide a
new Cygwin release or wait for the next upstream release, which is
likely to be due in the next two month?

Sincerely,

Oliver Wienand

--
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/

Re: REPOST: TeXLive cygwin port?

[Václav Haisman]

Sivaram Neelakantan wrote, On 27.3.2008 6:25:

Hello,

Is there a chance of a LaTeX port to cygwin?  The current TeTeX port
is pretty old.

 sivaram
Grab the source of the package, update it to the latest and submit a 
new/updated package. It is your chance to become famous!


--
VH



signature.asc
Description: OpenPGP digital signature

Re: [PATCH] Build system cleanups 1/4

[Paolo Bonzini]

Andreas Schwab wrote:

Paolo Bonzini <[EMAIL PROTECTED]> writes:


This one removes the PICFLAG variables, which are never set, as well as
the makefile fragments that used to set PICFLAG *at the time of Cygnus
configure*.

Committed to gcc and (shortly) to src.


AFAICS this is used by libiberty when --enable-shared.


Also, considering that libstdc++ compiles its own cp-demangle.c, and has 
always done so since it started using the libiberty demangler (r78553):


cp-demangle.c:
rm -f $@
$(LN_S) $(toplevel_srcdir)/libiberty/cp-demangle.c $@
cp-demangle.lo: cp-demangle.c
$(LTCOMPILE) -DIN_GLIBCPP_V3 -Wno-error -c $<
cp-demangle.o: cp-demangle.c
$(C_COMPILE) -DIN_GLIBCPP_V3 -Wno-error -c $<

I wonder why we still compile libiberty for the target at all.  Neither 
it nor libobjc needs it, which would leave only all-target-fastjar 
(which is a bogus target anyway) and all-target-winsup.


Cygwin people, does winsup actually need a target libiberty?  If so, 
were you aware that the target libiberty is not compiled as PIC?


Paolo

--
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/

Re: [PATCH] Build system cleanups 1/4

[Andreas Schwab]

Paolo Bonzini <[EMAIL PROTECTED]> writes:

> If so, were you aware that the target libiberty is not compiled as
> PIC?

This is not true.  The libiberty configure script handles that just
fine.

Andreas.

-- 
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

--
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/

Re: about cyglsa.dll

[Hugh Sasse]

On Wed, 26 Mar 2008, Eric Blake wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> According to Hugh Sasse on 3/26/2008 6:47 AM:
> |> This is getting tiring.  PLEASE follow directions.  I had to once again
> |> reformat and remunge your message.
> | [...]
> | All of which is fair comment, but
> |> - --
> |> Don't work too hard, make some time for fun as well!
> |>
> |> Eric Blake [EMAIL PROTECTED]
> |  ^
> | directly quoted from your .sig  Obviously I've not replied to the list.
> 
> I went ahead and re-added the list, so others can read my thoughts on the
> matter.
> 
> Reread the link: http://cygwin.com/acronyms/#PCYMTNQREAIYR

Fully agree with it, and had read it recently.
> 
> Pasting .sigs verbatim is fair game (ie. if I'm dumb enough to post my own
> email address in my .sig, that's my masochism, and I deserve what I get).

So I was trying to tell you privately, spare your blushes (if any) and 
not risk the misunderstanding that I might be publicly calling you a 
hypocrite -- because that is ABSOLUTELY NOT my intention.  "To err is
human, to really foul things up involve a computer", etc. I'm sure there
are quite enough examples of my own mistakes in various mail archives,
so I'm not too inclined to make life worse for anyone else.  Of course,
now you've made it public I've had to explain all that.

> ~ And my email address is already out there, so I am personally not too
> distraught about yet another instance of my address being exposed - after
> all, I have some decent spam filters at work.

That's OK then, just so long as this hasn't slipped past you.
> 
> But pasting mailing list headers verbatim is not fair game.  It's the
> principle - I strive to educate people who violate list netiquette, so
> that they don't make the same mistake the next time they reply to someone
> else who is more cautious about their .sig.

Absolutely agree with that.
> 
Hugh

--
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/

Re: [PATCH] Build system cleanups 1/4

[Paolo Bonzini]

Andreas Schwab wrote:

Paolo Bonzini <[EMAIL PROTECTED]> writes:


If so, were you aware that the target libiberty is not compiled as
PIC?


This is not true.


Here is the patch I'll test.  I'll commit this as build system 
maintainer; of course any other patch to convert libiberty to libtool 
will have to be approved by the libiberty maintainers.


Paolo
2008-03-27  Paolo Bonzini  <[EMAIL PROTECTED]>

* configure.ac (frags): Don't set, use frag instead.
(PICFLAG): Set here and substitute.
* Makefile.in: Substitute from autoconf.
* configure: Regenerate.

Index: configure.ac
===
--- configure.ac(revision 132479)
+++ configure.ac(working copy)
@@ -187,9 +187,7 @@ case "${host}" in
 esac
 
 if [[ -n "${frag}" ]]; then
-  frags=${libiberty_topdir}/libiberty/config/$frag
-else
-  frags=
+  frag=${libiberty_topdir}/libiberty/config/$frag
 fi
 
 # If they didn't specify --enable-shared, don't generate shared libs.
@@ -200,34 +198,34 @@ case "${enable_shared}" in
   *) shared=yes ;;
 esac
 if [[ "${shared}" = "yes" ]]; then
-  frag=
   case "${host}" in
 *-*-cygwin*)   ;;
-alpha*-*-linux*)   frag=mh-elfalphapic ;;
-arm*-*-*)  frag=mh-armpic ;;
-hppa*-*-*) frag=mh-papic ;;
+alpha*-*-linux*)   PICFLAG=-fPIC ;;
+arm*-*-*)  PICFLAG=-fPIC ;;
+hppa*-*-*) PICFLAG=-fPIC ;;
+i370-*-*)  PICFLAG=-fPIC ;;
+ia64-*-*)  PICFLAG=-fpic ;;
 i[[34567]]86-*-* | x86_64-*-*)
-   frag=mh-x86pic ;;
+   PICFLAG=-fpic ;;
+m68k-*-*)  PICFLAG=-fpic ;;
 powerpc*-*-aix*)   ;;
-powerpc*-*-*)  frag=mh-ppcpic ;;
-sparc*-*-*)frag=mh-sparcpic ;;
-s390*-*-*) frag=mh-s390pic ;;
-*) frag=mh-${host_cpu}pic ;;
+powerpc*-*-*)  PICFLAG=-fPIC ;;
+sparc*-*-*)case "${CFLAGS}" in
+ *-fpic* ) PICFLAG=-fpic ;;
+ * ) PICFLAG=-fPIC ;;
+   esac ;;
+s390*-*-*) PICFLAG=-fpic ;;
   esac
-  if [[ -n "${frag}" ]]; then
-frags="${frags} ${libiberty_topdir}/config/${frag}"
-  fi
 fi
+AC_SUBST(PICFLAG)
 
 echo "# Warning: this fragment is automatically generated" > temp-frag
 
-for frag in ${frags}; do
-  if [[ -f ${frag} ]]; then
-echo "Appending ${frag} to xhost-mkfrag"
-echo "# Following fragment copied from ${frag}" >> temp-frag
-cat ${frag} >> temp-frag
-  fi
-done
+if [[ -n "${frag}" ]] && [[ -f "${frag}" ]]; then
+  echo "Appending ${frag} to xhost-mkfrag"
+  echo "# Following fragment copied from ${frag}" >> temp-frag
+  cat ${frag} >> temp-frag
+fi
 
 # record if we want to build shared libs.
 if [[ "${shared}" = "yes" ]]; then
Index: Makefile.in
===
--- Makefile.in (revision 132479)
+++ Makefile.in (working copy)
@@ -60,7 +60,7 @@ RANLIB = @RANLIB@
 MAKEINFO = @MAKEINFO@
 PERL = @PERL@
 
-PICFLAG =
+PICFLAG = @PICFLAG@
 
 MAKEOVERRIDES =
 

--
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/

RE: about cyglsa.dll

[Dave Korn]

Hugh Sasse wrote on 27 March 2008 10:52:

> So I was trying to tell you privately, spare your blushes (if any) and
> not risk the misunderstanding that I might be publicly calling you a
> hypocrite -- because that is ABSOLUTELY NOT my intention.  

  Of course not.  This is the cygwin list.


  You'd be calling him a hippo-crit, if anything!  ;-)

cheers,
  DaveK
-- 
Can't think of a witty .sigline today


--
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/

Re: Cygwin is saving my ass

[Steven Woody]

The world would get even better if there were on windows at all:-)

On 3/27/08, Ignazio Di Napoli <[EMAIL PROTECTED]> wrote:
> Dave Korn wrote:
> > Robert Latest wrote on 25 March 2008 08:50:
> >
> >> Enter corporate IT. For four weeks now I've been holding my first real
> >> industry job. And I'm locked into a M$ Windows PC. God, I hadn't known
> >> just how much Windows sucks. Everything around here is done with
> >> Access and Excel and lots of ultra-slow VBA glue to hold it more or
> >> less together. Lotus Notes for appointments and email. Well, that's
> >> not going to change, but who helps ME to get MY work done?
> >>
> >> Enter Cygwin. Finally, things flow again. What a relief. Thanks, guys.
> >
> >   :)  I think you speak for quite a lot of people here when you say that.
> I
> > couldn't function in my day-to-day work without a real shell, and grep and
> > sed, and all the gnu tools.  Cygwin makes windows worth using!
>
> My opinion too...
>
> Ignazio
>
>
> --
> 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/
>
>

-- 
Sent from Gmail for mobile | mobile.google.com

woody

then sun rose thinly from the sea and the old man could see the other
boats, low on the water and well in toward the shore, spread out
across the current.

--
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/

RE: problem with cross-compilation i686-pc-mingw32

[Dave Korn]

\#Cyrille37\# wrote on 27 March 2008 08:04:

> Hello
> I could not find how to setup cygwin to make cross compilation for host
> i686-pc-mingw32.
> 
> I've got packages like :
> gcc  3.4.4-3
> gcc-core 3.4.4-3
> gcc-g++  3.4.4-3
> gcc-mingw20040810-1
> gcc-mingw-core   20050522-1
> gcc-mingw-g++20050522-1

  Ok, that's everything you need.
 
> but when running the configure for GMPlib it could not find
> some tools :

> checking compiler i686-pc-mingw32-gcc -m32 -O2
> -fomit-frame-pointer ... no
> checking compiler i686-pc-mingw32-gcc -O2 -fomit-frame-pointer ... no
> checking compiler gcc -m32 -O2 -fomit-frame-pointer ... yes
> checking compiler gcc -m32 -O2 -fomit-frame-pointer has
> sizeof(long)==4... yes ...
> checking for i686-pc-mingw32-g++... no
> checking for i686-pc-mingw32-c++... no
> checking for i686-pc-mingw32-gpp... no
> checking for i686-pc-mingw32-aCC... no
> checking for i686-pc-mingw32-CC... no
> checking for i686-pc-mingw32-cxx... no
> checking for i686-pc-mingw32-cc++... no
> checking for i686-pc-mingw32-cl... no
> checking for i686-pc-mingw32-FCC... no
> checking for i686-pc-mingw32-KCC... no
> checking for i686-pc-mingw32-RCC... no
> checking for i686-pc-mingw32-xlC_r... no
> checking for i686-pc-mingw32-xlC... no

> Do you know which packages are missing in my cygwin installation ?

  Nothing is missing.  What is happening is that cygwin's mingw
cross-compiler is actually built-in to the main system gcc.  You activate it
by passing the flag "-mno-cygwin" to gcc.  So you need to tell configure to
use the main system compiler and pass this flag when compiling.  This can be
done by adding

  CC_FOR_TARGET="gcc -mno-cygwin" CXX_FOR_TARGET="g++ -mno-cygwin"


cheers,
  DaveK
-- 
Can't think of a witty .sigline today


--
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/

Re: about cyglsa.dll

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Hugh Sasse on 3/27/2008 4:51 AM:
| So I was trying to tell you privately, spare your blushes (if any) and
| not risk the misunderstanding that I might be publicly calling you a
| hypocrite -- because that is ABSOLUTELY NOT my intention.

Thanks - no offense taken by any of your actions.  I apologize if my
action of exposing your off-list to the mail caused you any grief, or if I
came over a little too harsh in my reply.

| now you've made it public I've had to explain all that.

Then I think we are both in agreement - we understand the list policy of
munging email addresses from headers, the idea of trimming all but
relevant portions when replying (such as footers), and recognize that some
people (myself included) add email addresses in their footers with full
realization that it might invite more spam.

With that, I think this thread can come to a close, and we can send the
hippos after anyone else who doesn't add anything constructive to the
conversation (myself included - I'm already borderline by posting this
reply, related to cygwin list policy, but unrelated to the original
subject line :)

- --
Don't work too hard, make some time for fun as well!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkfrjfwACgkQ84KuGfSFAYAfewCgqWO16QgVwjg+8matCQUBiLmK
MjcAniZEFyBUCo365oAQmR/InD977kjD
=DV2I
-END PGP SIGNATURE-

--
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/

Re: [Packaging error] Singular

[Corinna Vinschen]

On Mar 27 09:04, Oliver Wienand wrote:
> Hi,
> 
> 2008/3/19, Dr. Volker Zell:
> >  Missing file: /usr/share/doc/Singular-3.0.3/COPYING from package 
> > singular-help
> >  Missing file: /usr/share/doc/Singular-3.0.3/GPL from package singular-help
> >  Missing file: /usr/share/doc/Singular-3.0.3/INSTALL from package 
> > singular-help
> >  Missing file: /usr/share/doc/Singular-3.0.3/NEWS from package singular-help
> >  Missing file: /usr/share/doc/Singular-3.0.3/README from package 
> > singular-help
> >  singular-help3.0.3-1 Incomplete
> 
> I added the license documentation to singular-help. Should I provide a
> new Cygwin release or wait for the next upstream release, which is
> likely to be due in the next two month?

Your choice.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
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/

Re: Bug in mv (coreutils 6.10)

[Corinna Vinschen]

On Mar 26 19:48, Eric Blake wrote:
> $ mkdir example
> $ cd example
> $ touch foo
> $ strace mv foo bar/. 2>&1 |grep rename
> ~  450  103717 [main] mv 2476 rename: 0 = rename
> (c:\cygwin\tmp\example\foo, c:\cygwin\tmp\example\bar\)
>
> That rename should have failed with ENOENT.

That was fixed in CVS for some rtime, but it failed with EINVAL
erroneously.  I changed rename to fail with the same error codes as
Linux in case one of the arguments has a trailing /. component.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
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/

Re: problem with cross-compilation i686-pc-mingw32

[#Cyrille37#]

#Cyrille37# a écrit :

Hello
I could not find how to setup cygwin to make cross compilation for 
host i686-pc-mingw32.


I've got packages like :
gcc  3.4.4-3
gcc-core 3.4.4-3
gcc-g++  3.4.4-3
gcc-mingw20040810-1
gcc-mingw-core   20050522-1
gcc-mingw-g++20050522-1

but when running the configure for GMPlib it could not find some tools :

$ ./configure --build=core2-pc-cygwin --host=i686-pc-mingw32 
--enable-cxx --disable-static --enable-shared

Ok, I've found the solution after many hours with my friend Google ...

must add CC="gcc -mno-cygwin" on the confiure line :

./configure CC="gcc -mno-cygwin" --build=core2-pc-cygwin 
--host=i686-pc-mingw32 --enable-cxx --disable-static --enable-shared


Cyrille


checking build system type... core2-pc-cygwin
checking host system type... i686-pc-mingw32
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for i686-pc-mingw32-strip... no
checking for strip... strip
checking whether to enable maintainer-specific portions of 
Makefiles... no

checking ABI=32
checking compiler i686-pc-mingw32-gcc -m32 -O2 -fomit-frame-pointer 
... no

checking compiler i686-pc-mingw32-gcc -O2 -fomit-frame-pointer ... no
checking compiler gcc -m32 -O2 -fomit-frame-pointer ... yes
checking compiler gcc -m32 -O2 -fomit-frame-pointer has 
sizeof(long)==4... yes

...
checking for i686-pc-mingw32-g++... no
checking for i686-pc-mingw32-c++... no
checking for i686-pc-mingw32-gpp... no
checking for i686-pc-mingw32-aCC... no
checking for i686-pc-mingw32-CC... no
checking for i686-pc-mingw32-cxx... no
checking for i686-pc-mingw32-cc++... no
checking for i686-pc-mingw32-cl... no
checking for i686-pc-mingw32-FCC... no
checking for i686-pc-mingw32-KCC... no
checking for i686-pc-mingw32-RCC... no
checking for i686-pc-mingw32-xlC_r... no
checking for i686-pc-mingw32-xlC... no
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
...

Do you know which packages are missing in my cygwin installation ?

Thanks
Cyrille






--
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/

Re: [PATCH] Build system cleanups 1/4

[Christopher Faylor]

On Thu, Mar 27, 2008 at 12:08:22PM +0100, Paolo Bonzini wrote:
> Andreas Schwab wrote:
>> Paolo Bonzini <[EMAIL PROTECTED]> writes:
>>> If so, were you aware that the target libiberty is not compiled as
>>> PIC?
>> This is not true.
>
> Here is the patch I'll test.  I'll commit this as build system maintainer; 
> of course any other patch to convert libiberty to libtool will have to be 
> approved by the libiberty maintainers.
>
> Paolo

>2008-03-27  Paolo Bonzini  <[EMAIL PROTECTED]>
>
>   * configure.ac (frags): Don't set, use frag instead.
>   (PICFLAG): Set here and substitute.
>   * Makefile.in: Substitute from autoconf.
>   * configure: Regenerate.

FWIW, Cygwin's reliance on libiberty, so:

2008-03-27  Christopher Faylor  <[EMAIL PROTECTED]>

* Makefile.in (all-target-winsup): Remove libiberty dependency.


Index: Makefile.in
===
RCS file: /cvs/uberbaum/Makefile.in,v
retrieving revision 1.279
diff -d -u -r1.279 Makefile.in
--- Makefile.in 27 Mar 2008 14:16:53 -  1.279
+++ Makefile.in 27 Mar 2008 15:16:59 -
@@ -53474,7 +53474,6 @@
 all-target-libstdc++-v3: maybe-all-target-libiberty
 configure-target-libstdc++-v3: maybe-configure-target-libgomp
 all-target-libgloss: maybe-all-target-newlib
-all-target-winsup: maybe-all-target-libiberty
 all-target-winsup: maybe-all-target-libtermcap


--
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/

Re: [PATCH] Build system cleanups 1/4

[Christopher Faylor]

On Thu, Mar 27, 2008 at 11:18:32AM -0400, Christopher Faylor wrote:
>On Thu, Mar 27, 2008 at 12:08:22PM +0100, Paolo Bonzini wrote:
>> Andreas Schwab wrote:
>>> Paolo Bonzini <[EMAIL PROTECTED]> writes:
 If so, were you aware that the target libiberty is not compiled as
 PIC?
>>> This is not true.
>>
>> Here is the patch I'll test.  I'll commit this as build system maintainer; 
>> of course any other patch to convert libiberty to libtool will have to be 
>> approved by the libiberty maintainers.
>>
>> Paolo
>
>>2008-03-27  Paolo Bonzini  <[EMAIL PROTECTED]>
>>
>>  * configure.ac (frags): Don't set, use frag instead.
>>  (PICFLAG): Set here and substitute.
>>  * Makefile.in: Substitute from autoconf.
>>  * configure: Regenerate.
>
>FWIW, Cygwin's reliance on libiberty, so:

Duh.  Try again.

Cygwin no longer relies on libiberty, so...

--
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/

File name length

[Troy Bull]

Greetings

Over the last few days I have ran into the error where a filename is
too long for cygwin.  I know this has been discussed does anyone have
a timeline for when this might get changed?

thanks

troy

--
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/

Re: [PATCH] Build system cleanups 1/4

[Paolo Bonzini]

FWIW, Cygwin's reliance on libiberty, so:


Duh.  Try again.

Cygwin no longer relies on libiberty, so...


You should have disabled it in Makefile.def, but no big deal -- I'll 
take care of it when I'll post a patch to remove target libiberty.


Paolo

--
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/

Cygwin Visuals

[Diego Costa]

Please how can i configure the cygwin shell to be exactly like the
solaris command prompt ?

Can anyone help me ?

Thanks

-- 
Diego

--
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/

Re: File name length

[Larry Hall (Cygwin)]

Troy Bull wrote:

Greetings

Over the last few days I have ran into the error where a filename is
too long for cygwin.  I know this has been discussed does anyone have
a timeline for when this might get changed?


It will be changed for the 1.7.x series.  You can experiment with the
snapshots  if you like.  There are no
firm timeline for the release yet.

--
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/

Re: File name length

[Troy Bull]

On Thu, Mar 27, 2008 at 2:07 PM, Larry Hall (Cygwin)
<[EMAIL PROTECTED]> wrote:
>
> Troy Bull wrote:
>  > Greetings
>  >
>  > Over the last few days I have ran into the error where a filename is
>  > too long for cygwin.  I know this has been discussed does anyone have
>  > a timeline for when this might get changed?
>
>  It will be changed for the 1.7.x series.  You can experiment with the
>  snapshots  if you like.  There are no
>  firm timeline for the release yet.
>

this looks interesting and I am glad to give it a try.  That being
said, how do i use it, just replace my current cygwin1.dll with the
one I download from this snapshot page?

Thanks
troy

--
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/

Re: File name length

[Larry Hall (Cygwin)]

Troy Bull wrote:

On Thu, Mar 27, 2008 at 2:07 PM, Larry Hall (Cygwin) wrote:

Troy Bull wrote:
 > Greetings
 >
 > Over the last few days I have ran into the error where a filename is
 > too long for cygwin.  I know this has been discussed does anyone have
 > a timeline for when this might get changed?

 It will be changed for the 1.7.x series.  You can experiment with the
 snapshots  if you like.  There are no
 firm timeline for the release yet.



this looks interesting and I am glad to give it a try.  That being
said, how do i use it, just replace my current cygwin1.dll with the
one I download from this snapshot page?


Yes, if you just want to use it.  If you want to build things against
this, then you need the larger set of files.  Make sure you've stopped
all Cygwin apps (including services) before doing the replace.

--
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/

RE: File name length

[Dave Korn]

[EMAIL PROTECTED] wrote on 27 March 2008 19:31:

> Troy Bull wrote:
> > On Thu, Mar 27, 2008 at 2:07 PM, Larry Hall (Cygwin) wrote:
> > > Troy Bull wrote:
> > >  > Greetings
> > >  >
> > >  > Over the last few days I have ran into the error where a filename
> > >  is > too long for cygwin.  I know this has been discussed does
> > >  anyone have > a timeline for when this might get changed?
> > > 
> > >  It will be changed for the 1.7.x series.  You can experiment with the
> > >  snapshots  if you like. There are no
> > >  firm timeline for the release yet.
> > > 
> > 
> > this looks interesting and I am glad to give it a try.  That being
> > said, how do i use it, just replace my current cygwin1.dll with the
> > one I download from this snapshot page?
> 
> Yes, if you just want to use it.  If you want to build things against
> this, then you need the larger set of files.  Make sure you've stopped
> all Cygwin apps (including services) before doing the replace.

  IIRC there's a FAQ entry on this.  Hang on, I'll look it up.  Ah, here we
are:

http://cygwin.com/faq/faq-nochunks.html#faq.setup.snapshots


cheers,
  DaveK
-- 
Can't think of a witty .sigline today


--
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/

Re: Cygwin Visuals

[Brian Mathis]

On Thu, Mar 27, 2008 at 2:38 PM, Diego Costa <[EMAIL PROTECTED]> wrote:
> Please how can i configure the cygwin shell to be exactly like the
>  solaris command prompt ?
>
>  Can anyone help me ?
>
>  Thanks
>  --
>  Diego
>

Cygwin by default uses the "bash" shell and runs it in the "Command
Prompt" window for windows.  You can change the shell to something
else if you like, by editing the cygwin.bat file.  You can change the
window it runs in by using either xterm (also requires X Windows to be
installed and running) or by using rxvt, which doesn't require X
Windows.  'rxvt' is a great solution and you will probably think it
works very much like solaris.

Remember that cygwin is not solaris (or any other type of unix) -- it
is its own thing and has its own unique feel to it (though it may be
similar to unix).

--
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/

Re: Cygwin Visuals

[Diego Costa]

Thanks,

But where do i find/config 'rtvt' and Xterm ?

Really thanks

On Thu, Mar 27, 2008 at 5:30 PM, Brian Mathis <[EMAIL PROTECTED]> wrote:
>
> On Thu, Mar 27, 2008 at 2:38 PM, Diego Costa <[EMAIL PROTECTED]> wrote:
>  > Please how can i configure the cygwin shell to be exactly like the
>  >  solaris command prompt ?
>  >
>  >  Can anyone help me ?
>  >
>  >  Thanks
>  >  --
>  >  Diego
>  >
>
>  Cygwin by default uses the "bash" shell and runs it in the "Command
>  Prompt" window for windows.  You can change the shell to something
>  else if you like, by editing the cygwin.bat file.  You can change the
>  window it runs in by using either xterm (also requires X Windows to be
>  installed and running) or by using rxvt, which doesn't require X
>  Windows.  'rxvt' is a great solution and you will probably think it
>  works very much like solaris.
>
>  Remember that cygwin is not solaris (or any other type of unix) -- it
>  is its own thing and has its own unique feel to it (though it may be
>  similar to unix).
>
>  --
>  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/
>
>



-- 
Diego

--
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/

Re: Cygwin Visuals

[Gary Johnson]

On 2008-03-27, Brian Mathis wrote:
> On Thu, Mar 27, 2008 at 2:38 PM, Diego Costa <[EMAIL PROTECTED]> wrote:
> > Please how can i configure the cygwin shell to be exactly like the
> >  solaris command prompt ?

> Cygwin by default uses the "bash" shell and runs it in the "Command
> Prompt" window for windows.  You can change the shell to something
> else if you like, by editing the cygwin.bat file.  You can change the
> window it runs in by using either xterm (also requires X Windows to be
> installed and running) or by using rxvt, which doesn't require X
> Windows.  'rxvt' is a great solution and you will probably think it
> works very much like solaris.
> 
> Remember that cygwin is not solaris (or any other type of unix) -- it
> is its own thing and has its own unique feel to it (though it may be
> similar to unix).

The look of the prompt itself is set by the PS1 variable.  You can 
look in /etc/profile for examples, then put your own definition in 
~/.profile or ~/.bash_profile.

Regards,
Gary


--
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/

Re: 1.5.24-2: Applications automatically restart on crash

[Christopher Morlier]

Christopher Faylor wrote:

set CYGWIN=proc_retry:1

is a much less intrusive way of dealing with this.

cgf


  
The proc_retry:1 worked great!  Although, at first I didn't think it was 
working, because I was trying to set the CYGWIN environment variable 
from within the shell.  For anybody else who does this (at least with 
rxvt), this seems to only work if you set it in the cygwin.bat file that 
launches the terminal.  I presume the CYGWIN variable is only read once 
when launching the the cygwin DLL?


Thanks Chris and Dave.

Best Regards,
Chris

--
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/

Re: Cygwin Visuals

[Andrew DeFaria]

Diego Costa wrote:
Please how can i configure the cygwin shell to be exactly like the 
solaris command prompt ?
By using the same shell and startup files as you do on Solaris! I have a 
set of rc files that I use on HP-UX, Solaris, FreeBDS, Linux and Cygwin. 
All of them give me a consistent environment (involved environment too 
with many aliases/functions for things like IBM/Rational's Clearcase and 
Multisite).


And rxvt is a very good substitute for the cruddy Window cmd window. 
Some things you should like is the ability to resize the rxvt window and 
have say vim just dynamically sense it and adjust. Also copy and paste 
is, for lack of a better term, normal.


Rxvt does not come from Cygwin by default but you can run cygwin.exe and 
search the full listing for it. As it has been said, rxvt can run 
without the heaviness of having to download, install, configure and run 
an X server. It still pays attention to things like ~/.Xdefaults. All in 
all a very good middle ground.


I configure Windows shortcuts to use Cygwin's run.exe program (starts a 
process without having a cmd window terminal pop up) to run rxvt. I then 
use -name to call out a class of .Xdefaults to color and otherwise 
configure the class of terminals (so let's say servers are dark 
backgrounds while desktops are light backgrons) then -e to have rxvt 
exec an ssh to a particular machine. I arrange these in a menu such that 
I just need to open the menu and select the proper machine and viola! An 
rxvt terminal comes up logged into the machine in question. I set up 
preshared ssh keys so that I don't have to constantly be typing in my 
password 1000 times a day and bam! A much more convenient work 
environment. I can be ssh'ed into an HP-UX, Solaris, FreeBDS or Linux 
box - even another Windows box courtesy of Cygwin, and develop software, 
work with Clearcase, build, etc. in my customized and efficient command 
line environment and it all works relatively the same everywhere!

--
Andrew DeFaria 
C:\> Bad command or file name! Go stand in the corner.


--
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/