Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Install an optimized BIND 9.2.3Beta' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Install an optimized BIND 9.2.3Beta
Authored by: uridium on Nov 04, '05 01:50:02PM

If your optimising you can also make it more portable. If you for instance run it over a mix older machines (for instance 750GX g3's) & newer kit (eg g5's) and want a common bin to roll out over {nfs,afp,smb} and have the latest tiger dev tools, you can create a fat binary using MAB's. If you set your CFLAGS to include: "-arch ppc -arch ppc64" this will let you run the same thing in/on 64bit mode on your g5 and in 32bit mode on your g3. OSX's got $CLUE which part to run for which binary without switches. Eg.. simple program dumping word size from sizeof(long):

(on the 32bit 750GX g3-400)
downshift:~ %./mabLuv-arch_DPaction

32 bit

(On the 64bit 970 g5-1.8ghz)
springer:~ %./mabLuv-arch_DPaction

64 bit

As far as $BLOAT factor goes, it's not that bad, here's the file sizes for ppc32bit, ppc64bit and the fat MAB bin:

-rwxr-xr-x 1 uridium uridium 13800 Oct 23 23:43 mabLuv-arch_ppc
-rwxr-xr-x 1 uridium uridium 12688 Oct 23 23:43 mabLuv-arch_ppc64
-rwxr-xr-x 1 uridium uridium 34280 Oct 23 23:42 mabLuv-arch_DPaction

Roughly double. Nice though if your messing with a few dozen or a cluster of machines and have the policy of rolling out a common binary without having to compile on each node.



[ Reply to This | # ]