Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
AW: [cdt-dev] CDT problems after upgrading to Cygwin 1.7

Hi Andrew,
 
> Which CDT do you use?
6.0.0?
 
There was a bug 218444 where the problem was solved by using sh at least for scanner discovery (toolchain level).
Oh. Yes, that exactly describes the problem and the solution I was thinking of.
 
You can also set that manually in Discovery Options project properties.
Unfortunately, I could not. In my version of CDT, I can only set the "invocation command" but not the options.
Maybe this has also been alredy changed in CDT since then.
 
 
Nils

Von: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Andrew Gvozdev
Gesendet: Freitag, 8. Januar 2010 17:33
An: CDT General developers list.
Betreff: Re: [cdt-dev] CDT problems after upgrading to Cygwin 1.7

Which CDT do you use? There was a bug 218444 where the problem was solved by using sh at least for scanner discovery (toolchain level). You can also set that manually in Discovery Options project properties.

Thanks,
Andrew

On Fri, Jan 8, 2010 at 10:50 AM, Hagge, Nils <nils.hagge@xxxxxxxxxxx> wrote:
Hi Andrew,
 
I think I am close to finding a solution. I just identified the problem (also thanks to Michael Luber):
 
The gcc.exe in Cygwin 1.7 is no longer a real "exe" file. It is a symbolic link that can only be
handled by a cygwin shell. The real exe is now called "gcc-3.exe". Unfortunately, CDT calls "gcc.exe"
directly when from its scannerInfoProviders. The creation of the Process object fails and thus no
path information (defines, etc.) can be gathered.
 
Compiling still works because then gcc is called indirectedly by the created makefile which in turn
starts a sh.exe to execute gcc and thus knows how to handle the symbolic link.
 
>  Also, what problem did you have with sh.exe? Did you delete it accidentally?
 
setup.exe deleted it. I learned from www.cygwin.com that sh.exe originally was a copy of/a link to ash.exe.
In cygwin 1.7 it is derived from bash.exe.
 
setup.exe ran a postinstall script to perform this modification. But since this script was executed with one
the shells (the old or the new one, I dont remember anymore) the file was blocked by the running process
and could not successfully replaced. Reinstalling the shells package solved the problem.
 
Mit freundlichen Grüßen / Best regards

Dr. Nils Hagge

Projektleiter Vorfeld

Siemens AG
Industry Sector, I IA&DT ATS 13
Telefon +49 911 895-3484
Telefax +49 911 895-153484
mailto:nils.hagge@xxxxxxxxxxx
http://www.siemens.com/automation


Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Gerhard Cromme
Managing Board: Peter Loescher, Chairman, President and Chief Executive Officer;
Wolfgang Dehen, Heinrich Hiesinger, Joe Kaeser, Jim Reid-Anderson, Hermann Requardt,
Siegfried Russwurm, Peter Y. Solmssen
Registered offices: Berlin and Munich;
Commercial registries: Berlin Charlottenburg, HRB 12300, Munich, HRB 6684
WEEE-Reg.-No. DE 23691322
 


Von: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Andrew Gvozdev
Gesendet: Freitag, 8. Januar 2010 15:15
An: CDT General developers list.
Betreff: Re: [cdt-dev] CDT problems after upgrading to Cygwin 1.7

Hi Nils,
What kind of project are you creating and what toolchain? Is it Makefile Project?

Also, what problem did you have with sh.exe? Did you delete it accidentally?

Thanks,
Andrew

On Fri, Jan 8, 2010 at 5:17 AM, Hagge, Nils <nils.hagge@xxxxxxxxxxx> wrote:
Dear friends,
 
unfortunately I had to upgrade Cygwin and now I CDT does no longer work
correctly. I fixed some problems, but now I am stuck.
 
First problems was that sh.exe was deleted. This problem is fixed.
 
My cygwin setup looks as follows.
 
