The x configure segmentation fault has been plaguing us since the release of OS X El Capitan. We were all worried that the new system would be a disaster. Now, we can rest easy knowing that the x configure error is going to be fixed and the new system will be just fine. We’re really excited about it.
After a long time of waiting for the x configure error to go away, Xcode has finally gotten around to fixing this bug. It’s always nice to know that Apple is working on fixing all their bugs. If it wasn’t for the x configure bug it would have been years before we could install OS X on our MacBooks. We’re very happy to see Apple fixing this bug though.
The x configure error is a bit like the “bad” version of the “dummy file” error. While its important to know that Apple is fixing the x configure bug, it’s important to know what the problem is and how to fix it. The problem is that the file it is referring to, /System/Library/… is a symlink and doesn’t exist on the device where the app is running.
The reason that there is a symlink is because the x configure bug is caused when a file gets corrupted.
Its no different than what happens when you build an app with a link to a folder on your desktop and then when you try to run the app, you get a segmentation fault. Apple fixed this bug with its new -X flag that lets you specify link locations. These link locations are what the x configure bug is all about.
The fix was pretty simple, if you wanted to build a new project and want to run it on your phone, you’d use the -D option. But once you got the -D flag, you’d get a segmentation fault. So the fix was not perfect, and it would probably throw you out of the project. I’ve been using this fix for a while now, and honestly, I can’t remember if it worked or not… But I can say that it didn’t.
If you’re using x configure, and youre not using the -D flag, then you will get a segmentation fault. I got one last week, and it was a bit of a bummer. You can get the problem by adding something like “0x1.0” somewhere in the link text, which results in a segmentation fault. Just put the right number in the link text, and it should go away.
I think that what is most confusing about this is when you run x configure, but youre not using the -D flag. When you remove that flag, you will get a segmentation fault (assuming you are running x configure). As far as I know, x configure has not been updated in a long time, so maybe it had its issues.
The problem is that x configure does not work very well if you’re compiling with gcc (which is the default compiler). When compiling with gcc, the compiler attempts to compile the linker into a separate, stand-alone program. This means that the linker itself is not being compiled, and the compiler fails to correctly see that the linker is being compiled. This can result in strange bugs that are hard to track down.
Why isn’t the x configure bug fix really an issue? I think it’s because the compiler has been stuck on the part of the source code that defines the default architecture. If you compile with gcc, it will find the default architecture and will warn you about a problem. If you compile with x configure, the compiler will find the default architecture and will warn you about the bug. The only way to fix the bug is to make the source code the same as the compiler source.
