My intention is to generate redistributable binaries of a compiler which is a spinoff of Open64. I am doing a ./configure - make - make install on my build machine, and I archived the content of the installdir and moved it to another machine under another user for testing. Upon testing, I see that the copied files still tries to access some files at a path which was at my build machine - and hence I get permissions denied error. Prior to creating a tarball of installdir, I am making all the files as universally +rwx.

I do not have root/sudo privileges. The crux is - how do I build in one machine and use the install-files in many others without running into permissions related problems? What are the rules to create universally distributable tarballs?

Okay, it's the distro that makes the "rules" (if any) in that you need to use the install-tool compatible software for that. On Fedora, for example, you'd use rpmbuild to make an rpm. Debian (and the drivatives) use deb and so on.

If you want to go really distro-independent, you need to go open source, with emphasis on source and either provide a build script (Arch Linux has pkgbuild for that) or rely on the know-how of the (end) user to compile the thing alone.

Thor

Actually at this present moment I am more keen on resolving the "permissions denied" error that is probably happening due to some flaw in my building. It would be great if you could comment on how I could fix it. I am building normally - as in first configure, then make and finally make install.