Menu
▾
▴
interix-wgcc-developer — Developer List
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
(15) |
Oct
(15) |
Nov
(6) |
Dec
(5) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(1) |
Feb
(2) |
Mar
(1) |
Apr
(3) |
May
(1) |
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Yahoo! G. <confirm-s2-se4s2xhfmzabxjsvhcdsyobxycc0daca-interix-wgcc-developer=<lis...@ya...> - 2009-02-15 18:25:28
|
Hello int...@li..., We have received your request to join the payal_nigam2007 group hosted by Yahoo! Groups, a free, easy-to-use community service. This request will expire in 7 days. TO BECOME A MEMBER OF THE GROUP: 1) Go to the Yahoo! Groups site by clicking on this link: http://groups.yahoo.com/i?i=se4s2xhfmzabxjsvhcdsyobxycc0daca&e=interix-wgcc-developer%40lists%2Esourceforge%2Enet (If clicking doesn't work, "Cut" and "Paste" the line above into your Web browser's address bar.) -OR- 2) REPLY to this email by clicking "Reply" and then "Send" in your email program If you did not request, or do not want, a membership in the payal_nigam2007 group, please accept our apologies and ignore this message. Regards, Yahoo! Groups Customer Care Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ |
|
From: <adv...@gm...> - 2008-02-25 02:56:48
|
Dear Manager, Happy New 2008 year!Hope you evry success and properous in 2008! Today,I've a great good news to you,that is,most our CCTV cameras are updated in Software program and details now,however,the pricing we can offer now is greatly more favourable now. Those model pricing reduced greatly are includig belowed:(Pls do take well this opportunity,as the need is day to day) 1)AD-DVR15CB Color series [Wired mini spy system,composed by 15x15mm button camera and mini portable AV Recorder] 2)AD-IR1180CW Color series [1/3" Sony CCD,420/480/520TVL Optional,0Lux(LED on),112 LEDs,6-15mm lens,80-100m Visible distance. DC12V] If be of any interests,pls don't hesitate to contact me,then I'll send you our favourable price to you after your specific inquiry. Thanks for your kind attention.Awaiting your reply here. Best regards, Shirley Shenzhen Beyond Tech Co.,Ltd. http://www.hiccd.com.cn Tel: 86-755-82660165 Fax: 86-755-82660170 Email:adv...@gm.../by...@gm... MSN: Shi...@16... Skype:Shirley19870118 |
|
From: Elmar R. <elm...@gm...> - 2007-08-15 09:34:51
|
-- Flora Lau wrote: > Hello all, > My experience in these things is not so good so please excuse any > naivetm. What I would like to know is will wgcc allow me to build an > open source c++ project (containing Makefile, configure, configure.in > files etc) intended for gcc and then link , for instance a static > library thus built, to a MSVC++ (v8) project within VS? interix-wgcc is exactly for that purpose. wgcc implements gcc interface, but beneath it uses cl.exe to compile and link.exe for linking. Though with wgcc you get native win32 libs and executables. For building an opensource package you only to overwrite CC, CXX and LD to use wgcc instead of gcc. > Presently I > have attempted to link gcc built static libraries to a MSVC++ project > but this has failed due to compiler incompatibilities (different name > mangling etc between compilers). To get around this problem I have > seen suggested that a C code interface between my MS project and any > gcc built libraries be created to handle any calls to the C++ code > within these libraries from MS project. With wgcc such stunts aren't necessary, because if you've build your package with wgcc you've got native win32 libs. Maybe you have to port some things in you opensource package though wgcc can compile the source. > Before I commence on such a > task unnecessarily, is the assumption in my question correct. My > perusal from the various internet chatter (wgcc, cccl, wcc, and > general) has created much confusion for me and I have not seen an > answer stated explicitly, for or against, to a question posed as I > have done. > > Any help is greatly appreciated, > > Flora L Elmar |
|
From: Flora L. <flo...@ya...> - 2007-08-14 11:35:42
|
Hello all,=0A=0AMy experience in these things is not so good so please excu= se any naivet=88m. What I would like to know is will wgcc allow me to build= an open source c++ project (containing Makefile, configure, configure.in f= iles etc) intended for gcc and then link , for instance a static library th= us built, to a MSVC++ (v8) project within VS? Presently I have attempted to= link gcc built static libraries to a MSVC++ project but this has failed du= e to compiler incompatibilities (different name mangling etc between compil= ers). To get around this problem I have seen suggested that a C code interf= ace between my MS project and any gcc built libraries be created to handle = any calls to the C++ code within these libraries from MS project. Before I = commence on such a task unnecessarily, is the assumption in my question cor= rect. My perusal from the various internet chatter (wgcc, cccl, wcc, and ge= neral) has created much confusion for me and I have not seen an answer stat= ed explicitly, for or against, to a question posed as I have done.=0A=0AAny h= elp is greatly appreciated,=0A=0AFlora L=0A=0A=0A=0A=0A =A8=CF=A5=CEYa= hoo! Mail =B5L=AD=AD=B9q=B6l=C0x=A6s=B6q=A1A=A5=CE=B1o=B7U=A6h=A1A=BD=E0=A7= A=B5L=AD=AD=C5=E5=B3=DF! =B8=D4=B1=A1=A5i=B0=D1=BE\http://hk.promo.yahoo.co= m/mail/loyalty072007/=0A=0A |
|
From: Duft M. <Mar...@sa...> - 2007-03-22 15:30:39
|
Hi! For anybody interested in this: Wgcc has been mentioned on http://www.linux-magazin.de/heft_abo/ausgaben/2007/02/projektekueche (german) as "GCC for Windows". Really cool! Cheers, Markus |
|
From: Erik de C. L. <mle...@me...> - 2007-02-13 00:42:26
|
Hi all, Is anyone using wgcc on win64 to build win64 binaries of code using autoconf/automake/libtool? Cheers, Erik -- +-----------------------------------------------------------+ Erik de Castro Lopo +-----------------------------------------------------------+ "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." --Brian Kernighan |
|
From: Michael H. <mic...@sa...> - 2006-12-18 16:30:34
|
On Mon, 2006-12-18 at 16:02 +0100, Francisco J. Royo Santas wrote: <snip> > I have even turned DEP off. <snip> > 3rd: > ---- > As M. Haubenwallner suggested, I tried downloading 'wgcc' but it din't > work for > cygwin as well. <snip> wgcc not running on cygwin currently is a known problem, although there is no known technical issue but just lack of resources. <snip> > What I did next was to download 'Microsoft Windows services for Unix' > and tried > to compile and run wgcc there but it was even funnier. After solving problems > like getting "Memory fault (core dumped)" for every single thing I > tried to do, > I tried to run "./configure" for wgcc and what I got (when compiling > conftest.cc, a simple main which has a "return 0" statement) was: > gcc: Internal error: Segmentation fault (program cc1plus) > Please submit a full bug report. > See <URL:http://gcc.gnu.org/bugs.html> for instructions. As you said above, did you have DEP also disabled when using Interix ? Interix-shipped gcc requires it to be disabled, at least for SFU 3.5. And which version of Windows and SFU do you use ? Windows 2000, XP: SFU 3.5 Windows 2003: SFU 3.5, but does not really work Windows 2003r2: SUA 5.2 (is a Windows component here) IMO we should continue wgcc/interix-specific discussion on interix-wgcc-developer list. /haubi/ -- Michael Haubenwallner SALOMON Automation GmbH Forschung & Entwicklung A-8114 Friesach bei Graz mailto:mic...@sa... http://www.salomon.at No HTML/MIME please, see http://expita.com/nomime.html |
|
From: Markus D. <mar...@ch...> - 2006-12-08 13:51:24
|
Hi! Yes you're right. Since wgcc uses cl.exe, it cannot compile gcc style inline asm. You will need to convert it to Microsoft style inline asm. Cheers, Markus _____ From: int...@li... [mailto:int...@li...] On Behalf Of fastreaming.com Sent: Donnerstag, 30. November 2006 09:28 To: int...@li... Subject: [wgcc-dev] Does wgcc recognize gcc inline asm? Dear: Does wgcc recognize gcc inline asm? IIRC. cl.exe failes to compile gcc inline asm, so wgcc is same Is it right? Thanks |
|
From: Duft M. <Mar...@sa...> - 2006-12-07 16:30:17
|
Hi! The yesterday-released version of wgcc (2.1.0) has a critical bug, making it crash whenever you pass certain options (like -O2) to it. This has been fixed in 2.1.1 which is available now from SF.net. Cheers, Markus |
|
From: Duft M. <Mar...@sa...> - 2006-12-06 16:56:33
|
Hi together! I'm proud to announce the 2.1.0 "stabilizing release" of wgcc. For more info read below. Cheers, Markus =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D wgcc is a cross-compiler tool primarily written for Microsoft's Interix. Its primary purpose is to produce native Windows binaries (internally using the Microsoft Tool chain), and to mimic the behaviour of the GNU compiler collection. This means that wgcc understands many of GCC's command line arguments, and in most cases delivers the same results as expected, sometimes manipulating the underlying tool's input and output. Even though wgcc was written for Interix only, it can be used on native Windows (without Interix), and other Systems, like Cygwin. The only restriction is that on Platforms other than Interix, only Windows style paths are understood. With the release of version 2.0.1 this changed. Now Cygwin too is able to convert paths correctly. On Interix (and now Cygwin) wgcc automatically converts UNIX style paths to Windows style ones (i.e. /wgcc to C:\SFU\wgcc). wgcc abstracts away lots of inconveniences that are introduced by building static libraries, shared libraries (DLL's) and executables with any possible combination of those three. When using wgcc both static and shared libraries behave exactly the same on Windows, and this makes tons of defines unnecessary. The only thing that still has to be done is to give all Data symbols (i.e. Variables) an import attribute (__declspec(dllimport)) when using them (i.e. in the library header files) in an executable. For a simple example take a look at the file tests/shared.test inside the wgcc distribution. Teh 2.1.0 release of wgcc is a "stabilizing" release, means that there are not many new features, but the existing code has been improved. Since there was some feedback from 2.0.5 (finally) i could find some memory leaks and performance hits. Especially the performance of the 2.1.0 release has been improved a lot (by about factor 2 to 3, means it's up to three times faster). This release of wgcc has a fairly small memory footprint which should be in most cases under 10 MB. Also if the configuration is tweaked a little (turn dependency tracking off) wgcc takes just between 70 and 150 ms (!) for all its work (excluding external tasks like the compiler). This time was taken while compiling with a fairly long command line under full (90 - 100%) CPU load. Libtool has been removed from the wgcc and ucl packages, since it would be an overhead. This only means that building wgcc is a little faster now, and has no influence on the libtool patches shipped from the wgcc page. To continue improving wgcc and pxwc packages, we now need your help in testing them. Please download wgcc and try to compile your software using it. If something goes wrong please contact mduft or open an issue using the Sourceforge Tracker at http://sourceforge.net/tracker/?group_id=3D158081&atid=3D806404, or ask = your questions at the forums at http://sourceforge.net/forum/?group_id=3D158081. You can browse the Subversion Repository here: http://svn.sourceforge.net/viewvc/interix-wgcc/trunks/ Documentation can be found here: http://sourceforge.net/project/showfiles.php?group_id=3D158081&package_id= =3D 203917&release_id=3D446943 Source Packages can be found here: http://sourceforge.net/project/showfiles.php?group_id=3D158081&package_id= =3D 177049&release_id=3D445894 The Patch for Libtool can be found here: http://sourceforge.net/project/showfiles.php?group_id=3D158081&package_id= =3D 196163&release_id=3D446510 The PXWC library can be found here: http://sourceforge.net/project/showfiles.php?group_id=3D158081&package_id= =3D 195309&release_id=3D449425 |
|
From: Duft M. <Mar...@sa...> - 2006-12-05 11:22:48
|
Hi!
Looks like wgcc fails recognizing your instance of visual studio during
configure.
Some things are interesting here:
* are you using Interix or Cygwin?
* where is your MSVC installed?
* where is (if you have it) your platform SDK?
* the config.log file
* the ${prefix}/etc/.wgccrc file
Maybe you could send me those infos, that would help. ;o)
You may also just have a look at the .wgccrc file (should be in the dir
where you gmake check)
There should be some lines like
Paths.c =3D ...
Paths.c +=3D ...
Paths.c++ =3D ...
Paths.c++ +=3D ...
Paths.linker =3D ...
Paths.linker +=3D ...
These should *each* include the prefix for which wgcc was configured,
and any visual studio directory that is neccessary.
Hope this help!
Cheers, Markus
Aleksey Cheusov <> wrote:
> While installing wgcc I have the following.
> MSVC version is 2005 Express Edition.
>=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> 0 wgcc-2.0.5>make check
> Making check in confix-admin
> Making check in coff
> Making check in tests
> make check-TESTS
> error : execution of task seemed to fail, return code 32512 fatal :
> assembler queue didn't complete, cannot continue compilation failed.
> FAIL: assembler.test=20
> linking failed.
> FAIL: c.test
> linking failed.
> FAIL: cpp.test
> [ checking c ]
> shared library link failed
> FAIL: explicit-import.test
> [ checking c ]
> shared library link failed
> FAIL: export-all.test
> [ checking c ]
> shared library link failed
> FAIL: implicit-import.test
> [ checking c ]
> warning: wrapper header set but not available!
> linking failed.
> FAIL: profiler.test
> [ checking c ]
> shared library link failed
> FAIL: shared.test
> [ checking c ]
> linking failed.
> FAIL: static.test
> SKIP: stdcxx.test
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> 9 of 9 tests failed
> (1 tests were not run)
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> *** Error code 1
>=20
> Stop.
> *** Error code 1
>=20
> Stop.
> *** Error code 1
>=20
> Stop.
> 0 wgcc-2.0.5>cl.exe /? | head -n 2
> Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.42
> for 80x86 Copyright (C) Microsoft Corporation. All rights reserved.
> 0 wgcc-2.0.5>uname -a=20
> Interix syn-fs 3.5 SP-8.0.1969.1 x86 AMD Athlon/Duron 0 wgcc-2.0.5>
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20
>=20
> After 'make install' it to /opt/wgcc
> (It was configured configure with --prefix /opt/wgcc).
> I updated PATH and LD_LIBRARY_PATH.
>=20
> Then, I have the following trouble with real C++ project.
> "fatal : cannot execute assembler task for generator."
>=20
> Does wgcc work with MSVC++ 2005 Express Edition?
|
|
From: Aleksey C. <vl...@gm...> - 2006-11-30 16:32:39
|
While installing wgcc I have the following. MSVC version is 2005 Express Edition. =================================================================== 0 wgcc-2.0.5>make check Making check in confix-admin Making check in coff Making check in tests make check-TESTS error : execution of task seemed to fail, return code 32512 fatal : assembler queue didn't complete, cannot continue compilation failed. FAIL: assembler.test linking failed. FAIL: c.test linking failed. FAIL: cpp.test [ checking c ] shared library link failed FAIL: explicit-import.test [ checking c ] shared library link failed FAIL: export-all.test [ checking c ] shared library link failed FAIL: implicit-import.test [ checking c ] warning: wrapper header set but not available! linking failed. FAIL: profiler.test [ checking c ] shared library link failed FAIL: shared.test [ checking c ] linking failed. FAIL: static.test SKIP: stdcxx.test ====================== 9 of 9 tests failed (1 tests were not run) ====================== *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. 0 wgcc-2.0.5>cl.exe /? | head -n 2 Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.42 for 80x86 Copyright (C) Microsoft Corporation. All rights reserved. 0 wgcc-2.0.5>uname -a Interix syn-fs 3.5 SP-8.0.1969.1 x86 AMD Athlon/Duron 0 wgcc-2.0.5> =================================================================== After 'make install' it to /opt/wgcc (It was configured configure with --prefix /opt/wgcc). I updated PATH and LD_LIBRARY_PATH. Then, I have the following trouble with real C++ project. "fatal : cannot execute assembler task for generator." Does wgcc work with MSVC++ 2005 Express Edition? -- Best regards, Aleksey Cheusov. |
|
From: fastreaming.com <de...@fa...> - 2006-11-30 08:28:20
|
Dear: Does wgcc recognize gcc inline asm? IIRC. cl.exe failes to compile gcc inline asm, so wgcc is same Is it right? Thanks |
|
From: Duft M. <Mar...@sa...> - 2006-11-29 13:18:07
|
I am very proud to announce the release 2.0.5 of wgcc. Maybe there is some interest. It is a very much improved version compared to the previous ones. List of changes below. Cheers, Markus wgcc is a cross-compiler tool primarily written for Microsoft's Interix. Its primary purpose is to produce native Windows binaries (internally using the Microsoft Tool chain), and to mimic the behaviour of the GNU compiler collection. This means that wgcc understands many of GCC's command line arguments, and in most cases delivers the same results as expected, sometimes manipulating the underlying tool's input and output. Even though wgcc was written for Interix only, it can be used on native Windows (without Interix), and other Systems, like Cygwin. The only restriction is that on Platforms other than Interix, only Windows style paths are understood. With the release of version 2.0.1 this changed. Now Cygwin too is able to convert paths correctly. On Interix (and now Cygwin) wgcc automatically converts UNIX style paths to Windows style ones (i.e. /wgcc to C:\SFU\wgcc). wgcc abstracts away lots of inconveniences that are introduced by building static libraries, shared libraries (DLL's) and executables with any possible combination of those three. When using wgcc both static and shared libraries behave exactly the same on Windows, and this makes tons of defines unnecessary. The only thing that still has to be done is to give all Data symbols (i.e. Variables) an import attribute (__declspec(dllimport)) when using them (i.e. in the library header files) in an executable. For a simple example take a look at the file tests/shared.test inside the wgcc distribution. This release includes some really big, heavy and *cool* new things: Instead if the very slow and memory intensive dumpbin.exe, wgcc now includes a little library (libcoff) that does all the object and library reading. This increases linking performance by about the factor three. Additionally when used in a really big link, wgcc does not anymore need up to 800 MB memory, but now uses constant low amounts like 5 to 10 MB. There was a spelling error in the default .wgccrc file. "no-import-filter" should have been "import-filter". This feature now should work again. All the warnings from dependency tracking have been move to level s3 (verbose). So Dependency tracking is quiet now. Configuration files are now loaded in a slightly different way. The old behaviour was to check a number of locations, and load each (!) file, if it was there. The new one checks the same locations, but then only loads the one (!) file that takes the highest precedence. The only exception is, that configuration files that are specified with the "-config" option get loaded over any already loaded file. Also the rules for file lookup have been changed. Now first the Environment variable WGCC_CONFIG is checked for a configuration file path, then the current directory, then the "etc" directory in the wgcc prefix, then the directory where wgcc resides. The ln utility was broken in the last release, this has been fixed. The order of include directories was fixed, and now the options from the command line take precedence over any directories from the environment. Some tools that may generate parts of the command line that is passed to wgcc may include "\r" since win32 executables are used in this processes. Wgcc now handles such things, and does not warn anymore, about being unable to match an empty option. Microsoft's compiler v8 uses 64bit time_t's by default (even on 32bit systems, wgcc does not yet support 64bit). Wgcc provides the option to revert to 32bit time_t's (which is the wgcc default) by setting the "32bit-time_t" configuration directive. The very time consuming runtime indicator checks may now be (and are by default) disabled to speed up linking in shared libraries. However if you plan to use the memory profiling feature from pxwc, you should enable this option (using the "search-indicator" configuration directive). Some simple profiling has been implemented which takes times of the main tasks. This is only available when building wgcc with gcc, not when using the native win32 build with Visual Studio. To see the output, set the debug level to s3. Future versions may include a separate debug level to only include profiling output. The "-static" option has been fixed in this release to behave like the gcc counterpart, which refuses to link in shared libraries. To continue improving wgcc and pxwc packages, we now need your help in testing them. Please download wgcc and try to compile your software using it. If something goes wrong please contact mduft or open an issue using the Sourceforge Tracker at http://sourceforge.net/tracker/?group_id=3D158081&atid=3D806404, or ask = your questions at the forums at http://sourceforge.net/forum/?group_id=3D158081. You can browse the Subversion Repository here: http://svn.sourceforge.net/viewvc/interix-wgcc/trunks/ Documentation can be found here: http://sourceforge.net/project/showfiles.php?group_id=3D158081&package_id= =3D 203917&release_id=3D446943 Source Packages can be found here: http://sourceforge.net/project/showfiles.php?group_id=3D158081&package_id= =3D 177049&release_id=3D445894 The Patch for Libtool can be found here: http://sourceforge.net/project/showfiles.php?group_id=3D158081&package_id= =3D 196163&release_id=3D446510 The PXWC library can be found here: http://sourceforge.net/project/showfiles.php?group_id=3D158081&package_id= =3D 195309&release_id=3D449425 |
|
From: Duft M. <Mar...@sa...> - 2006-11-06 08:17:18
|
For future use forwarded to mailing list.
Note: as seen in here the VC98 (VC6) ml.exe does not work with wgcc.
Cheers, Markus
-----Original Message-----
From: Steve Bardwell [mailto:SBa...@lb...]=20
Sent: Sunday, November 05, 2006 4:10 PM
To: Duft Markus
Subject: RE: Problems installing wgcc
Markus -
OK. I am understanding more of this -- one must use the Windows APIs to
do anything!
I replaced my Unix socket commands:
'read()' with 'recv()'
'write()' with 'send()'
and I get errors using WSAGetLastError() and it is now working!!!!
This is enough so that I can code the programs I need as Win32
executables.
Many thanks for your help and for your compiler! I am happy.
Steve
=20
-----Original Message-----
From: Duft Markus [mailto:Mar...@sa...]
Sent: Friday, November 03, 2006 10:21 AM
To: sba...@lb...
Subject: RE: Problems installing wgcc
Hi!
It now compiles ;o) differences in diff file, new version in attached
.c.new ;o)
The thing is that lot's of signals are not available on windows, and
winsock uses slightly different names for some defines. Additionally
you will have to reimplement mygethostname somehow for windows, but
that should not be a big problem, consult msdn here.
You really should fix the remaining warnings ;o)
Cheers, Markus=20
-----Original Message-----
From: Steve Bardwell [mailto:sba...@lb...]
Sent: Friday, November 03, 2006 3:46 PM
To: Duft Markus
Subject: RE: Problems installing wgcc
Getting closer!
I have simplified the source (attached) with only one local Include
file.
What are your suggestions for the following output from wgcc:
$ wgcc -o test_ipsock test_ipsock.c
error : execution of task seemed to fail, return code 512
C:\SFU\tmp\wgcc\installed\bin\test_ipsock.c(46) : error C2373:
'gethostbyname' : redefinition; different type modifiers
V:\Vc7\PlatformSDK\Include\WinSock2.h(2120) : see declaration of
'gethostbyname'
C:\SFU\tmp\wgcc\installed\bin\test_ipsock.c(157) : error C2065:
'SIGALRM' :
undeclared identifier
C:\SFU\tmp\wgcc\installed\bin\test_ipsock.c(316) : error C2065:
'ECONNREFUSED' : undeclared identifier
C:\SFU\tmp\wgcc\installed\bin\test_ipsock.c(350) : error C2079: 'utsn'
uses undefined struct 'utsname'
C:\SFU\tmp\wgcc\installed\bin\test_ipsock.c(362) : error C2224: left of
'.nodename' must have struct/union type
C:\SFU\tmp\wgcc\installed\bin\test_ipsock.c(362) : error C2198: 'strcpy'
:
too few arguments for call through pointer-to-fun ction fatal :
compiler queue didn't complete, cannot continue
Steve
=20
-----Original Message-----
From: Duft Markus [mailto:Mar...@sa...]
Sent: Friday, November 03, 2006 9:11 AM
To: sba...@lb...
Subject: RE: Problems installing wgcc
Hey!
Cool ;o)
Just ifdef out the include for netdb.h, you won't need it on windows i
think.
The thing is, that wgcc uses the include directories from cl.exe, and
not /usr/include. This is the reason for pxwc ;o) it abstracts away lots
of issues with the cl.exe includes.
The /usr/include files would require the interix libc to be used, and
that is against the concept of wgcc -> it's purpose is to create native
executables with the native runtime, so it's all windows ;o)
Cheers, Markus=20
-----Original Message-----
From: Steve Bardwell [mailto:sba...@lb...]
Sent: Friday, November 03, 2006 2:52 PM
To: Duft Markus
Subject: RE: Problems installing wgcc
Markus -
It now passes all the tests!!
Since I have you on the line, I will keep asking questions until you get
tired! =20
So, to compile my test program, I am running:
Wgcc -o test_ipsock test_ipsock.c
I now get the error:
$ wgcc -o test_ipsock test_ipsock.c
error : execution of task seemed to fail, return code 512
C:\SFU\tmp\wgcc\installed\bin\test_ipsock.c(16) : fatal error C1083:
Cannot open include file: 'netdb.h': No such file or directory fatal :
compiler queue didn't complete, cannot continue
Of course, there is 'netdb.h' in /usr/include.
Steve
-----Original Message-----
From: Duft Markus [mailto:Mar...@sa...]
Sent: Friday, November 03, 2006 8:33 AM
To: sba...@lb...
Subject: RE: Problems installing wgcc
Hi!
Sorry, i forgot: you will have to re configure for the vs checks to run
again, so wgcc gets the correct visual studio. After that please edit
.wgccrc in your build directory again to have debuglevel f3.
Hope it works then ;o)
Cheers, markus=20
-----Original Message-----
From: Steve Bardwell [mailto:sba...@lb...]
Sent: Friday, November 03, 2006 2:27 PM
To: Duft Markus
Subject: FW: Problems installing wgcc
OK. I also have Visual Studio .NET 2003 installed. I changed the
INTERIX_COMPILEDIR environment variable to point to it (instead of my
old VC98).
I ran the following commands:
make clean
make
make check
gmake check TESTS=3D"assembler.test"
I have attached the 'wgcc_debug.out'.=20
Steve
=20
-----Original Message-----
From: Duft Markus [mailto:Mar...@sa...]
Sent: Friday, November 03, 2006 7:28 AM
To: sba...@lb...
Subject: RE: Problems installing wgcc
Hey!
When looking again over your output i saw that you're using VC98... I
never tested anything with such an old version, so i'm not quite sure if
it's not a problem with wgcc/ml.exe versions...
Additionally there is no platform sdk in your configuration. This
doesn't matter for the tests, but you'll need it to compile your test
program you sent me. The wgcc configure script is very limited in
detecting platform sdk and compiler location, so you'll have to add
paths you allways need manually.
Cheers, Markus
-----Original Message-----
From: Steve Bardwell [mailto:sba...@lb...]
Sent: Friday, November 03, 2006 12:09 PM
To: Duft Markus
Subject: FW: Problems installing wgcc
=20
Markus -
Here are the two files created with the new debug level. I may have not
gotten the paths correctly set before running the tests, so I will run
these again if necessary.
Thanks again.
Steve
=20
-----Original Message-----
From: Duft Markus [mailto:Mar...@sa...]
Sent: Friday, November 03, 2006 1:52 AM
To: Steve Bardwell
Subject: RE: Problems installing wgcc
Hi!
Uff, sorry, i messed up something ;o) the tests use the non-installed
.wgccrc that is on your machine:
/dev/fs/T/wgcc/build.wgcc/.wgccrc
Set the debuglevel there please.
For the Windows Version: the versions that we (our company) support with
our software are:
Windows 2000 with Interix 3.5
Windows XP with Interix 3.5
Windows Server 2003 R2 (!) with Interix 5.2
The "R2" is very important ;o) The thing is that win server 2003 has
proven very unstable when building things. We build things on windows
server 2003 R2 and then copy the binaries to the 2003 SP[0|1] if we
really need them there.
There are some hotfixes available for which one would have to contact
microsoft to get them, and they _may_ fix _some_ problems, but i don't
think that it ever will work as good as the other combinations.
You may want to have a look at http://www.duh.org/interix/hotfixes.php .
I don't know if this is really legal, since microsoft request you to
contact them, but i googled this one out ;o)
For the test program. There for sure will be some minor issues when
porting to wgcc, since you're using the native compiler then, but as far
as the socket stuff is concerned, there is not a big problem there; try
with including WinSock2.h all functions should be there.
The bigger problem will be getopt i think, since there is no
implementation available. You may want to have a look at the attached
version of getopt which i modified (original from berkeley db) to
support even shared libraries (just some pointers more in this case) ;o)
Just try to compile it, i did, but i'm missing tons of headers, of
course ;o) I'll be glad helping you with any issue coming up...
Cheers, Markus
-----Original Message-----
From: Steve Bardwell [mailto:SBa...@lb...]
Sent: Thursday, November 02, 2006 6:54 PM
To: Duft Markus
Subject: RE: Problems installing wgcc
Markus -
Many thanks for your help. First, a couple of things:
1) I was incorrect about my machine. It is running W2003 WITHOUT SP1.
2) my ultimate goal is to produce Win32 executables for programs like
the attached source. Specifically, I am hoping to build programs that
use Unix network APIs (gethostbyname, etc). Will this work? I have been
using Cygwin to build a Win32 executable and am not happy with the
results.
I ran the two commands you requested after changing the preferences:
* gmake check TESTS=3D"assembler.test" -- the wgcc_debug.out is
attached.
* gmake check TESTS=3D"static.test" -- no wgcc_debug.out file was
created. The output to the screen from the command is attached
(g.out).
Thanks again for your help.
Steve
-----Original Message-----
From: Duft Markus [mailto:Mar...@sa...]
Sent: Thursday, November 02, 2006 1:10 AM
To: Steve Bardwell
Subject: RE: Problems installing wgcc
Hey!
I'm really proud to hear that some more people start using wgcc - or try
to ;o)
It doesn't look too bad in your case i think, even though in our company
Win2003SP1 is the only windows version thats left out because it's known
to make much trouble with interix. We had big problems compiling even
simple hallo world programs without crashes ... (not wgcc but gcc an
cl.exe directly)
But now for your problem: things look fine except for the two tests.
Maybe you could do the following:
Edit your ${prefix}/etc/.wgccrc so that: "color =3D 0" and "debuglevel =
=3D
f3".
Then run 'gmake check TESTS=3D"assembler.test"'. In the
${buildddir}/tests/.compile directory should be a file containing the
wgcc debug output: wgcc_debug.out
Move that file away somewhere and do a 'gmake check
TESTS=3D"static.test"'. Again move away the wgcc_debug.out, and mail me
those two files. I'll see what i can do.
I hope that i will release version 2.0.4 in a few days, maybe this will
help!
Cheers, Markus
-----Original Message-----
From: Steve Bardwell [mailto:SBa...@lb...]
Sent: Tuesday, October 31, 2006 4:24 PM
To: Duft Markus
Subject: Problems installing wgcc
Markus -
I am having trouble installing your 'wgcc' compiler. I have attached the
output from the make commands in each build directory.
My machine is running Windows 2003 (SP1) with Interix 3.5. I have been
using Interix and its compiler for a long time without any problems.
I appreciate any guidance you can give me.
Steve
+----------------------------------------------------------------+
| LBM SYSTEMS CORPORATION | Steven Bardwell, PhD |
| 145 Cherry Street | |
| New Canaan, CT 06840 | sba...@lb... |
| Fax: (203) 966-8242 | (203) 966-0661 |
| | |
| http://www.lbmsys.com |
+----------------------------------------------------------------+
|
|
From: maheshwari4vivaha m. <mah...@ya...> - 2006-11-02 05:10:56
|
mah...@ya... has invited you to join maheshwari4vivaha [http://groups.yahoo.com/group/maheshwari4vivaha/] on Yahoo! Groups, the best way to discover and share information and advice with others. All for free. A personal invitation from mah...@ya...: Welcome to the Maheshwari Matrimonial group at yahoo. Dear sir or Madam we are please to inform you that you can see here over 15,000 matrimonial bio-data of bride and groom of different Maheshwari section.If you or your relatives are looking for a Match or life partner than plz visit the site. www.maheshwary.net Registration free here join from the option given below Join group. See for yourself why millions of people are members of Yahoo! Groups. But hurry. This invitation expires in 30 days. Join this group: http://groups.yahoo.com/i?i=ai68gX9Wc6TkAMtPuWCj9ZUbYSk&e=interix-wgcc-developer%40lists%2Esourceforge%2Enet ------------------------------------------------------------------------ Yahoo! Groups is a free service that allows you to stay in touch with friends and family or meet new people who share your interests. Yahoo! Groups values your privacy. It is a violation of our service rules for Groups members to abuse this invitation feature. If you feel this has happened, please notify us: http://help.yahoo.com/help/us/groups/abuse/index.html You may also change your email preferences to stop receiving group invitations in the future. To do so, please go here: http://groups.yahoo.com/s?tag=dggssigI47LYV17no4t76mrY5Tz3iansmNad030X6KYZC_X2WpoFiVq_x4gNi4XKi3Wvy7PA_IxNHRnhe61mxA3TJ3fBX8TxHnCE_f2XU8HuDEcujZ0 Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/ |
|
From: Duft M. <Mar...@sa...> - 2006-10-24 13:41:47
|
No, i don't see any use in it right now. Cheers, Markus -----Original Message----- From: Jerker B=E4ck [mailto:jer...@ho...]=20 Sent: Tuesday, October 24, 2006 1:40 PM To: Duft Markus Subject: RE: [wgcc-dev] Apache stdcxx and STL in general > This makes it impossible to build wgcc using stdcxx, since wgcc is a=20 > gcc built executable. Yes, since SUA/SFU gcc has it's own STL, I get that But you made no attempt on a stdcxx build for Interix? |
|
From: Duft M. <Mar...@sa...> - 2006-10-24 11:20:44
|
I built stdcxx using the MS project files with the regular cl.exe build. = Since wgcc's primary goal (at the moment) is building native windows = binaries, not interix one's, the stdcxx library needs to be a native = build to be included in every wgcc-built binary. This makes it = impossible to build wgcc using stdcxx, since wgcc is a gcc built = executable. Wgcc is capable of automatically including stdcxx in every build, but = there are some things to do to make him do so. Have a look at the manual = pdf for some explanation. Cheers, Markus -----Original Message----- From: int...@li... = [mailto:int...@li...] On Behalf = Of Jerker B=E4ck Sent: Tuesday, October 24, 2006 12:29 PM To: int...@li... Subject: [wgcc-dev] Apache stdcxx and STL in general Marcus,=20 Apache stdcxx (Rouge Wave donation) is mentioned in the source. Have you done an Interix build of stdcxx or an attempt to build? In that case, SFU or SUA? What compiler and which build tool? I'm particularly interested in a MS compiler Interix build. Have you done an stdcxx build of wgcc? Have you made any changes/defines to the source? In that case, have you = reported these to the stdcxx dev team? I did an Interix SUA build with cl.exe using the GNUmakefile tools in = January. I based my config file on the Intel Linux compiler config file = and SUA cc. As I remember, it was a great deal of work to get it going, = specifically at the later build processes. I wasn't really satisfied = with the result though. Sadly I lost the whole thing when my RAID was = broken later that spring.=20 regards Jerker -------------------------------------------------------------------------= Using Tomcat but need to do more? Need to support web services, = security? Get stuff done quickly with pre-integrated technology to make your job = easier Download IBM WebSphere Application Server v.1.0.1 based on Apache = Geronimo http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D= 121642 _______________________________________________ Interix-wgcc-developer mailing list Int...@li... https://lists.sourceforge.net/lists/listinfo/interix-wgcc-developer |
|
From: <jer...@ho...> - 2006-10-24 10:31:18
|
Marcus, Apache stdcxx (Rouge Wave donation) is mentioned in the source. Have you done an Interix build of stdcxx or an attempt to build? In that case, SFU or SUA? What compiler and which build tool? I'm particularly interested in a MS compiler Interix build. Have you done an stdcxx build of wgcc? Have you made any changes/defines to the source? In that case, have you reported these to the stdcxx dev team? I did an Interix SUA build with cl.exe using the GNUmakefile tools in January. I based my config file on the Intel Linux compiler config file and SUA cc. As I remember, it was a great deal of work to get it going, specifically at the later build processes. I wasn't really satisfied with the result though. Sadly I lost the whole thing when my RAID was broken later that spring. regards Jerker |
|
From: Duft M. <Mar...@sa...> - 2006-10-19 12:15:35
|
Cool! ;o)
It just came into my mind, that the environment stuff additionally uses =
a fixed buffer (4096 chars) somewhere. This is fixed in the next version =
of wgcc, but you should have the old sources...
So wgcc now works fine with a cc build?
Cheers, Markus=20
-----Original Message-----
From: Jerker B=E4ck [mailto:jer...@ho...]=20
Sent: Thursday, October 19, 2006 1:44 PM
To: int...@li...
Cc: Duft Markus
Subject: BUG - POSIX build
I finally got the posix debugger working - yess!
And finally found the bug in wgcc preventing the MS build.
The current wgcc posix build will not even make it to main(). It throws =
an exception during construction of the context instance of class =
Context located in Context.cpp(700):
Context::Context()
...
more exactly here:
paths.c =3D Environment::getPaths(COMPILER_C);
=3D> stop - stack buffer overrun.
The output looks like this:
---------------------------------------------------
*** A stack buffer overrun occurred in ?=01:
This is usually the result of a memory copy to a local buffer or =
structure where the size is not properly calculated/checked.
If this bug ends up in the shipping product, it could be a severe =
security hole.
The stack trace should show the guilty function (the function directly =
above __report_gsfailure).
*** enter .exr 49ACA2A0 for the exception record
*** then kb to get the faulting stack
Windows has triggered a breakpoint in wgcc.SUA.exe.
This may be due to a corruption of the heap, and indicates a bug in =
wgcc.SUA.exe or any of the DLLs it has loaded.
The output window may have more diagnostic information
---------------------------------------------------
At this point _mainCRTStartup have not been started yet:
Program flow =3D>
>wgcc.SUA.exe!__PosixProcessStartup(int calledFromldso=3D0, _startupData =
*
incomingStartup=3D0x00000000)
>wgcc.SUA.exe!_init(int argc=3D1, char * * argv=3D0x00010640, char * *
environ=3D0x00010648)
>wgcc.SUA.exe!_cinit()
>wgcc.SUA.exe!_initterm(void (void)* * pfbegin=3D0x00462094, void =
(void)*=20
>*
pfend=3D0x004620f0)
>wgcc.SUA.exe!wgcc::`dynamic initializer for 'context''() Line 703 C++
>wgcc.SUA.exe!wgcc::Context::Context() Line 35 C++
code in Environment.cpp is executed =3D> exception, stack buffer =
overrun.
>wgcc.SUA.exe!_mainCRTStartup()
>wgcc.SUA.exe!main(int argc=3D1, char * * argv=3D0x00010640) Line 100 =
C++
=09
The construction and memory allocation done in Environment.cpp should be =
delayed until we enter main()
I suggest a Context::init() function from main() like this:
extern "C"
int __cdecl main(int argc, char ** argv) {
wgcc::CommandLine::OptionManager manager(wgcc::options, false);
if(!wgcc::context.init()) return ERROR_CODE;
...
and
bool Environment::getPaths(Destination dest, std::list<std::string>& =
paths); bool Context::init() {
// Supply existing list by reference
if(!Environment::getPaths(COMPILER_C, paths.c)) return false;
if(!Environment::getPaths(COMPILER_CPP, paths.cpp)) return false;
if(!Environment::getPaths(LINKER, paths.linker)) return false;
return true;
}
When I applied this fix I got a working build from cc and VS2005
I attach a code analysis build log FYI
Note: The dynamic_cast's mentioned earlier is still turned into =
static_cast's
regards Jerker
|
|
From: Duft M. <Mar...@sa...> - 2006-10-18 11:12:02
|
The reason for the copy is that args_asm get/may get modified after =
that, and this should not happen with the original arguments, since they =
get passed on to other tasks too. I'm using /W3 since /W4 is absolutely =
unusable, i will not correct those warning (at least not all of them) =
WP64 will get interesting in the next few weeks, i'll look at it.
Cheers, Markus=20
-----Original Message-----
From: int...@li... =
[mailto:int...@li...] On Behalf =
Of Jerker B=E4ck
Sent: Wednesday, October 18, 2006 12:00 PM
To: int...@li...
Subject: [wgcc-dev] std::list construct question
A quick question
Did a WIN32 compile and some things float up a lot of 4100 warnings =
(unreferenced formal parameter)
not so pretty - I suggest: Do a /W4 /Wp64 WIN32 compile to clean them =
out
Then the compiler does not understand this (last line):
from AssemblerQueue.cpp(40)
bool AssemblerTaskQueue::prepare(
const std::list< CommandLine::OptionValue >& arguments) {
if(m_Predicate)
if(!m_Predicate->required()) return false;
for(std::list<std::string>::iterator it =3D
context.sources.assembler.begin();
it !=3D context.sources.assembler.end(); it++)
{
std::list<CommandLine::OptionValue> args_asm(arguments);
warning C4510: 'std::_List_nod<_Ty,_Alloc>::_Node' :=20
default constructor could not be generated
warning C4610: struct 'std::_List_nod<_Ty,_Alloc>::_Node'=20
can never be instantiated - user defined constructor required
You try construct a new list copy from a reference to a list?
I don't understand, why not use arguments as it is?
regards
Jerker B=E4ck=20
-------------------------------------------------------------------------=
Using Tomcat but need to do more? Need to support web services, =
security?
Get stuff done quickly with pre-integrated technology to make your job =
easier Download IBM WebSphere Application Server v.1.0.1 based on Apache =
Geronimo
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D=
121642
_______________________________________________
Interix-wgcc-developer mailing list
Int...@li...
https://lists.sourceforge.net/lists/listinfo/interix-wgcc-developer
|
|
From: <jer...@te...> - 2006-10-18 10:01:57
|
A quick question
Did a WIN32 compile and some things float up
a lot of 4100 warnings (unreferenced formal parameter)
not so pretty - I suggest: Do a /W4 /Wp64 WIN32 compile to clean them =
out
Then the compiler does not understand this (last line):
from AssemblerQueue.cpp(40)
bool AssemblerTaskQueue::prepare(
const std::list< CommandLine::OptionValue >& arguments)=20
{
if(m_Predicate)
if(!m_Predicate->required()) return false;
for(std::list<std::string>::iterator it =3D=20
context.sources.assembler.begin();=20
it !=3D context.sources.assembler.end(); it++)
{
std::list<CommandLine::OptionValue> args_asm(arguments);
warning C4510: 'std::_List_nod<_Ty,_Alloc>::_Node' :=20
default constructor could not be generated
warning C4610: struct 'std::_List_nod<_Ty,_Alloc>::_Node'=20
can never be instantiated - user defined constructor required
You try construct a new list copy from a reference to a list?
I don't understand, why not use arguments as it is?
regards
Jerker B=E4ck=20
|
|
From: Duft M. <Mar...@sa...> - 2006-10-18 09:12:10
|
It made it through ;o) Nice to see that some work is done. I currently really have no time = (sorry) to take a deeper look at it. The optimizations are applied to = wgcc? What happens when you don't optimize, or optimize less? Does wggc = work then? Does wgcc convert paths from unix to windows correctly in = this kind of mixed build? I don't know if tha static_cast is a really good idea, this may cause = some difficult to find issues. But for now... ;o) the include should be = ok in any case ... The cool thing is, that both gcc and cl.exe builds of wgcc work for me = (i didn't try with cc) so this must be something with optimization or = static_cast... I wouldn't just take __RTDynamicCast from windows libc, = this would be really dangerous, if one could get it to work somehow. Cheers, Markus=20 -----Original Message----- From: int...@li... = [mailto:int...@li...] On Behalf = Of Jerker B=E4ck Sent: Wednesday, October 18, 2006 10:32 AM To: int...@li... Subject: [wgcc-dev] Some bugs in wgcc when compiling with the MS = compiler Hello all, I have been testing a MS compiler build of wgcc Only a posix build for = Interix 5.2 (SUA) have been tested - no WIN32 or SFU builds. All changes to source code and "full" specification of tools used are mentioned. Compile and link are straightforward but execution of the binary = produced is still failing.=20 This is my first findings - I attach the bug report to this post. Hope it will make it trough the mail system. Regards Jerker B=E4ck=20 |
|
From: <jer...@ho...> - 2006-10-18 08:34:10
|
Hello all, I have been testing a MS compiler build of wgcc Only a posix build for Interix 5.2 (SUA) have been tested - no WIN32 or SFU builds. All changes to source code and "full" specification of tools used are mentioned. Compile and link are straightforward but execution of the binary produced is still failing.=20 This is my first findings - I attach the bug report to this post. Hope it will make it trough the mail system. Regards Jerker B=E4ck=20 |
|
From: Duft M. <Mar...@sa...> - 2006-10-11 06:46:50
|
Hi! Wgcc is capable of building shared libs .dll with import libs that use .so to emulate gcc's behaviour. This .so libraries may be linked by both, but mixing of compilers is extremely dangerous. Linking wgcc compiled objects is only possible if you change the runtime from dynamic to static either by giving -X/MT on the command line or changeing the $prefix/etc/.wgccrc file to use /MT instead of /MD. Then it works... I really have no idea when i'll have time to look into this. I would have to take alook at CC/C89 again (my first approach was changing those ;o)) and implement some stuff in wgcc... Cheers, Markus=20 -----Original Message----- From: Martin Koeppe [mailto:mk...@gm...]=20 Sent: Wednesday, October 11, 2006 1:00 AM To: Duft Markus Cc: int...@li... Subject: RE: wgcc does not build Hi Markus, > I wrote wgcc with the main intention to get native windows binaries=20 > that are plain win32 and have nothing to do anymore with any unix=20 > subsystem or something, since this gave lots of problems, especially=20 > with debugging. For example try to build wgcc debuggable with gcc and=20 > debug with gdb -> it's really impossible ;o) yes, that's a problem. :-( > Debugging with visual studio is really cool only when building really=20 > native (linking with link.exe) maybe the best woulb be building with=20 > gcc and linking with link.exe. agreed here, too. To continue my last mail for motivations for creating POSIX-CUI exes with MS tools, I have these: - One could have link.exe via wgcc as drop-in replacement for ld, which is buggy in some situations. (Of course then there is only static linking...) - gcc/g++ 3.3 is rather old now, so cl.exe could be used, e.g. instead of g++ to have better C++ support. > If you look at the source code of wgcc it would be not a big problem > implementing alternative compiler/linker tasks, since everything is > really modular. sounds good. > At the moment i don't have enough time to work on this, but i will take > a look at it in the near future, since it sounds promising and desirable > to make wgcc able of using the interix tools too. This would make wgcc > the most powerfull build tool for interix around (and most configurable > one)... > > I played around with wgcc and ld, and it seems to work for a small hello > world.... Really cool would have been beeing able of using msvcrt libc > when linking with ld, but there seem to be some restriction, since i > can't seem to be able to execute the resulting binary (but link goes ok > without even a warning)... > > As far as i now see, using either ld or gcc forces the use of the > interix libc & co. This is for our (company) current situation not > really desireable as i allready said, but since wgcc is an open source > project i'm willing to spend some time in implementing this anyway - > when i got some time ;o) Thank you. Can you approximately say, when this might happen? > As far as building bash & co. With cl.exe is concerned: be aware of > compiler capability differences... For example gcc uses > __atribute__(...) and MS uses __declspec(...) which each other don't > understand. So the sources will most likely not build. One more thing > is, that you would have to first port libtermcap or libncurses or so to > cl.exe, which as far as i know would be _really much_ work... >From gcc-4.1 docs: You can use __declspec(dllexport) as a synonym for __attribute__=20 ((dllexport)) for compatibility with other compilers. But: for .so files, you don't need any of __attribute__ or __declspec.=20 .so libs are not DLLs! I currently don't know much technical detail,=20 but they are different. That's why only ld can link (to) them. The=20 general idea is of course the same, though. See here for some details: http://www.interopsystems.com/tools/tm.aspx?m=3D7904 >> Many questions ;o) maybe you want to try (after wgcc works ;o)) to=20 >> only compile with wgcc, and manually link with ld and gather some=20 >> experience in this direction.... I will try too! > > Ok, will try with wgcc, too. This doesn't work, because wgcc compiles with Win32 libc headers, so=20 gcc/ld complains when linking: $ wgcc -g -c -o hello.o hello.c $ gcc hello.o hello.o(.text+0xc): undefined reference to `__imp__printf' collect2: ld returned 1 exit status Martin |
9 messages has been excluded from this view by a project administrator.
