On 8/20/2016 5:54 PM, Ken Brown wrote:
I'm trying to rebuild texlive, and the build on x86 is failing as follows:
make[2]: Entering directory
'/home/kbrown/src/cygtexlive/texlive/texlive-20160520-2.i686/build/texk/xdvik'
/bin/sh ./libtool --tag=CC --mode=link gcc -Wimplicit -Wreturn-type
-W
On Sat, Aug 20, 2016 at 3:37 PM, Corinna Vinschen wrote:
> - Fix the bug reported in
> https://cygwin.com/ml/cygwin/2016-08/msg00357.html
Fixed, thanks!
--
Jim Reisert AD1C, , http://www.ad1c.us
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.co
Hello everyone,
FWIW, I can't get the current may git clone of Cygwin to build on the
current release version of itself: (64-bit "Current" on Win10):
/home/hbbro/prg/cygwin/bld/x86_64-unknown-cygwin/newlib/libc/libc.a(lib_a-wcwidth.o):
In function `__wcwidth':
/home/hbbro/prg/cygwin/bld/x86_6
I'm trying to rebuild texlive, and the build on x86 is failing as follows:
make[2]: Entering directory
'/home/kbrown/src/cygtexlive/texlive/texlive-20160520-2.i686/build/texk/xdvik'
/bin/sh ./libtool --tag=CC --mode=link gcc -Wimplicit -Wreturn-type
-Wdeclaration-after-statement -Wno-unknown-
Hi folks,
I uploaded a new Cygwin test release 2.6.0-0.11.
--
I managed to build the 2.6.0-10 package from the wrong sources, so
here's the fixed 2.6.0-0.11. Sorry about that!
---
Am 20.08.2016 um 19:42 schrieb Morten Kjærulff:
Hi,
I thought that #!/bin/sh in a script would be a bash, but it seems not
to be - or what am I doing wrong?
You're asking bash the wrong questions, for starters. In particular,
you're mixing up the check whether the shell running that script _
On Aug 20 15:12, Jim Reisert AD1C wrote:
> On Sat, Aug 20, 2016 at 10:04 AM, Corinna Vinschen wrote:
>
> > Ouch. This is hopefully fixed in 2.6.0-0.10 which I'll upload right
> > after sending this reply.
>
> Nope, not fixed:
>
> CYGWIN_NT-10.0 JJR 2.6.0(0.301/5/3) 2016-08-20 17:49 x86_64 Cygwi
On Sat, Aug 20, 2016 at 10:04 AM, Corinna Vinschen wrote:
> Ouch. This is hopefully fixed in 2.6.0-0.10 which I'll upload right
> after sending this reply.
Nope, not fixed:
CYGWIN_NT-10.0 JJR 2.6.0(0.301/5/3) 2016-08-20 17:49 x86_64 Cygwin
[JJR:/cygdrive/e/unified] $ ls /usr/include/tls*
ls: c
Hi,
I thought that #!/bin/sh in a script would be a bash, but it seems not
to be - or what am I doing wrong?
vp01mkf@DX305 ~/bin
$ cat ./tsh.sh
#!/bin/sh
cat < <(pwd)
vp01mkf@DX305 ~/bin
$ ./tsh.sh
./tsh.sh: line 3: syntax error near unexpected token `<'
./tsh.sh: line 3: `cat < <(pwd)'
vp01mk
On 8/20/2016 9:41 AM, Marco Atzeri wrote:
On 20/08/2016 04:52, Ken Brown wrote:
On 8/19/2016 4:03 PM, Ken Brown wrote:
On 8/19/2016 11:22 AM, Ken Brown wrote:
On 8/19/2016 9:55 AM, Ken Brown wrote:
On 8/19/2016 6:27 AM, Peter Hull wrote:
Hi all,
The problem turns out to be related to the
Hi folks,
I uploaded a new Cygwin test release 2.6.0-0.10.
Two interesting changes in this test release:
- Fix the bug reported in
https://cygwin.com/ml/cygwin/2016-08/msg00357.html
- Add missing nl_langinfo_l functions as reported in
https://cygwin.com/ml/cygwin/2016-08/msg00349.html
===
On Aug 19 19:51, Jim Reisert AD1C wrote:
> I just updated my 64-bit Cygwin environment. All had been working
> fine up until this morning. I last updated when Cygwin 2.6.0-0.8 was
> released a few days ago.
>
> Now I can't compile one (or probably all) of my C programs:
>
> # g++ -Wall -O2 -DDE
Hi Brian,
On Aug 19 13:06, Brian Inglis wrote:
> On 2016-08-19 09:31, Corinna Vinschen wrote:
> > I uploaded a new Cygwin test release 2.6.0-0.9.
> > The 2.6.0 release is going to introducing the locale_t datatype, as well
> > as all functions related to locale_t locales and per-thread locales per
Am 20.08.2016, 15:27 Uhr, schrieb Marco Atzeri:
setup.ini is reporting it on both 32 and 64 bit version:
You're right. Maybe I should stop using apt-cyg ..
-Helmut
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
On 20/08/2016 04:52, Ken Brown wrote:
On 8/19/2016 4:03 PM, Ken Brown wrote:
On 8/19/2016 11:22 AM, Ken Brown wrote:
On 8/19/2016 9:55 AM, Ken Brown wrote:
On 8/19/2016 6:27 AM, Peter Hull wrote:
Hi all,
The problem turns out to be related to the recent update of libgd3.
Reverting to the p
On 20/08/2016 08:31, Helmut Karlowski wrote:
I guess libqpdf17 belongs into the qpdf-dependencies:
$cygcheck qpdf
Found: C:\cygwin\bin\qpdf.exe
C:\cygwin\bin\qpdf.exe
C:\cygwin\bin\cygwin1.dll
C:\WINDOWS\system32\KERNEL32.dll
C:\WINDOWS\system32\ntdll.dll
C:\WINDOWS\system32\KE
16 matches
Mail list logo