I cannot compile gtk apps after updating to 18.04





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







1















I try to compile a program with a user interface as a .out file, and I compiled it just the same way before and I did not edit the code, using this



`pkg-config --cflags --libs gtk+-2.0`


Back in 16.04, the code compiled into an application and I could double click and launch the app. This time, I can`t When I douuble click, it tries to open with glade and shows an error. For some reason, the compiler or the system thinks the file is supposed to be a shared library. How can I tell it to be an application? I have to execute it in the terminal like a non gtk compiled c file.



How can I compile it as an app on 18.04?



somebody heeeeeEEEEEEEEELP MEEEEEEEEEEEEE!










share|improve this question




















  • 2





    As of gcc-6.2 gcc is configured with the --enable-default-pie option, that's why it's a shared object. This shouldn't normally prevent executing the file. (take a look in /usr/bin) I guess you could try using the respective compile & link options of -fno-pie -no-pie

    – doug
    Feb 23 at 21:12











  • @doug consider to write your method as answer. Really gcc hello.c `pkg-config --cflags --libs gtk+-2.0` -no-pie allows a.out to be executable from file-manager.

    – N0rbert
    Feb 23 at 21:27


















1















I try to compile a program with a user interface as a .out file, and I compiled it just the same way before and I did not edit the code, using this



`pkg-config --cflags --libs gtk+-2.0`


Back in 16.04, the code compiled into an application and I could double click and launch the app. This time, I can`t When I douuble click, it tries to open with glade and shows an error. For some reason, the compiler or the system thinks the file is supposed to be a shared library. How can I tell it to be an application? I have to execute it in the terminal like a non gtk compiled c file.



How can I compile it as an app on 18.04?



somebody heeeeeEEEEEEEEELP MEEEEEEEEEEEEE!










share|improve this question




















  • 2





    As of gcc-6.2 gcc is configured with the --enable-default-pie option, that's why it's a shared object. This shouldn't normally prevent executing the file. (take a look in /usr/bin) I guess you could try using the respective compile & link options of -fno-pie -no-pie

    – doug
    Feb 23 at 21:12











  • @doug consider to write your method as answer. Really gcc hello.c `pkg-config --cflags --libs gtk+-2.0` -no-pie allows a.out to be executable from file-manager.

    – N0rbert
    Feb 23 at 21:27














1












1








1








I try to compile a program with a user interface as a .out file, and I compiled it just the same way before and I did not edit the code, using this



`pkg-config --cflags --libs gtk+-2.0`


Back in 16.04, the code compiled into an application and I could double click and launch the app. This time, I can`t When I douuble click, it tries to open with glade and shows an error. For some reason, the compiler or the system thinks the file is supposed to be a shared library. How can I tell it to be an application? I have to execute it in the terminal like a non gtk compiled c file.



How can I compile it as an app on 18.04?



somebody heeeeeEEEEEEEEELP MEEEEEEEEEEEEE!










share|improve this question
















I try to compile a program with a user interface as a .out file, and I compiled it just the same way before and I did not edit the code, using this



`pkg-config --cflags --libs gtk+-2.0`


Back in 16.04, the code compiled into an application and I could double click and launch the app. This time, I can`t When I douuble click, it tries to open with glade and shows an error. For some reason, the compiler or the system thinks the file is supposed to be a shared library. How can I tell it to be an application? I have to execute it in the terminal like a non gtk compiled c file.



How can I compile it as an app on 18.04?



somebody heeeeeEEEEEEEEELP MEEEEEEEEEEEEE!







command-line compiling gtk c glade






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 23 at 20:59







90 98

















asked Feb 23 at 20:26









90 9890 98

83




83








  • 2





    As of gcc-6.2 gcc is configured with the --enable-default-pie option, that's why it's a shared object. This shouldn't normally prevent executing the file. (take a look in /usr/bin) I guess you could try using the respective compile & link options of -fno-pie -no-pie

    – doug
    Feb 23 at 21:12











  • @doug consider to write your method as answer. Really gcc hello.c `pkg-config --cflags --libs gtk+-2.0` -no-pie allows a.out to be executable from file-manager.

    – N0rbert
    Feb 23 at 21:27














  • 2





    As of gcc-6.2 gcc is configured with the --enable-default-pie option, that's why it's a shared object. This shouldn't normally prevent executing the file. (take a look in /usr/bin) I guess you could try using the respective compile & link options of -fno-pie -no-pie

    – doug
    Feb 23 at 21:12











  • @doug consider to write your method as answer. Really gcc hello.c `pkg-config --cflags --libs gtk+-2.0` -no-pie allows a.out to be executable from file-manager.

    – N0rbert
    Feb 23 at 21:27








