On 04/12/2011 07:38 AM, Hans Horn wrote:
Folks,
has anybody got any experience interfacing (g)fortran routines with Java via
JNI?
I'm on 64bit Windows7 using cygwin
x86_64-w64-mingw32-gcc and x86_64-w64-mingw32-gfortran, both v4.5.2
Java: jdk-6u24-windows-x64
Even though I can statically
On 03/26/2011 03:33 AM, marco atzeri wrote:
On Sat, Mar 26, 2011 at 10:45 AM, Corinna Vinschen wrote:
On Mar 26 06:56, marco atzeri wrote:
Hi,
I rebuilt lapack, qrupdate, octave and netcdf with the libgfortran3-4.3.4-4.
( If you wan to try them, install with
setup.exe -X -O -s
On 03/26/2011 08:35 AM, Jerry DeLisle wrote:
I have been monitoring this thread for the libgfortran maintainer side, but have
not had time yet to investigate further. The only platform reporting the issue
so far is Cygwin. I am not aware of any changes occurring with 4.3 upstream of
Cygwin
On 03/26/2011 11:18 AM, marco atzeri wrote:
--- snip ---
Today I have
cygwin-1.7.7 , libgfortran3-4.3.4-3, lapack-3.2.2-1,
qrupdate-qrupdate-1.1.0-1 fine
cygwin-1.7.8 , libgfortran3-4.3.4-4, lapack-3.2.2-2,
qrupdate-qrupdate-1.1.1-1 broken (as also octave3.4.0-3)
The full source is here, and
See attached stackdump. This output was followed by a bundle of messages like
this:
End of stack trace
7247 [sig] top 6112 exception::handle: Error while dumping state (probably
corrupted stack)
128235 [sig] top 6112 exception::handle: Error while dumping state (probably
corrupted stack)
We are developing a quad precision floating point library for use with gfortran.
When attempting to build the library under Cygwin, we are stopped because:
__float128 is not supported when running the ./configure for the package. I
suspect the issue may be related to newlib vs glibc, but I
Hi,
Who is the Cygwin gcc package maintainer? I want to make sure my gfortran 4.6
experimental builds are consistent with Cygwin distributions. I notice I have
far fewer configure parameters then I see when I invoke gfortran -v .
Regards,
Jerry
--
Problem reports:
On 08/07/2010 01:13 PM, Dave Korn wrote:
On 07/08/2010 17:59, Jerry DeLisle wrote:
Hi,
Who is the Cygwin gcc package maintainer?
I've been a bit AWOL recently, but I think that's still me :-/
I want to make sure my
gfortran 4.6 experimental builds are consistent with Cygwin
Paul Bibbings wrote:
Whilst I do use the versions of gcc available as Cygwin packages, I have
also successfully built from source and used other versions. Most
recently I have added gcc-4.4.1, 4.4.3 and a 4.5.0 snapshot (end of Feb
2010). I configure them to build and install in
The gfortran binary at the wiki has been updated to latest trunk experimental
4.6. This binary includes c, c++, and fortran compilers. (Note: This is not an
official Gnu or Cygwin release.)
Let me know if any problems encountered.
http://gcc.gnu.org/wiki/GFortranBinaries
Regards,
Jerry
--
On a separate machine from my previous install problem, setup.exe runs but I get
this warning:
The current ini file is from a newer version of setup.exe. If you have any
trouble installing, please download a fresh
I have scanned the disks for any ini I can find and there are none
On 12/28/2009 08:18 PM, Christopher Faylor wrote:
On Mon, Dec 28, 2009 at 08:05:10PM -0800, Jerry DeLisle wrote:
On a separate machine from my previous install problem, setup.exe runs but I get
this warning:
The current ini file is from a newer version of setup.exe. If you have any
trouble
On 12/28/2009 08:41 PM, Jerry DeLisle wrote:
On 12/28/2009 08:18 PM, Christopher Faylor wrote:
On Mon, Dec 28, 2009 at 08:05:10PM -0800, Jerry DeLisle wrote:
On a separate machine from my previous install problem, setup.exe
runs but I get
this warning:
The current ini file is from a newer
I have been using the 1.7 beta without any issues up until the official release.
I try to run 1.7.1 setup and nothing happens, it just exits without even
opening a window.
Trying to run the previous version of setup works until it encounters setup.ini
which no longer matches the version.
Christopher Faylor wrote:
On Sun, Dec 27, 2009 at 07:57:37AM -0800, Jerry DeLisle wrote:
I have been using the 1.7 beta without any issues up until the official release.
I try to run 1.7.1 setup and nothing happens, it just exits without even
opening a window.
Trying to run the previous
Jerry DeLisle wrote:
Christopher Faylor wrote:
On Sun, Dec 27, 2009 at 07:57:37AM -0800, Jerry DeLisle wrote:
I have been using the 1.7 beta without any issues up until the
official release. I try to run 1.7.1 setup and nothing happens, it
just exits without even opening a window.
Trying
Andy Koppe wrote:
2009/12/27 Jerry DeLisle:
I am going to try a completely fresh install. I have nothing to lose.
No point in that. I'm afraid you'll need to wait for a setup.exe fix.
No problem, I appreciate the help.
I do hope this will be fixed. Admittedly there may not be too many
Christopher Faylor wrote:
On Sun, Dec 27, 2009 at 09:20:11AM -0800, Jerry DeLisle wrote:
Jerry DeLisle wrote:
Christopher Faylor wrote:
On Sun, Dec 27, 2009 at 07:57:37AM -0800, Jerry DeLisle wrote:
I have been using the 1.7 beta without any issues up until the
official release. I try
Christopher Faylor wrote:
On Sun, Dec 27, 2009 at 12:28:47PM -0500, Christopher Faylor wrote:
Hold off. I'm fixing setup.exe now.
I've uploaded a new version. It seems to work ok on NT4.
It appears to be working here as well. Running now.
Thanks,
Jerry
--
Problem reports:
On 12/27/2009 10:25 AM, Christopher Faylor wrote:
On Sun, Dec 27, 2009 at 12:28:47PM -0500, Christopher Faylor wrote:
Hold off. I'm fixing setup.exe now.
I've uploaded a new version. It seems to work ok on NT4.
What is the version number of the new one?
I have moved to a new location on
On 11/20/2009 06:24 PM, Linda Walsh wrote:
Andy Koppe wrote:
2009/11/20 Linda Walsh:
Some things are obviously not cygwin related. But sometimes it seems
like cygwin isn't able to see files that I can see there with explorer.
We'd of course need concrete examples for this.
I'd love to
See the wiki:
http://gcc.gnu.org/wiki/GFortranBinaries
This binary was built with Cygwin-1.7 running on WinNT in VirtualBox on a Linux
host. It is provided as a courtesy to expand the gfortran test base and provide
users the latest bug fixes and features.
Comments and bug reports welcome.
On 10/01/2009 02:21 PM, Jim Reisert AD1C wrote:
I understand this error:
# gcc-4 -mno-cygwin
gcc-4: The -mno-cygwin flag has been removed; use a mingw-targeted
cross-compiler.
However, I could find no mingw-targeted cross-compiler for gcc-4
(though they seem to be there for gcc-3). Does one
On 09/14/2009 02:04 AM, Dave Korn wrote:
Dave Korn wrote:
Nah, hang on, I'll give the psychic debugging a go.places hand to
forehead, covering eyes, waves other hand out in front of me in a
mystical-looking way I'm getting something the spirits are talking... or
maybe it's just the
I first noticed this when trying to build and run gfortran 4.5 for my
development work on cygwin 1.7. This is on WinNT running in VirtualBox.
With 4.5, I get no output at all. With gfortran distributed with Cygwin
I get the following. Am I configured wrong?
Regards,
Jerry
$ cat
On 08/13/2009 09:06 AM, Corinna Vinschen wrote:
Hi folks,
I just uploaded a new Cygwin 1.7 test release, 1.7.0-58.
I still refrain from telling stuff like this is the last test release,
but I still hope we're getting really close now, even after I had
screwed up so nicely with the 1.7.0-53
On 08/06/2009 08:02 AM, Stephan Mueller wrote:
Andy Koppe wrote:
(And to be honest I don't see the point in Cygwin 1.7 still supporting
NT4. Anyone willing to stick with an OS that's been unsupported for
five years should be more than happy to stick with Cygwin 1.5.)
Agreed, it seems a bit
I tried to bunzip the snapshot and get the following:
~
$ bunzip2.exe cygwin1-20090804.dll.bz2
bunzip2: Data integrity error when decompressing.
Input file = cygwin1-20090804.dll.bz2, output file =
cygwin1-20090804.dll
It is possible that the compressed file(s) have become corrupted.
On 08/04/2009 07:43 PM, Jerry DeLisle wrote:
I tried to bunzip the snapshot and get the following:
~
$ bunzip2.exe cygwin1-20090804.dll.bz2
bunzip2: Data integrity error when decompressing.
Input file = cygwin1-20090804.dll.bz2, output file =
cygwin1-20090804.dll
It is possible
On 08/04/2009 08:27 PM, Christopher Faylor wrote:
I screwed up the previous cygwin-20090804 snapshot but there is a new
one up now which shouldn't produce a STATUS_EXCEPTION_VIOLATION.
Sorry for the inconvenience with the previous one.
This one installs and runs fine now on NT 4.
Jerry
I have posted a link to gfortran and gcc binaries for the latest gcc
experimental 4.5 trunk at the gfortran wiki.
This was built under Cygwin-1.7. I do not know if they will run on under
Cygwin-1.5.
These binaries are pre-release provided for testing purposes. The executables
are stripped.
Christopher Faylor wrote:
On Mon, Jul 06, 2009 at 12:32:16AM -0400, Christopher Faylor wrote:
On Mon, Jul 06, 2009 at 05:20:41AM +0100, Dave Korn wrote:
Jerry DeLisle wrote:
I am making the switch to 1.7. I started with a clean windows (nt4)
environment and went through the usual run
Christopher Faylor wrote:
--- snip ---
I will try the manual process you suggested after I figure out how to get the
snapshot and when it is available.
Bare in mind that I am using the broken environment to do this. I managed to
extract the snapshot and replace the cygwin1.dll while not
Christopher Faylor wrote:
On Mon, Jul 06, 2009 at 10:55:40AM -0700, Jerry DeLisle wrote:
Christopher Faylor wrote:
--- snip ---
I will try the manual process you suggested after I figure out how to get the
snapshot and when it is available.
Bare in mind that I am using the broken environment
Dave Korn wrote:
--- snip ---
This is not a binutils bug report any longer! Try downgrading bash; there's
a problem with the new libreadline7 build, which hopefully a respin with gcc-4
and this new binutils will fix.
cheers,
DaveK
I backed down on bash version which required
Vincent R. wrote:
I backed down on bash version which required install of libreadline6.
bash still fails. This is on NT4.
Maybe I need a different combination of binutils, libreadline, and bash.
I
will
play with this for a bit.
Jerry
I have installed new binutils and previous bash
Moving to this thread:
Vincent R. wrote:
I backed down on bash version which required install of libreadline6.
bash still fails. This is on NT4.
Maybe I need a different combination of binutils, libreadline, and bash.
I
will play with this for a bit.
Jerry
I have installed new
See attached file.
Regards,
Jerry
Cygwin Configuration Diagnostics
Current System Time: Sun Jul 05 12:28:58 2009
Windows NT 4 Workstation Ver 4.0 Build 1381 Service Pack 6
Path: C:\WINNT\system32
C:\WINNT
D:\cygwin-1.7\bin
SysDir: C:\WINNT\System32
WinDir: C:\WINNT
PWD =
Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jerry DeLisle on 7/5/2009 1:35 PM:
Warning: There are multiple cygwin1.dlls on your path
That's probably your culprit.
I saw that too and did a full search of the disk and there is only one
cygwin1.dll
I am
Dave Korn wrote:
Vincent R. wrote:
bash 3.2.49-22 OK
libreadline6 5.2.14-12 OK
libreadline7 6.0.3-1OK
Jerry DeLisle wrote:
bash 3.2.49-22
libreadline6 5.2.14-12
libreadline7 6.0.3-1
Here is some more information:
bash-3.2$ ./cygcheck -s jerrycheck
741 [main] id 85 _cygtls::handle_exceptions: Exception:
STATUS_STACK_OVERFLO
W
3209 [main] id 85 open_stackdumpfile: Dumping stack trace to
id.exe.stackdump
garbled output from 'id' command - no uid= found
1206 [main]
Christopher Faylor wrote:
On Sun, Jul 05, 2009 at 07:34:24PM -0700, Jerry DeLisle wrote:
Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jerry DeLisle on 7/5/2009 1:35 PM:
Warning: There are multiple cygwin1.dlls on your path
That's probably your culprit.
I
Dave Korn wrote:
Jerry DeLisle wrote:
Well, I am moving to this thread now.
Jerry, can I show you something you must not have realised about how email
threading works?
Thank you for pointing this out. I usually don't use the thread view in my mail
client. I will avoid this breakage
I am making the switch to 1.7. I started with a clean windows (nt4) environment
and went through the usual run of setup-1.7 downloaded today.
All appears fine, but bash does not get initialized.
pwd is /usr/bin
path is not set
home directory is not created
These are all taken care of
Christopher Faylor wrote:
On Mon, Jul 06, 2009 at 05:20:41AM +0100, Dave Korn wrote:
Jerry DeLisle wrote:
I am making the switch to 1.7. I started with a clean windows (nt4)
environment and went through the usual run of setup-1.7 downloaded today.
All appears fine, but bash does not get
I am making the switch to 1.7. I started with a clean windows (nt4) environment
and went through the usual run of setup-1.7 downloaded today.
All appears fine, but bash does not get initialized.
pwd is /usr/bin
path is not set
home directory is not created
These are all taken care of
Christopher Faylor wrote:
I've made a new version of binutils available for installation. This is
a much-needed, much-delayed refresh against the current CVS. It should
work better with gcc-4.
The list of changes is included after the unsubscribe info. This is a
list of changes from three
Current 1.7 documentation states that Cygwi-1.7 will not work on Win 95, 98, or
Me. Does this also include Win NT? I tried installing on Win NT and I get the
following when trying to open a terminal.
78 [main] bash 139 tty_list::allocate: No tty allocated
Any help or clarification would be
Christopher Faylor wrote:
On Sun, Jun 21, 2009 at 06:45:48AM -0700, Jerry DeLisle wrote:
Current 1.7 documentation states that Cygwi-1.7 will not work on Win 95, 98, or
Me. Does this also include Win NT?
I tried installing on Win NT and I get the following when trying to
open a terminal.
78
While attempting to run the gcc testsuite today I am getting this error.
Bash appears to then lock up. If I attempt to close the terminal
window, I get a windows error dialog about failing to respond. If I
select to end the hung task, it terminates and the bash command prompt
comes back.
Jerry DeLisle wrote:
While attempting to run the gcc testsuite today I am getting this error.
Bash appears to then lock up. If I attempt to close the terminal
window, I get a windows error dialog about failing to respond. If I
select to end the hung task, it terminates and the bash command
I have updated the Cygwin build of gfortran 4.4 experimental on the gfortran
wiki to 10-19-2008 trunk. This is not a regular Cygwin package.
http://gcc.gnu.org/wiki/GFortranBinaries
Please let me know if anyone has any problems with it.
Best regards,
Jerry
--
Unsubscribe info:
Hi folks,
I am implementing UTF-8 encoding capability for gfortran. I can test fine on
linux platforms because the gnome-terminal has UTF-8 capability built in.
How can I achieve similar capability in a Cygwin terminal so that I can test the
gfortran Cygwin build? The gfortran library code
Jason Pyeron wrote:
We use utf teraterm which has a cygterm built in.
http://www.google.com/search?source=ighl=enrlz=q=teraterm+utf
http://ttssh2.sourceforge.jp/
--
Thank you very much.
This looks like it will work well.
Jerry
--
Unsubscribe info:
Corinna Vinschen wrote:
On Feb 5 17:23, Jerry DeLisle wrote:
Corinna Vinschen wrote:
On Feb 4 17:24, Christopher Faylor wrote:
On Mon, Feb 04, 2008 at 01:25:27PM -0800, Jerry DeLisle wrote:
The test also appears very clean on Linux. The gfortran library is
implemented in C. I need
Corinna Vinschen wrote:
On Feb 4 17:24, Christopher Faylor wrote:
On Mon, Feb 04, 2008 at 01:25:27PM -0800, Jerry DeLisle wrote:
The test also appears very clean on Linux. The gfortran library is
implemented in C. I need to examine some dumps from the compiler and I
will get back with you
Corinna Vinschen wrote:
On Feb 3 11:24, Jerry DeLisle wrote:
I have confirmed this problem on Cygwin reported here:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063
I am not very familiar with the windows environment. Having patched most
of the gfortran I/O library in the last 2-3 years I
Dave Korn wrote:
On 04 February 2008 22:25, Christopher Faylor wrote:
On Mon, Feb 04, 2008 at 01:25:27PM -0800, Jerry DeLisle wrote:
The test also appears very clean on Linux. The gfortran library is
implemented in C. I need to examine some dumps from the compiler and I
will get back
I have confirmed this problem on Cygwin reported here:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063
I am not very familiar with the windows environment. Having patched most of the
gfortran I/O library in the last 2-3 years I can say that we do a lot of memory
allocation for I/O.
On
Dave Korn wrote:
On 03 February 2008 19:24, Jerry DeLisle wrote:
I have confirmed this problem on Cygwin reported here:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063
Those of you most familiar with the Windows environment could perhaps help
here. Is this a bug in Cygwin memory
Angelo Graziosi wrote:
Jerry DeLisle wrote:
I have confirmed this problem on Cygwin reported here:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063
I do not know if this can help, but...
Building the above test with G95, it does not fail!
If I have understood it, I have pressed 1
I ssh into my remote Cygwin box. Is there a way to run a script to check for
updates, download them, and install?
Thanks,
Jerry
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation:
Angelo Graziosi wrote:
Jerry DeLisle wrote:
Is there a way to run a script to check for updates, download them,
and install?
I download the updates using a combination of a my script (getcurr.sh)
and one (clean_setup.pl) found following the Cygwin lists. See the
attachment in [1].
In any
Brian Dessent wrote:
Kevin Hilton wrote:
Let me just make sure I know what you are telling me to do, since I
already did this and it didnt make a difference. As an administrator,
I:
1. Delete the sshd user -- Ok I manually edited the /etc/passwd file
and deleted this user
No, I mean delete
Angelo Graziosi wrote:
Corinna Vinschen wrote:
I've made another version of the Cygwin DLL, 1.5.25-3
With this new version of Cygwin, the problem, with which I started this
thread, seems to be solved!
Now the build of GFortran (20071201, trunk 130556) is completed without
problems.
Many
Corinna Vinschen wrote:
[Forgot to CC the fortran list. Re-sending...]
On Nov 29 17:05, Jerry DeLisle wrote:
Angelo Graziosi wrote:
/tmp/gcc/libgfortran/intrinsics/system_clock.c: In function
'system_clock_4':
/tmp/gcc/libgfortran/intrinsics/system_clock.c:67: error: storage size of
'tzp
Angelo Graziosi wrote:
For the sake of completeness I want to flag the following.
Building GFortran CVS 20071129 trunk 130516 on Cygwin it fails in this
way:
...
libtool: compile: /tmp/gcc/build/./gcc/xgcc
67 matches
Mail list logo
