From: Alexander H. <ale...@gm...> - 2017-11-16 05:10:08
|
> On Nov 15, 2017, at 21:03, Mark D. McKean <qp...@qu...> wrote: > > On 10/17/2017 08:18 pm, Alexander Hansen wrote: >> >>> On Oct 17, 2017, at 07:54, Alexander Hansen <ale...@gm... <mailto:ale...@gm...>> wrote: >>> >>> >>>> On Oct 16, 2017, at 08:38, Alexander Hansen <ale...@gm... <mailto:ale...@gm...>> wrote: >>>> >>>>> >>>>> On Oct 13, 2017, at 23:34, Mark D. McKean <qp...@qu... <mailto:qp...@qu...>> wrote: >>>>> >>>>> I'm getting a compile failure on gcc5-5.5.0.1-1. It doesn't appear to be >>>>> the same problem that someone else posted here today about. I tried the >>>>> solution mentioned in that thread (move aside /usr/local) and the >>>>> compile still failed with the same error as before moving /usr/local. >>>>> >>>>> The error in my compile came up as: >>>>> >>>>> In file included from ../../../../gcc-5.5.0/libgcc/libgcc2.c:27:0: >>>>> ../../../../gcc-5.5.0/libgcc/../gcc/tsystem.h:87:19: fatal error: >>>>> stdio.h: No such file or directory >>>>> >>>>> I've appended more of the output below my signature, starting several >>>>> lines before the error. Let me know if you want the full compile output >>>>> as well (it's really long--it spent over half an hour working on it >>>>> before hitting the error). >>>>> >>>>> Mark D. McKean >>>>> qp...@qu... <mailto:qp...@qu...> >>>>> >>>>> make[5]: Entering directory >>>>> '/sw/src/fink.build/gcc5-5.5.0-1/darwin_objdir/x86_64-apple-darwin14.5.0/i386/libgcc' >>>>> # If this is the top-level multilib, build all the other >>>>> # multilibs. >>>>> /bin/sh ../../../../gcc-5.5.0/libgcc/../mkinstalldirs ../../.././gcc/i386 >>>>> mkdir ../../.././gcc/i386 >>>>> for file in libgcc_s.1.dylib libgcc_ext.10.4.dylib >>>>> libgcc_ext.10.5.dylib; do \ >>>>> rm -f ../../.././gcc/i386/$file; \ >>>>> ln -s ../$file ../../.././gcc/i386/; \ >>>>> done >>>>> rm -f ../../.././gcc/i386/libgcc_s_x86_64.1.dylib >>>>> ln -s libgcc_s.1.dylib \ >>>>> ../../.././gcc/i386/libgcc_s_x86_64.1.dylib >>>>> rm -f ../../.././gcc/i386/libgcc_s_ppc64.1.dylib >>>>> ln -s libgcc_s.1.dylib \ >>>>> ../../.././gcc/i386/libgcc_s_ppc64.1.dylib >>>>> DEFINES='' HEADERS='../../../../gcc-5.5.0/libgcc/config/i386/darwin-lib.h' \ >>>>> ../../../../gcc-5.5.0/libgcc/mkheader.sh > tmp-libgcc_tm.h >>>>> /bin/sh ../../../../gcc-5.5.0/libgcc/../move-if-change tmp-libgcc_tm.h >>>>> libgcc_tm.h >>>>> echo timestamp > libgcc_tm.stamp >>>>> /sw/src/fink.build/gcc5-5.5.0-1/darwin_objdir/./gcc/xgcc >>>>> -B/sw/src/fink.build/gcc5-5.5.0-1/darwin_objdir/./gcc/ >>>>> -B/sw/lib/gcc5/x86_64-apple-darwin14.5.0/bin/ >>>>> -B/sw/lib/gcc5/x86_64-apple-darwin14.5.0/lib/ -isystem >>>>> /sw/lib/gcc5/x86_64-apple-darwin14.5.0/include -isystem >>>>> /sw/lib/gcc5/x86_64-apple-darwin14.5.0/sys-include -g -O2 -m32 -O2 >>>>> -g -O2 -DIN_GCC -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual >>>>> -Wno-format -Wstrict-prototypes -Wmissing-prototypes >>>>> -Wold-style-definition -isystem ./include -mmacosx-version-min=10.5 >>>>> -pipe -fno-common -g -DIN_LIBGCC2 -fbuilding-libgcc >>>>> -fno-stack-protector -mmacosx-version-min=10.5 -pipe -fno-common -I. >>>>> -I. -I../../.././gcc -I../../../../gcc-5.5.0/libgcc >>>>> -I../../../../gcc-5.5.0/libgcc/. -I../../../../gcc-5.5.0/libgcc/../gcc >>>>> -I../../../../gcc-5.5.0/libgcc/../include -DHAVE_CC_TLS -DUSE_EMUTLS -o >>>>> _muldi3.o -MT _muldi3.o -MD -MP -MF _muldi3.dep -DL_muldi3 -c >>>>> ../../../../gcc-5.5.0/libgcc/libgcc2.c -fvisibility=hidden -DHIDE_EXPORTS >>>>> In file included from ../../../../gcc-5.5.0/libgcc/libgcc2.c:27:0: >>>>> ../../../../gcc-5.5.0/libgcc/../gcc/tsystem.h:87:19: fatal error: >>>>> stdio.h: No such file or directory >>>>> compilation terminated. >>>>> make[5]: *** [Makefile:466: _muldi3.o] Error 1 >>>>> make[5]: Leaving directory >>>>> '/sw/src/fink.build/gcc5-5.5.0-1/darwin_objdir/x86_64-apple-darwin14.5.0/i386/libgcc' >>>>> make[4]: *** [Makefile:1154: multi-do] Error 1 >>>>> make[4]: Leaving directory >>>>> '/sw/src/fink.build/gcc5-5.5.0-1/darwin_objdir/x86_64-apple-darwin14.5.0/libgcc' >>>>> make[3]: *** [Makefile:119: all-multi] Error 2 >>>>> make[3]: Leaving directory >>>>> '/sw/src/fink.build/gcc5-5.5.0-1/darwin_objdir/x86_64-apple-darwin14.5.0/libgcc' >>>>> make[2]: *** [Makefile:14832: all-stage1-target-libgcc] Error 2 >>>>> make[2]: Leaving directory '/sw/src/fink.build/gcc5-5.5.0-1/darwin_objdir' >>>>> make[1]: *** [Makefile:20771: stage1-bubble] Error 2 >>>>> make[1]: Leaving directory '/sw/src/fink.build/gcc5-5.5.0-1/darwin_objdir' >>>>> make: *** [Makefile:21087: bootstrap-lean] Error 2 >>>>> ### execution of /tmp/fink.3y2jr failed, exit code 2 >>>>> ### execution of /tmp/fink.slNzb failed, exit code 2 >>>>> Removing runtime build-lock... >>>>> Removing build-lock package... >>>>> /sw/bin/dpkg-lockwait -r fink-buildlock-gcc5-5.5.0-1 >>>>> (Reading database ... 54845 files and directories currently installed.) >>>>> Removing fink-buildlock-gcc5-5.5.0-1 ... >>>>> Failed: phase compiling: gcc5-5.5.0-1 failed >>>>> >>>>> Package manager version: 0.42.0 >>>>> Distribution version: selfupdate-rsync Fri Oct 13 23:20:39 2017, 10.10, >>>>> x86_64 >>>>> Trees: local/main stable/main stable/crypto >>>>> Xcode.app: 7.2.1 >>>>> Xcode command-line tools: 7.2.0.0.1.1447826929 >>>>> Max. Fink build jobs: 1 >>>>> >>>> >>>> Hi. I’ve got a 10.10 environment ready to try to reproduce this, but since I use my machine for work I can really only do that off hours or in chunks when I don’t need CPU during the day. I’ll follow up when I’ve got some output. >>>> >>>> -- >>>> Alexander Hansen, Ph.D. >>>> Fink User Liaison >>> >>> >>> Meh, that virtual machine managed to break itself really badly. I’ll have to see if I’ve got a backup. Or maybe someone else who is on 10.10 can chime in with a success/failure report. >>> >>> >>> -- >>> Alexander Hansen, Ph.D. >>> Fink User Liaison >>> >> >> No working backup, and apparently my 10.10 installer won’t work anymore, either. Drat. >> > Just checking in to see if anyone can help with this. I understand you're having troubles getting a 10.10 environment to test this on, Alexander, but if anyone else can help, I'd be appreciative. My ability to do updates is hampered by this, because gcc5 always comes up on an update-all, so anything that wasn't updated before it gets to this has to be manually updated. > > I just tested the gcc5 install again today, and it still fails with the same error. If I knew more about how these packages were put together, I'd be more than willing to try to figure out what's causing the problem. > > I did a little research, but I don't know how helpful this info might be. Spotlight found six files called "stdio.h" inside the fink.build directory, at the following locations: > /sw/src/fink.build/gcc5-5.5.0-1/gcc-5.5.0/fixincludes/tests/base/stdio.h > /sw/src/fink.build/gcc5-5.5.0-1/gcc-5.5.0/gcc/testsuite/gcc.dg/cpp/usr/include/stdio.h > /sw/src/fink.build/gcc5-5.5.0-1/gcc-5.5.0/libstdc++-v3/include/tr1/stdio.h > /sw/src/fink.build/gcc5-5.5.0-1/gcc-5.5.0/libstdc++-v3/include/c_compatibility/stdio.h > /sw/src/fink.build/gcc5-5.5.0-1/gcc-5.5.0/libssp/ssp/stdio.h > /sw/src/fink.build/gcc5-5.5.0-1/gcc-5.5.0/fixincludes/tests/base/rtldef/stdio.h > > All six, of course, are different. And none of them is in /sw/src/fink.build/gcc5-5.5.0-1/gcc-5.5.0/include, which is where I would expect the install script to look for it if it doesn't pull it directly from the appropriate SDK in Xcode (and I have verified that it is present in all my Xcode SDKs). But I don't know whether any of that matters; for all I know, a bad reference to "stdio.h" could just be a result of some cascading problem elsewhere in the process, the symptom that caused the compile to actually break. > > I grepped the entire fink.build directory in BBEdit for references to "stdio.h", and found 2251 occurrences in 1290 files. I'm not going to manually read through over a thousand files to figure out which one, if any, is the one that's causing this problem. And I have no idea which file the affected part of the compile would have been reading from at that time. This is where knowing more about this end of it might be helpful. (I can figure out simple compiles, but gcc5 appears to be the antithesis of "simple".) > > If there are any logfiles that would be useful for me to send or look through, let me know. I'd really like to get this figured out. > > Mark D. McKean > qp...@qu... <mailto:qp...@qu...>My guess is that the stdio.h that it wants is one from the system, e.g. /usr/include/stdio.h . You might check that that is present—a Fink build doesn’t necessarily automatically delve into the SDK directories. —akh |