From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Fwd: octave updated to 3.4.0-3. Please test
Date: Thu, 31 Mar 2011 10:41:00 -0000 [thread overview]
Message-ID: <AANLkTimJ7=6AaGdNUxnCu3_p3k1CW9kByWAzAQ-UfOLw@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=_WBph8XP1Nd0eDmDoKuurdUeN=SFONH68WunW@mail.gmail.com>
same message for the cygwin mailing list, hoping that now I catch all the users.
Not the standard announcement message, but the situation was a bit unusual.
Marco
---------- Forwarded message ----------
From: marco atzeri
Date: Thu, Mar 31, 2011 at 7:22 AM
Subject: octave updated to 3.4.0-3. Please test
To: Octave users list
dear octave user on cygwin,
after some tricking, hacking and polishing the new octave 3.4.0-3 has
been released for cygwin.
Also lapack and qrupdate have been updated to solve the
libgfortran3-4.3.4-4 issue.
This configuration should work :
$ cygcheck -c octave liblapack0 cygwin libqrupdate0 libgfortran3
Cygwin Package Information
Package Version Status
cygwin 1.7.9-1 OK
libgfortran3 4.3.4-4 OK
liblapack0 3.2.2-2 OK
libqrupdate0 1.1.1-1 OK
octave 3.4.0-3 OK
and also this one (as I built all the package on cygwin-1.7.8-1 and
libgfortran3-4.3.4-4 )
$ cygcheck -c octave liblapack0 cygwin libqrupdate0 libgfortran3
Cygwin Package Information
Package Version Status
cygwin 1.7.8-1 OK
libgfortran3 4.3.4-4 OK
liblapack0 3.2.2-2 OK
libqrupdate0 1.1.1-1 OK
octave 3.4.0-3 OK
the configuration before libgfortran3 update, that worked was
$ cygcheck -c octave liblapack0 cygwin libqrupdate0 libgfortran3
Cygwin Package Information
Package Version Status
cygwin 1.7.8-1 OK
libgfortran3 4.3.4-3 OK
liblapack0 3.2.2-1 OK
libqrupdate0 1.1.0-1 OK
octave 3.4.0-2 OK
please test, including plotting and in case of failures let me know on
this mailing list or (better) in the cygwin mailing list.
Regards
Marco
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next parent reply other threads:[~2011-03-31 5:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTi=_WBph8XP1Nd0eDmDoKuurdUeN=SFONH68WunW@mail.gmail.com>
2011-03-31 10:41 ` marco atzeri [this message]
2011-03-31 20:38 ` Fwd: octave updated to 3.4.0-3. Please test (strcat error) A.R. Burgers
2011-03-31 20:58 ` marco atzeri
2011-03-31 21:33 ` A.R. Burgers
2011-03-31 21:53 ` A.R. Burgers
2011-04-01 2:22 ` marco atzeri
2011-04-01 5:25 ` Christopher Faylor
2011-04-01 6:32 ` marco atzeri
2011-04-02 16:40 ` marco atzeri
2011-04-04 22:19 ` Christopher Faylor
2011-04-04 22:21 ` marco atzeri
2011-04-06 10:04 ` Tatsuro MATSUOKA
2011-04-06 17:39 ` Christopher Faylor
2011-04-08 4:51 ` Stan
2011-04-08 11:04 ` Christopher Faylor
2011-04-08 11:15 ` marco atzeri
2011-04-01 2:52 ` Tatsuro MATSUOKA
2011-05-09 9:15 ` Stephane MONTESINO
[not found] ` <558253.52815.qm@web111307.mail.gq1.yahoo.com>
2011-03-31 21:23 ` octave updated to 3.4.0-3. Please test marco atzeri
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='AANLkTimJ7=6AaGdNUxnCu3_p3k1CW9kByWAzAQ-UfOLw@mail.gmail.com' \
--to=marco.atzeri@gmail.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).