Need to disable codesign

[BooCocky]

Somewhere between 4.2.1-4.3.5 apple decided to make the sysctl variables that disable codesign check "read only" this means you cant disable them with a simple sysctl command.  Im now on iOS5 and it still exists.  This didnt used to be a real issue, but Ive been getting errors when compiling big programs.  The error I get is in configure

Code: [Select]

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... arm-apple-darwin11.0.0
checking host system type... arm-apple-darwin11.0.0
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C
 compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
w
Here is the issue, configure creates a test program "a.out" then trys to run it but cant because it is not signed, so then it stops because it thinks it cant run c compiled programs.  There needs to be a work around this, either someway to disable codesign another way. Here is the part of the config.log that tells me this is the case:

Code: [Select]

configure:2246: checking whether the C compiler works
configure:2252: ./a.out
./configure: line 2253: 11872 Killed: 9               ./$ac_file
configure:2255: $? = 137
configure:2264: error: cannot run C compiled programs.

only thing I can think of is find the rule in the configure script that runs a.out and sign it before it is run.  Which is kind of a pain in the ass.  Whatch think?

[A12danrulz]

Sounds good

[Trcx528]

can you edit out the part that goes: checking whether the C compiler works... configure: error: cannot run C ?

[BooCocky]

Yea I was able to get past that part of the configure script by deleting like 20 lines of code.  Just another thing thats a pain in the ass ya know.

[A12danrulz]

Yeah

[h4ck3rpr0n3]

hmm... but once we got around it if we package it like that then we're golden right? so it'd be a one time pain in the ass instead of repeating.

[Trcx528]

Could we write a script to move/replace gcc that would pass all the args to gcc, but then codesign the output with ldid?  

[A12danrulz]

Or we could make our own version of make

[h4ck3rpr0n3]

Or we could make our own version of make

yes we could, but wouldn't that be more work than it's worth?

[BooCocky]

Every package source uses different CC flags so you can do that .  You have to either find the flags in the configure script and add ldid, or delete the part of the script that trys to run a test program.  

[Trcx528]

Code: [Select]

checking for C compiler default output file name... a.out
I think we could use logic similar to this part of the configure script to detect any gcc output.  Then it would be as simple as writing a new script that we would call gcc.  The code would be something like:

Code: [Select]

#!/bin/bash
gcc $*
<Logic to detect output>
ldid -S output
idk, I think ir would work unless I'm missing something.  

[C0deH4cker]

Python FTW!!!!


#!/usr/bin/env python
import os, sys
os.system("realgcc " + " ".join(sys.argv[1:]))
for i in range(0,len(sys.argv)-1):
    if sys.argv == "-o":
        output = sys.argv[i+1]
        break
if not output:
    output = "a.out"

os.system("ldid -S %s" % output)

[Trcx528]

Ya, would something like that work?

[C0deH4cker]

Think so. Havent tested, but it should work.

[LeoTh3o]

No, it doesn't work due a python parse error in "-o". I don't know python, so I can only report the error.