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++200
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: /
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.a
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 w
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, 90
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 fai
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
wi
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
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
\#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-mingw2004081
-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.
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/INS
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
#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
g
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
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 no
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:
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.co
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/do
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
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
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 cha
[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
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
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
> > s
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 f
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
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 envir
28 matches
Mail list logo