4.4/include/c++
into $INSTALL/lib/gcc/i686-pc-cygwin/3.4.4/include,
to cp /usr/lib/gcc/i686-pc-cygwin/3.4.4/include/lib{std,sup}c++.{a,la}
into $INSTALL/i686-pc-cygwin/lib and to edit the .la
files to refer to my $INSTALL directory (for -L options
in dependencies and the libdir
age and let the compilation continue?
Is there something else I am missing in my distro (of course, I've
patched the sources using the distributed file).
Thanks for any help,
Daniel Villeneuve
Kronos
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports:
n attachment here.
check
Description: Binary data
Let me know if more information is needed.
Thanks for your time,
--
Daniel Villeneuve
AD OPT Technologies Inc.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Hi,
I'm still working on the problem related to using execvp to
call a program through a relative symbolic link.
I have installed the latest release of cygwin (1.3.22-1)
available today.
I use the following test environment:
- create a directory d2 on a network share, containing two programs;
-
works in all cases (it seems that bash expands the
symlink before calling execXX);
- changing the call to ./callfoo to
does not work because perl call execvp directly.
I have searched cygwin archives and google about "exec symlink
cygwin" and found nothing really illuminating
5 matches
Mail list logo