I started compiling ReactOS 0.2.7 on my Linux box uname -a Linux localhost 2.6.3-7mdk #1 Wed Mar 17 15:56:42 CET 2004 i686 Celeron (Coppermine) unknown GNU/Linux This was the result.
I'm using i586-mingw32mscv-*. Now my question is, in which file do I find the elusive (PREFIX)? Because I can't find it in Makefile.
[wparish@localhost reactos027]$ make [MKDIR] obj-i386/tools [MKDIR] obj-i386/tools/rbuild [MKDIR] obj-i386/tools/rbuild/backend [MKDIR] obj-i386/tools/rbuild/backend/mingw [CC] tools/rbuild/backend/mingw/mingw.cpp [CC] tools/rbuild/backend/mingw/modulehandler.cpp [CC] tools/rbuild/backend/mingw/proxymakefile.cpp [MKDIR] obj-i386/tools/rbuild/backend/devcpp [CC] tools/rbuild/backend/devcpp/devcpp.cpp [CC] tools/rbuild/backend/backend.cpp [CC] tools/rbuild/automaticdependency.cpp [CC] tools/rbuild/bootstrap.cpp [CC] tools/rbuild/cdfile.cpp [CC] tools/rbuild/compilerflag.cpp [CC] tools/rbuild/configuration.cpp [CC] tools/rbuild/define.cpp [CC] tools/rbuild/exception.cpp [CC] tools/rbuild/filesupportcode.cpp [CC] tools/rbuild/include.cpp [CC] tools/rbuild/installfile.cpp [CC] tools/rbuild/linkerflag.cpp [CC] tools/rbuild/module.cpp [CC] tools/rbuild/project.cpp [CC] tools/rbuild/ssprintf.cpp [CC] tools/rbuild/stubbedcomponent.cpp [CC] tools/rbuild/testsupportcode.cpp [CC] tools/rbuild/wineresource.cpp [CC] tools/rbuild/XML.cpp [CC] tools/rbuild/rbuild.cpp [MKDIR] output-i386/tools [MKDIR] output-i386/tools/rbuild [LD] output-i386/tools/rbuild/rbuild [MKDIR] obj-i386/tools/bin2res [CC] tools/bin2res/bin2res.c [CC] tools/bin2res/mkstemps.c [MKDIR] output-i386/tools/bin2res [LD] output-i386/tools/bin2res/bin2res [MKDIR] obj-i386/tools/buildno [CC] tools/buildno/buildno.cpp [CC] tools/buildno/exception.cpp [CC] tools/buildno/ssprintf.cpp [CC] tools/buildno/XML.cpp [MKDIR] output-i386/tools/buildno [LD] output-i386/tools/buildno/buildno [BUILDNO] include/reactos/buildno.h [MKDIR] obj-i386/tools/wmc [CC] tools/wmc/getopt.c [CC] tools/wmc/lang.c [CC] tools/wmc/mcl.c [CC] tools/wmc/utils.c [CC] tools/wmc/wmc.c [CC] tools/wmc/write.c [CC] tools/wmc/y_tab.c [CC] tools/wmc/misc.c [MKDIR] output-i386/tools/wmc [LD] output-i386/tools/wmc/wmc [WMC] include/reactos/bugcodes.h [WMC] include/reactos/errcodes.h [MKDIR] obj-i386/tools/nci [CC] tools/nci/ncitool.c [MKDIR] output-i386/tools/nci [LD] output-i386/tools/nci/nci [NCI] ntoskrnl/include/internal/napi.h [MKDIR] obj-i386/tools/gendib [CC] tools/gendib/gendib.c [MKDIR] output-i386/tools/gendib [LD] output-i386/tools/gendib/gendib [GENDIB] subsys/win32k/dib/dib16gen.c [RBUILD] makefile.auto Reading build files...done Detecting compiler...not detected Detecting netwide assembler...detected (nasm) Detecting compiler -pipe support...not detected Detecting compiler pre-compiled header support...not detected Processing modules...done Creating directories...done Unpacking WINE resources...done Generating test support code...done Generating proxy makefiles...done Checking automatic dependencies...done [DLLTOOL] obj-i386/lib/kernel32/libkernel32.a make: mingw32-dlltool: Command not found make: *** [obj-i386/lib/kernel32/libkernel32.a] Error 127 [wparish@localhost reactos027]$
on gentoo I used to create the install cd with these commands: export ROS_PREFIX=i386-mingw32msvc export PATH=$PATH:/opt/xmingw/bin make bootcd
you should: export ROS_PREFIX=i586-mingw32msvc and export PATH=$PATH:<folder of your mingw installation>
talley
ps: you should read the beginning of the trunk/reactos/Makefile. it contains a lot of inromation.. like: # Accepted environment variables: # # ROS_PREFIX # This variable specifies the prefix of the MinGW installation. On Windows # a prefix is usually not needed, but on linux it is usually "mingw32". If # not present and no executable named "gcc" can be found, then the prefix is # assumed to be "mingw32". If your gcc is named i386-mingw32-gcc then set # ROS_PREFIX to i386-mingw32. Don't include the dash (-) before gcc.
Wesley Parish wrote:
I started compiling ReactOS 0.2.7 on my Linux box uname -a Linux localhost 2.6.3-7mdk #1 Wed Mar 17 15:56:42 CET 2004 i686 Celeron (Coppermine) unknown GNU/Linux This was the result.
I'm using i586-mingw32mscv-*. Now my question is, in which file do I find the elusive (PREFIX)? Because I can't find it in Makefile.
...
make: mingw32-dlltool: Command not found make: *** [obj-i386/lib/kernel32/libkernel32.a] Error 127 [wparish@localhost reactos027]$
Thanks.
But the problem's solved - at least for the moment. I edited PREFIX in makefile.auto, ignoring the warning about it being an automatically-generated file, and typed 'make' and it decided to do its thing.
Still, your idea sounds good. I'll keep it in mind.
Wesley Parish
On Sat, 15 Oct 2005 23:21, Horváth Róbert wrote:
on gentoo I used to create the install cd with these commands: export ROS_PREFIX=i386-mingw32msvc export PATH=$PATH:/opt/xmingw/bin make bootcd
you should: export ROS_PREFIX=i586-mingw32msvc and export PATH=$PATH:<folder of your mingw installation>
talley
ps: you should read the beginning of the trunk/reactos/Makefile. it contains a lot of inromation.. like: # Accepted environment variables: # # ROS_PREFIX # This variable specifies the prefix of the MinGW installation. On Windows # a prefix is usually not needed, but on linux it is usually "mingw32". If # not present and no executable named "gcc" can be found, then the prefix is # assumed to be "mingw32". If your gcc is named i386-mingw32-gcc then set # ROS_PREFIX to i386-mingw32. Don't include the dash (-) before gcc.
Wesley Parish wrote:
I started compiling ReactOS 0.2.7 on my Linux box uname -a Linux localhost 2.6.3-7mdk #1 Wed Mar 17 15:56:42 CET 2004 i686 Celeron (Coppermine) unknown GNU/Linux This was the result.
I'm using i586-mingw32mscv-*. Now my question is, in which file do I find the elusive (PREFIX)? Because I can't find it in Makefile.
...
make: mingw32-dlltool: Command not found make: *** [obj-i386/lib/kernel32/libkernel32.a] Error 127 [wparish@localhost reactos027]$
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
-
Horváth Róbert -
Wesley Parish