I downloaded the mingw gcc 3.4.2 from mingw.org and it seems that it's specs/linker script is messed up. By default g++ should link to libstdc++.a shouldn't it? Well this thing isn't. Now I don't really understand how the gcc specs file works, but I think that is where it should be telling g++ to link to libstdc++.a, so if anyone else has any idea how that file works and might point out where I need to add the command to link in libstdc++.a, I'd appreciate it.
Figured it out on irc thanks to... was it steven? I'm beat so I can't think straight. Anyhow, turned out the blasted specs file had an absolute path refering to c:\mingw and I had installed to c:\rosbe.
Phillip Susi wrote:
I downloaded the mingw gcc 3.4.2 from mingw.org and it seems that it's specs/linker script is messed up. By default g++ should link to libstdc++.a shouldn't it? Well this thing isn't. Now I don't really understand how the gcc specs file works, but I think that is where it should be telling g++ to link to libstdc++.a, so if anyone else has any idea how that file works and might point out where I need to add the command to link in libstdc++.a, I'd appreciate it.
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
On Tuesday 05 April 2005 07:32, Phillip Susi wrote:
Figured it out on irc thanks to... was it steven? I'm beat so I can't think straight. Anyhow, turned out the blasted specs file had an absolute path refering to c:\mingw and I had installed to c:\rosbe.
Have you used the "ReactOS Build Environment" package? If yes, then I gotta fix it to adjust that path when installing I guess.
-blight
I started off with the reactos build environment package, but it failed to build. I can't remember if it was because of this problem or something else, so I overwrote it with an older version of gcc mentioned on reactos.com with a message saying the newer version is buggy. I was told by a few people on irc that web page is obsolete, the new, new version of gcc works fine and so I should use that. I got that downloaded and then started having this problem.
Anich Gregor wrote:
On Tuesday 05 April 2005 07:32, Phillip Susi wrote:
Figured it out on irc thanks to... was it steven? I'm beat so I can't think straight. Anyhow, turned out the blasted specs file had an absolute path refering to c:\mingw and I had installed to c:\rosbe.
Have you used the "ReactOS Build Environment" package? If yes, then I gotta fix it to adjust that path when installing I guess.
-blight _______________________________________________ Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Having also problems using the latest releases from mingw.org!
Strangely the #error command in ./tools/tools-check.c tells me to get the newest version of binutils. Found no later than the one on mingw.org which is actually causing this #error to be shown.
Also I am missing tools-check.h in the RC2.
No idea how to build ROS now :-(
Oliver
I started off with the reactos build environment package, but it failed to build. I can't remember if it was because of this problem or something else, so I overwrote it with an older version of gcc mentioned on reactos.com with a message saying the newer version is buggy. I was told by a few people on irc that web page is obsolete, the new, new version of gcc works fine and so I should use that. I got that downloaded and then started having this problem.
Anich Gregor wrote:
On Tuesday 05 April 2005 07:32, Phillip Susi wrote:
Figured it out on irc thanks to... was it steven? I'm beat so I can't think straight. Anyhow, turned out the blasted specs file had an absolute path refering to c:\mingw and I had installed to c:\rosbe.
Have you used the "ReactOS Build Environment" package? If yes, then I
gotta
fix it to adjust that path when installing I guess.
-blight _______________________________________________ Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Oliver Schneider wrote:
Having also problems using the latest releases from mingw.org!
Strangely the #error command in ./tools/tools-check.c tells me to get the newest version of binutils. Found no later than the one on mingw.org which is actually causing this #error to be shown.
Also I am missing tools-check.h in the RC2.
That file should be auto-generated... Let me guess, you're using MSYS make, right?
Filip
Thanks for your reply.
That file should be auto-generated... Let me guess, you're using MSYS make, right?
I believe so. What's wrong with it? The GAIM guys also complain about it. It it really always the culprit? ;)
So it should work with either Cygwin's make or the make you provide on the ROS-website?
Oliver
Oliver Schneider wrote:
Thanks for your reply.
hat file should be auto-generated... Let me guess, you're using MSYS make, right?
I believe so. What's wrong with it? The GAIM guys also complain about it. It it really always the culprit? ;)
I can only say that you're on your own when using MSYS make...it's pretty different environment from standard MinGW. The attached patch solves the problem with tools-check on MSYS, but be prepared that other problems can appear (especially with dependency files)..
- Filip.
Index: tools-check.mak =================================================================== --- tools-check.mak (revision 14332) +++ tools-check.mak (working copy) @@ -12,9 +12,7 @@ BINUTILS_VERSION_DATE=$(word 5,$(shell $(PREFIX)ld -v))
all: -ifeq ($(HOST),mingw32-linux) @echo "#define BINUTILS_VERSION_DATE $(BINUTILS_VERSION_DATE)" > tools-check.h -endif ifeq ($(HOST),mingw32-windows) @echo #define BINUTILS_VERSION_DATE $(BINUTILS_VERSION_DATE) > tools-check.h endif
Perhaps the page at http://reactos.com/en/reactos_developer_site/resources/download_the_recommen... be updated as the version there causes this error. Which version should I be using? Should I use the latest version of MinGW available from the MinGW site?
On Apr 5, 2005 8:55 AM, Filip Navara xnavara@volny.cz wrote:
Oliver Schneider wrote:
Thanks for your reply.
hat file should be auto-generated... Let me guess, you're using MSYS make, right?
I believe so. What's wrong with it? The GAIM guys also complain about it.
It
it really always the culprit? ;)
I can only say that you're on your own when using MSYS make...it's pretty different environment from standard MinGW. The attached patch solves the problem with tools-check on MSYS, but be prepared that other problems can appear (especially with dependency files)..
- Filip.
Index: tools-check.mak
--- tools-check.mak (revision 14332) +++ tools-check.mak (working copy) @@ -12,9 +12,7 @@ BINUTILS_VERSION_DATE=$(word 5,$(shell $(PREFIX)ld -v))
all: -ifeq ($(HOST),mingw32-linux) @echo "#define BINUTILS_VERSION_DATE $(BINUTILS_VERSION_DATE)" > tools-check.h -endif ifeq ($(HOST),mingw32-windows) @echo #define BINUTILS_VERSION_DATE $(BINUTILS_VERSION_DATE) > tools-check.h endif
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Phillip Susi wrote:
I started off with the reactos build environment package, but it failed to build. I can't remember if it was because of this problem or something else, so I overwrote it with an older version of gcc mentioned on reactos.com with a message saying the newer version is buggy. I was told by a few people on irc that web page is obsolete, the new, new version of gcc works fine and so I should use that. I got that downloaded and then started having this problem.
Have you tried doing "make clean" in subsys/system/explorer (and subsys/system/ibrowser)?
- Filip
P.S. Welcome back!
-
Anich Gregor -
David Leinbach -
Filip Navara -
Oliver Schneider -
Phillip Susi