Problems when running "configure -static" for 4.7.3

[high_flyer]

I stand corrected then.
I'll have to read about it...
But on first thought, I makes little sense.
If you can as a developer elevate your applications rights, what is the point if having them?
If the system can't prohibit my application do access things the system deems as restricted, what is the point?
But this still has nothing to do with static linking (unless the goal is to avoid linking privileged libs? but with admin rights that should not be a problem...)

[wysota]

You can elevate if the system policy lets you (i.e. you know the password or the system is configured to let the particular application gain superuser rights). Nothing to do with static linking though

[high_flyer]

Ok, I still stand by what I said in post#10.
Basically "elevating" boils down to "automating" what I wrote is needed in post#10.

Off topic:
And this here, demonstrates exactly the "non-sense" in allowing such a mechanism...
http://www.withinwindows.com/2009/02...freely-easily/

Yes, its dues to a bug and not a design problem, but who can claim to have written an application (of any serious volume) which is bug free?
Such an feature is asking for security problems IMHO.

[Gokulnathvc]

Actually, i did the static build by opening the command prompt as Administrator, but it fails to do the work after executing. I have tried "Run as administrator" still the same thing occurs. Nothing is happened, just the application window opens.

[Cucus]

Wow thank you very much for your reply Gokulnathvc!
It looks really complete the method you propose. I haven't tried it yet, I finally could manage it to work with version 4.8.0 beta and I saw that it also works with 4.7.4.

[Gokulnathvc]

You Are always welcome..