2




2





As of gcc-6.2 gcc is configured with the --enable-default-pie option, that's why it's a shared object. This shouldn't normally prevent executing the file. (take a look in /usr/bin) I guess you could try using the respective compile & link options of -fno-pie -no-pie

– doug
Feb 23 at 21:12





As of gcc-6.2 gcc is configured with the --enable-default-pie option, that's why it's a shared object. This shouldn't normally prevent executing the file. (take a look in /usr/bin) I guess you could try using the respective compile & link options of -fno-pie -no-pie

– doug
Feb 23 at 21:12













@doug consider to write your method as answer. Really gcc hello.c `pkg-config --cflags --libs gtk+-2.0` -no-pie allows a.out to be executable from file-manager.

– N0rbert
Feb 23 at 21:27





@doug consider to write your method as answer. Really gcc hello.c `pkg-config --cflags --libs gtk+-2.0` -no-pie allows a.out to be executable from file-manager.

– N0rbert
Feb 23 at 21:27










1 Answer
1






active

oldest

votes


















0














As of gcc-6.2 gcc in Ubuntu is configured with the --enable-default-pie option, (Position Independent Executable), that's why it's a shared object. (- LSB shared object



The compiler override for this is -fno-pie , the linker override is -no-pie



Apparently for an a.out file you only need to apply the linker -no-pie though both options together also work.



Also a factor may be your file manager, some will allow marking & running the shared object as exectubale. Nautilus doesn't anymore.(nemo does






share|improve this answer


























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1120702%2fi-cannot-compile-gtk-apps-after-updating-to-18-04%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    As of gcc-6.2 gcc in Ubuntu is configured with the --enable-default-pie option, (Position Independent Executable), that's why it's a shared object. (- LSB shared object



    The compiler override for this is -fno-pie , the linker override is -no-pie



    Apparently for an a.out file you only need to apply the linker -no-pie though both options together also work.



    Also a factor may be your file manager, some will allow marking & running the shared object as exectubale. Nautilus doesn't anymore.(nemo does






    share|improve this answer






























      0














      As of gcc-6.2 gcc in Ubuntu is configured with the --enable-default-pie option, (Position Independent Executable), that's why it's a shared object. (- LSB shared object



      The compiler override for this is -fno-pie , the linker override is -no-pie



      Apparently for an a.out file you only need to apply the linker -no-pie though both options together also work.



      Also a factor may be your file manager, some will allow marking & running the shared object as exectubale. Nautilus doesn't anymore.(nemo does






      share|improve this answer




























        0












        0








        0







        As of gcc-6.2 gcc in Ubuntu is configured with the --enable-default-pie option, (Position Independent Executable), that's why it's a shared object. (- LSB shared object



        The compiler override for this is -fno-pie , the linker override is -no-pie



        Apparently for an a.out file you only need to apply the linker -no-pie though both options together also work.



        Also a factor may be your file manager, some will allow marking & running the shared object as exectubale. Nautilus doesn't anymore.(nemo does






        share|improve this answer















        As of gcc-6.2 gcc in Ubuntu is configured with the --enable-default-pie option, (Position Independent Executable), that's why it's a shared object. (- LSB shared object



        The compiler override for this is -fno-pie , the linker override is -no-pie



        Apparently for an a.out file you only need to apply the linker -no-pie though both options together also work.



        Also a factor may be your file manager, some will allow marking & running the shared object as exectubale. Nautilus doesn't anymore.(nemo does







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Mar 12 at 21:02

























        answered Feb 23 at 22:14









        dougdoug

        14.3k13553




        14.3k13553






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1120702%2fi-cannot-compile-gtk-apps-after-updating-to-18-04%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Biblatex bibliography style without URLs when DOI exists (in Overleaf with Zotero bibliography)

            ComboBox Display Member on multiple fields

            Is it possible to collect Nectar points via Trainline?