Re: [ft-devel] Problems compiling freetype into dll
>> What about leaving the path as-is, but saying >> >>mingw32-make SHELL=CMD.exe ... >> >> instead? > > That seems to fix it. Great! Just to be sure: You now get a working DLL? If so, I'll update the documentation. Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Problems compiling freetype into dll
That seems to fix it. Thanks. On 7/10/2013 3:21 PM, Werner LEMBERG wrote: A few "Error 127" messages still occurred until I removed \mingw\msys\1.0\bin from the path, as you suggested. What about leaving the path as-is, but saying mingw32-make SHELL=CMD.exe ... instead? Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Problems compiling freetype into dll
> A few "Error 127" messages still occurred until I removed > \mingw\msys\1.0\bin from the path, as you suggested. What about leaving the path as-is, but saying mingw32-make SHELL=CMD.exe ... instead? Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Problems compiling freetype into dll
Hi Werner, You have provided another hint. I was using "make" which is in \mingw\msys\1.0\bin. But you mentioned "mingw32-make". This program is in \mingw\bin. I did not realize that mingw came with two versions of make! mingw32-make works much better. A few "Error 127" messages still occurred until I removed \mingw\msys\1.0\bin from the path, as you suggested. But I am not happy to lose "less" "grep" and all the other unix commands that live in \mingw\msys\1.0\bin. Some more work will be needed. Thanks. -Dave On 7/8/2013 9:34 PM, Werner LEMBERG wrote: Hello Dave! I have also seen the "Command not found" and "Error 127" messages when trying to run make with mingw. Since the "ver" and "type" commands are built-in, I assumed something in the make script was running a shell other than cmd. Ah, this is probably the right hint. Jörg has the following directories in the path: C:\mingw\mingw\bin C:\mingw\mingw\MSYS\1.0\local\bin C:\mingw\mingw\MSYS\1.0\bin and the last entry makes mingw32-make find `sh.exe' before `cmd.exe', I think. Can you try to remove the last two entries so that the MSYS binaries are not used? Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Problems compiling freetype into dll
Hello Dave! > I have also seen the "Command not found" and "Error 127" messages > when trying to run make with mingw. Since the "ver" and "type" > commands are built-in, I assumed something in the make script was > running a shell other than cmd. Ah, this is probably the right hint. Jörg has the following directories in the path: C:\mingw\mingw\bin C:\mingw\mingw\MSYS\1.0\local\bin C:\mingw\mingw\MSYS\1.0\bin and the last entry makes mingw32-make find `sh.exe' before `cmd.exe', I think. Can you try to remove the last two entries so that the MSYS binaries are not used? Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Problems compiling freetype into dll
I have also seen the "Command not found" and "Error 127" messages when trying to run make with mingw. Since the "ver" and "type" commands are built-in, I assumed something in the make script was running a shell other than cmd. On 7/7/2013 7:19 PM, Werner LEMBERG wrote: C:\ft2501\freetype-2.5.0.1>make make: ver: Command not found make: type: Command not found make: *** [dos_setup] Error 127 Hmm. You are doing something wrong. Both the `ver' and `type' commands exist even for Windows 8, according to http://pcsupport.about.com/od/commandlinereference/tp/windows-8-commands-p3.01.htm Have you inadvertently removed the directory of the Windows command line tools from the path? Anyway, I did a 'make' after that and now I've got a libfreetype-6.dll in ft2501\freetype-2.5.0.1\objs\.libs Great! Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Problems compiling freetype into dll
> C:\ft2501\freetype-2.5.0.1>make > make: ver: Command not found > make: type: Command not found > make: *** [dos_setup] Error 127 Hmm. You are doing something wrong. Both the `ver' and `type' commands exist even for Windows 8, according to http://pcsupport.about.com/od/commandlinereference/tp/windows-8-commands-p3.01.htm Have you inadvertently removed the directory of the Windows command line tools from the path? > Anyway, I did a 'make' after that and now I've got a > libfreetype-6.dll in ft2501\freetype-2.5.0.1\objs\.libs Great! Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Problems compiling freetype into dll
Hello. Sorry, I had a busy week, otherwise I'd have replied earlier. >>Please open a standard Windows >>terminal (*not* msys), set up a proper path to the mingw tools (gcc, >>GNU make, etc.), and execute make This is the mingw part of my path variable: C:\mingw\mingw\bin;C:\mingw\mingw\MSYS\1.0\local\bin;C:\mingw\mingw\MSYS\1.0\bin; Fresh clean freetype is put into C:\ft2501\freetype-2.5.0.1 Opening cmd, going to that dir, running 'make' results in C:\ft2501\freetype-2.5.0.1>make make: ver: Command not found make: type: Command not found make: *** [dos_setup] Error 127 That doesn't look good. >>Maybe you can use ProcMon Starting over from a clean freetype in msys/home/ft2501 I ran procmon, opened the msys prompt and did ./configure --without-png Libtool didn't complain about write permissions this time (Which is strange since I didn't change anything else...) Anyway, I did a 'make' after that and now I've got a libfreetype-6.dll in ft2501\freetype-2.5.0.1\objs\.libs I'll go and try out whether I can use that. I'll report back on how that works out. With regards, Jörg ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Problems compiling freetype into dll
> Since I don't need png support, I ran > ./configure --without.png > > Then, my platform gets identified as unix. This is OK, since it is the very job of msys to emulate a UNIX environment while running the `configure' script -- please remember that `configure' does normally not check the platform itself but rather whether certain features are available, delegating all such questions to the compiler, the linker, the archiver, etc., which can answer this best. However, the script itself needs a UNIX shell for proper execution. The same is true for make: If the Makefile contains calls to shell scripts (like the libtool stuff which is used for compiling and creating the DLL in Unix mode), you should run it in msys. > I added the log as an attachment. Thanks. This looks good, except this: mv: cannot move `libtoolT.tmp' to `libtoolT': Permission denied Apparently there is a missing writing permission somewhere. On the other hand, the `configure' script doesn't have this problem, which is strange. Maybe you can use ProcMon http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx or logger http://msdn.microsoft.com/en-us/library/windows/hardware/ff552060(v=vs.85).aspx to find out where the problem is. * * * Now back to your original question. Please open a standard Windows terminal (*not* msys), set up a proper path to the mingw tools (gcc, GNU make, etc.), and execute make and make again (starting from a clean FreeType tree) and send us a log. This should build a DLL also, and if it doesn't, there is a bug somewhere which has crept in over the years, and hopefully we can fix it. Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Problems compiling freetype into dll
Hi. >>What do you mean with `mingw32-make'? The mingw32-make.exe of mingw, which is located in mingw/bin. >>Are you actually using the mingw build system? Yes. >>Then simply say `./configure' within an msys terminal, followed by `make'. D'oh! I've been running mingw32-make.exe directly from cmd. Still getting used to this build system. >> Please show us *exactly* what you do from a clean directory My msys/mingw is installed under C:\mingw\mingw\msys\1.0 I unpacked a clean freetype archive to C:\mingw\mingw\msys\1.0\home\ft2501\freetype-2.5.0.1 Ran msys.bat, changed to the directory Since I don't need png support, I ran ./configure --without.png Then, my platform gets identified as unix. >> please send us log data I added the log as an attachment. With regards Jörg Yoerg@Computer ~ $ cd .. Yoerg@Computer /home $ cd ft2501/ Yoerg@Computer /home/ft2501 $ cd freetype-2.5.0.1/ Yoerg@Computer /home/ft2501/freetype-2.5.0.1 $ ./configure --without-png FreeType build system -- automatic system detection The following settings are used: platformunix compilercc configuration directory ./builds/unix configuration rules ./builds/unix/unix.mk If this does not correspond to your system or settings please remove the file `config.mk' from this directory then read the INSTALL file for help. Otherwise, simply type `make' again to build the library, or `make refdoc' to build the API reference (the latter needs python). cd builds/unix; /bin/sh ./configure '--without-png' checking build system type... i686-pc-mingw32 checking host system type... i686-pc-mingw32 checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.exe checking for suffix of executables... .exe checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking how to run the C preprocessor... gcc -E checking for rmdir... rmdir checking for a BSD-compatible install... /bin/install -c checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking for unistd.h... (cached) yes checking for an ANSI C-conforming const... yes checking size of int... 4 checking size of long... 4 checking whether cpp computation of bit length in ftconfig.in works... yes checking for stdlib.h... (cached) yes checking for unistd.h... (cached) yes checking for sys/param.h... yes checking for getpagesize... yes checking for working mmap... no checking for memcpy... yes checking for memmove... yes checking gcc compiler flag -pedantic to assure ANSI C works correctly... ok, add it to XX_ANSIFLAGS checking gcc compiler flag -ansi to assure ANSI C works correctly... ok, add it to XX_ANSIFLAGS checking for gzsetparams in -lz... no checking for BZ2_bzDecompress in -lbz2... no checking how to print strings... printf checking for a sed that does not truncate output... /bin/sed checking for fgrep... /bin/grep -F checking for ld used by gcc... c:/mingw/mingw/mingw32/bin/ld.exe checking if the linker (c:/mingw/mingw/mingw32/bin/ld.exe) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /mingw/bin/nm checking the name lister (/mingw/bin/nm) interface... BSD nm checking whether ln -s works... no, using cp -pR checking the maximum length of command line arguments... 8192 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking how to convert i686-pc-mingw32 file names to i686-pc-mingw32 format... func_convert_file_msys_to_w32 checking how to convert i686-pc-mingw32 file names to toolchain format... func_c onvert_file_msys_to_w32 checking for c:/mingw/mingw/mingw32/bin/ld.exe option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... file_magic ^x86 archive import| ^x86 DLL checking for dlltool... dlltool checking how to associate runtime and link libraries... func_cygming_dll_for_imp lib checking for ar... ar checking for archiver @FILE support... @ checking for strip... strip checking for ranlib... ranlib checking for gawk... gawk checking command to parse /mingw/bin/nm output from gcc object... ok checking for sysroot... no checking for mt... no checking if : is a manifest tool... no checking for dlfcn.h... no checking for as... as checking for dlltool... (cached) dlltool checking for
Re: [ft-devel] Problems compiling freetype into dll
> I've tried to compile freetype 2.5.0.1 from source using mingw32-make > (v2.8.3) on win7. > > My system was identyfied as windows w/gcc, so I went and manually > replaced the contents of confic.mk with the contents of > w32-mingw32.mk. What do you mean with `mingw32-make'? Are you actually using the mingw build system? Then simply say `./configure' within an msys terminal, followed by `make'. IIRC, this works out of the box. > "mingw32-make: *** No rule to make target `exported_symbols', needed by > `dll'. A bug. Don't use the `dll' target (I've just removed it in the git repository). Note that there are high chances that the non-configure setup is broken since I don't use Windows by default for testing. > How can I fix this and get a dll? Well, the DLL should be built automatically. Please show us *exactly* what you do from a clean directory, and please send us log data. Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
[ft-devel] Problems compiling freetype into dll
Hello. I've tried to compile freetype 2.5.0.1 from source using mingw32-make (v2.8.3) on win7. My system was identyfied as windows w/gcc, so I went and manually replaced the contents of confic.mk with the contents of w32-mingw32.mk. 'Make'-ing the project works, but doesn't result in a dynamic lib (e.g. only the .a is build). Trying out target 'dll' results in "mingw32-make: *** No rule to make target `exported_symbols', needed by `dll'. S top." Anyone know how what's going wrong here? (Obviously, a built rule missing or not found, but the error's not very verbose about where). How can I fix this and get a dll? Kind regards, Jörg ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