$ cat /etc/setup/installed.db
INSTALLED.DB 2
alternatives alternatives-1.3.30c-10.tar.bz2 0
base-cygwin base-cygwin-2.1-1.tar.bz2 0
base-files base-files-3.9-3.tar.bz2 0
base-passwd base-passwd-3.1-1.tar.bz2 0
bash bash-3.2.49-23.tar.bz2 0
binutils binutils-2.19.51-1.tar.bz2 0
bzip2 bzip2-1.0.5-10.tar.bz2 0
coreutils coreutils-7.0-2.tar.bz2 0
cppunit cppunit-1.12.0-1.tar.bz2 0
cygutils cygutils-1.4.2-1.tar.bz2 0
cygwin cygwin-1.7.1-1.tar.bz2 0
cygwin-doc cygwin-doc-1.5-1.tar.bz2 0
dash dash-0.5.5.1-2.tar.bz2 0
editrights editrights-1.01-2.tar.bz2 0
findutils findutils-4.5.5-1.tar.bz2 0
gawk gawk-3.1.7-1.tar.bz2 0
gcc-core gcc-core-3.4.4-999.tar.bz2 0
gcc-g++ gcc-g++-3.4.4-999.tar.bz2 0
gcc-java gcc-java-3.4.4-999.tar.bz2 0
gcc-mingw-core gcc-mingw-core-20050522-1.tar.bz2 0
gcc-mingw-g++ gcc-mingw-g++-20050522-1.tar.bz2 0
gcc-mingw-java gcc-mingw-java-20050522-1.tar.bz2 0
gdb gdb-6.8-2.tar.bz2 0
gettext gettext-0.17-11.tar.bz2 0
grep grep-2.5.4-2.tar.bz2 0
groff groff-1.19.2-2.tar.bz2 0
gzip gzip-1.3.12-2.tar.bz2 0
ipc-utils ipc-utils-1.0-1.tar.bz2 0
less less-429-1.tar.bz2 0
libbz2_1 libbz2_1-1.0.5-10.tar.bz2 0
libgcc1 libgcc1-4.3.4-3.tar.bz2 0
libgmp3 libgmp3-4.3.1-3.tar.bz2 0
libiconv2 libiconv2-1.13.1-1.tar.bz2 0
libintl3 libintl3-0.14.5-1.tar.bz2 0
libintl8 libintl8-0.17-11.tar.bz2 0
libncurses8 libncurses8-5.5-10.tar.bz2 0
libncurses9 libncurses9-5.7-16.tar.bz2 0
libpcre0 libpcre0-8.00-1.tar.bz2 0
libpopt0 libpopt0-1.6.4-4.tar.bz2 0
libreadline7 libreadline7-6.0.3-2.tar.bz2 0
libstdc++6 libstdc++6-4.3.4-3.tar.bz2 0
login login-1.10-10.tar.bz2 0
make make-3.81-2.tar.bz2 0
man man-1.6e-1.tar.bz2 0
mingw-runtime mingw-runtime-3.17-1.tar.bz2 0
rebase rebase-3.0.1-1.tar.bz2 0
run run-1.1.12-11.tar.bz2 0
sed sed-4.1.5-2.tar.bz2 0
tar tar-1.22-1.tar.bz2 0
tcltk tcltk-20080420-1.tar.bz2 0
terminfo terminfo-5.7_20091114-13.tar.bz2 0
terminfo0 terminfo0-5.5_20061104-11.tar.bz2 0
texinfo texinfo-4.13-3.tar.bz2 0
tzcode tzcode-2009k-1.tar.bz2 0
w32api w32api-3.14-1.tar.bz2 0
which which-2.20-2.tar.bz2 0
zlib zlib-1.2.3-10.tar.bz2 0
zlib-devel zlib-devel-1.2.3-10.tar.bz2 0
zlib0 zlib0-1.2.3-10.tar.bz2 0
_update-info-dir _update-info-dir-00843-1.tar.bz2 0
 
From a previous question from Markus on 2009-01-31 I learned that
a package named "gcc" should be installed. I only have gcc-core and do not
know how to get just gcc. Maybe I am looking at a false trace, since when
I type "gcc" into a bash, gcc is found.
 
CDT can compile C source, but CDT cannot find/resolve standard include paths anymore!
 
Please help....
 
 
 
Mit freundlichen Grüßen / Best regards

Dr. Nils Hagge

Projektleiter Vorfeld

Siemens AGIndustry Sector, I IA&DT ATS 13
Telefon +49 911 895-3484
Telefax +49 911 895-153484
mailto:nils.hagge@xxxxxxxxxxx
http://www.siemens.com/automation


Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Gerhard Cromme
Managing Board: Peter Loescher, Chairman, President and Chief Executive Officer;
Wolfgang Dehen, Heinrich Hiesinger, Joe Kaeser, Jim Reid-Anderson, Hermann Requardt,
Siegfried Russwurm, Peter Y. Solmssen
Registered offices: Berlin and Munich;
Commercial registries: Berlin Charlottenburg, HRB 12300, Munich, HRB 6684
WEEE-Reg.-No. DE 23691322
 

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev



_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev



Back to the top