On Tue, 2011-11-15, upset was true to its name and complained:
upset: *** setup.ini: warning - package libneon26 refers to non-existent
external-source: neon
Dr. Volker Zell,
Apparently you did some pruning in release/neon, but now there is no
source package for libneon26-0.26.4-1. Nothing
Please upload the release update package for mined:
mkdir mined
cd mined
wget http://towo.net/mined/cygwin/mined-2011.19-0.tar.bz2
wget http://towo.net/mined/cygwin/mined-2011.19-0-src.tar.bz2
wget
Thank you, Whatzit Toya, your solution compatibility mode/run as admin solution
worked like a charm for me!
-jw
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:
CVSROOT:/cvs/uberbaum
Module name:winsup
Changes by: c...@sourceware.org 2011-11-16 04:09:33
Modified files:
cygwin : ChangeLog child_info.h dcrt0.cc sigproc.cc
spawn.cc
Log message:
* child_info.h (CURR_CHILD_INFO_MAGIC):
Hi all,
There seems to be a packaging error in autoconf (autoconf2.5-2.68-1
according to cygcheck -f /usr/share/man/man1/autoconf-2.68.1.gz).
The shorter names for the man pages point to non-existent files:
~/workspace/TTCNv3 $ file /usr/share/man/man1/auto*
On 11/15/2011 5:06 AM, Csaba Raduly wrote:
Hi all,
There seems to be a packaging error in autoconf (autoconf2.5-2.68-1
according to cygcheck -f /usr/share/man/man1/autoconf-2.68.1.gz).
The shorter names for the man pages point to non-existent files:
The symlinks don't appear in the output of
On 11/14/2011 6:11 PM, Christopher Faylor wrote:
FYI, the last thing any developer wants to hear after a major code
change is a generic It's broke report with no details and no way to
duplicate the problem. A stack trace from a home-grown version of
cygwin1.dll is not a detail. It's
On 09/11/2011 12:15, Edvardsen Kåre wrote:
This is again related to the failure of execution of a gfortran built
binary (cannot execute binary, see thread
http://cygwin.com/ml/cygwin/2011-11/msg00034.html )
In short, the main problem is that I can't build a successful binary
from the
On 15/11/2011 10:53 AM, Dave Korn wrote:
On 09/11/2011 12:15, Edvardsen Kåre wrote:
This is again related to the failure of execution of a gfortran built
binary (cannot execute binary, see thread
http://cygwin.com/ml/cygwin/2011-11/msg00034.html )
In short, the main problem is that I can't
On 11/11/2011 12:29 PM, Ken Brown wrote:
On 11/11/2011 10:58 AM, Jesse Ziser wrote:
Hello,
Since attempting to upgrade from Cygwin 1.5 to 1.7, I'm having the
problem that attempting to run various programs results in a slew of
errors like the following:
1 [main] bash 4276
On Tue, Nov 15, 2011 at 04:04:16PM +0100, marco atzeri wrote:
On 11/14/2011 6:11 PM, Christopher Faylor wrote:
FYI, the last thing any developer wants to hear after a major code
change is a generic It's broke report with no details and no way to
duplicate the problem. A stack trace from a
First of all, I would like to warn some that this message may be a bit
lengthy.
I installed Cygwin 1.7.9-1 mainly for the purpose of compiling and trying
out THC-Hydra. I've managed to install some necessary dependencies, but
other are so troublesome I just can't deal with them.
The avalanche
On 11/15/2011 2:28 PM, viper_88 wrote:
The avalanche of my problems has started when I wanted to install
compat-libstdc++ 33-3.2.3. The installation failed due to the following
dependencies errors:
error: Failed dependencies:
/sbin/ldconfig is needed by compat-libstdc++-33-3.2.3-55.fc5
I have a Smalltalk application that looks for a shared Library which
contains C and FORTRAN routines. This shared library has been called
BIEsharedLib.so regardless of the platform we run on, Windows, Linux or
originally Unix. On the Windows boxes we have used the Intel compilers
successfully for
I've accidentally updated Subversion to 1.7.x on Cygwin.
Is there a way to get an older package of Subversion installed?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:
On 11/15/2011 3:31 PM, Jim Harsh wrote:
[snip]
I searched the archive and that's where I got the idea to use the -W1,
--out-implib,BIEsharedLib.dll.a switch to get a .so vs a .dll file.
The option is a lowercase L not a 1, i.e. -Wl,-out-implib,...
(you can use one dash for double dashed
On 11/15/2011 4:31 PM, Jim Harsh wrote:
COLLECT_GCC_OPTIONS='-v' '-shared' '-W1,--out-implib,BIEsharedLib.dll.a'
'-o' '/cygdrive/c/BIE_work/ver747Dev/BIEsharedLib.so' '-shared-libgcc'
'-mtune=generic' '-march=i686'
/usr/lib/gcc/i686-pc-cygwin/4.5.3/collect2.exe --wrap _Znwj --wrap _Znaj
On 11/15/2011 4:31 PM, Jim Harsh wrote:
If you're depending on a specific C++ mangling to match what you've put
in your build, bear in mind that no g++ will match any Visual Studio
compatible C++ compiler. Normal procedure is to use extern C on the
C++ side and iso_c_interop on the Fortran
Le 10/11/2011 02:05, Andrey Repin a écrit :
Greetings, Cyrille Lefevre!
Would defining $SHELL at a system level solve your issue?
well, I'm not the one who is having the problem,
I'm the one who is trying to help to solve the issue... :-)
Regards,
Cyrille Lefevre
--
Le 08/11/2011 00:25, Cyrille Lefevre a écrit :
Hi,
are you working on these issues ?
thanks in advance.
Le 04/11/2011 21:22, David Sastre a écrit :
On Fri, Nov 04, 2011 at 06:05:39AM +0100, Cyrille Lefevre wrote:
the base-file maintainer has been BCC'ed to add the export SHELL to
the
On 15/11/2011 16:20, Ryan Johnson wrote:
On 15/11/2011 10:53 AM, Dave Korn wrote:
On 09/11/2011 12:15, Edvardsen Kåre wrote:
In short, the main problem is that I can't build a successful binary
from the FLEXPART fortran code
FLEXPART is one of those huge number-crunching Fortran programs
21 matches
Mail list logo
