https://sourceware.org/bugzilla/show_bug.cgi?id=23573
--- Comment #17 from Nick Clifton <nickc at redhat dot com> --- Hi Benjamin, > https://www.dropbox.com/s/jyaapql2gj1r7br/gcc-win64.tar.gz?dl=0 Thanks - I was able to download the tarball from there. Unfortunately I do not have a copy of the /usr/lib/x86_64-w64-mingw32/lib/crt2.o object file. (I am using an installed x86_64-mingw32 cross compiler running under Linux). When I commented that part out from the build command line however I was able to run the entire command, including using the plugin, and not get an error message about too many open files. (I did get the messages about the missing libraries however). I suspect therefore that part of the problem is that a native mingw32 build system has a lower limit on the maximum number of files that can be open at any one time. > So removing the linker plugin arguments makes the command work. OK, so this is significant. The implication therefore is that it is the plugin itself which is opening files and then not closing them. (Or maybe the plugin calls a linker function which opens a file, but then the plugin does call the corresponding linker function to close the file). It also means that compiling without -flto is an option for a workaround. Unfortunately the libtlo plugin is actually part of the gcc project, rather than the binutils project, so you may need to refile this bug report there, sorry. In fact it may be that there is no simple solution. It may well be that linking large projects with LTO enabled on a system with a low limit on the number of open files is just not going to work. :-( Not what you want to hear, I know, but it certainly is starting to look like this is the case. Cheers Nick -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
