Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

gcc & make - aaaagh!

  • 01-02-2002 6:57pm
    #1
    Closed Accounts Posts: 2,349 ✭✭✭


    I just put Tiny Linux on an old 386 (it's based on slackware 4.0). As you know, slackware is never without a problem. It didn't install GCC or make, so I was thinking "wtf am I gonna do? how the hell am I gonna install anything". So after 2 whole minutes of hardcore thinking, I decided I'd download the binaries for GCC, and that worked fine.

    So i try to install make again with ./configure and I get something the likes of:

    checking for GCC.... yes
    checking if GCC works...
    GCC can't compile binaries.

    It's something like that except slightly more technical. So I figure it's to do with GCC not installing the header files. So I stroll my ass back to the windows machine and download glibc so I can install the header files. And what do I need to install it? make. So, feeling mighty puzzled I look for some make binaries so I won't need GCC to install it. I find these ELF binaries, and don't have a clue what they are. So I unpack them and run /usr/bin/make, which returns a segmentation fault.

    If you didn't really get that, basically i'm stuck in kind of a loop where I need glibc to install make and make to install gcc. What the hell do I do?


Comments

  • Closed Accounts Posts: 2,349 ✭✭✭nobodythere


    aaah! who put my sig like that. That's too prolonged and overused!


  • Closed Accounts Posts: 5,564 ✭✭✭Typedef


    Originally posted by grasshopa I just put Tiny Linux on an old 386 (it's based on slackware 4.0). As you know, slackware is never without a problem.
    Maybe you are living in a parallel universe but slackware ist der uber os.
    It didn't install GCC or make, so I was thinking "wtf am I gonna do? how the hell am I gonna install anything". So after 2 whole minutes of hardcore thinking, I decided I'd download the binaries for GCC, and that worked fine.
    Above: Is this the second time you are reading this? if so read below. Ye can't run elf binaries in an aout kernel ye ninny ok? GNU HURD.

    I think you may find that ther kernel you are using is an aout kernel as opposed to an elf kernel so ye won't be able to run elf binary or (program file) on aout, aout runs in elf tho I think, so either upgrade your kernel to an elf kernel or get a gcc binary based on aout, simple really no? ..... so it follows if you download the gcc package that the small linux guide recommends... you 'should' be ok, I dunno. The thing is unless you have a really small hard disk you 'should' be able to get away with installing 7.1 onto a hard drive and then connecting that same hard drive to the 386. I my self was running slack 7.1 as dhcp and internet portal on a 386 with 3.7 mb of ram so you see even though it might be slow, it will still preform a decent function ... if you let it.
    So i try to install make again with ./configure and I get something the likes of:

    checking for GCC.... yes
    checking if GCC works...
    GCC can't compile binaries.
    Below:
    Have you read above ? Read above if not.
    Now read above.

    It's something like that except slightly more technical. So I figure it's to do with GCC not installing the header files. So I stroll my ass back to the windows machine and download glibc so I can install the header files. And what do I need to install it? make. So, feeling mighty puzzled I look for some make binaries so I won't need GCC to install it. I find these ELF binaries, and don't have a clue what they are. So I unpack them and run /usr/bin/make, which returns a segmentation fault.

    bahhh have you read above, no cheating


    Me thinks slackware has provided an uber package for a nice aout kernel back in the day and stuff, you might want to check that out. I don't think I will search for the exact reference ..... if you mount your floppy disk from small linux and read the file that says readme or install or something I have a vague impression the guy who made small linux has some reference as to where you will find the relevant gcc package. I don't remember where.


  • Banned (with Prison Access) Posts: 16,659 ✭✭✭✭dahamsta


    As you know, slackware is never without a problem.

    Haha! Bite me Typedef!

    heh

    adam


  • Closed Accounts Posts: 5,564 ✭✭✭Typedef


    adam, if you insist on renaming yourself grasshoppa just to troll on about slackware's infallability ..... (or was that me) at least be less obvious about it.

    gcc `adams-a-troll --cflags --libs` -mpreferred-stack-boundary=red_hat -o fek off_red_hat_sux.c


  • Banned (with Prison Access) Posts: 16,659 ✭✭✭✭dahamsta


    echo "YORE MA"

    heh


  • Advertisement
  • Closed Accounts Posts: 5,564 ✭✭✭Typedef


    033.jpg
    ping -f
    phone jacked


  • Closed Accounts Posts: 2,349 ✭✭✭nobodythere


    I explained that badly. I have GCC binaries working fine without libraries, so make won't compile, so how do i compile glibc without make to create make?


  • Closed Accounts Posts: 5,564 ✭✭✭Typedef


    Perhaps I'm stating something entirely obvious like (SLACKWARE IT DER UBER-OS) but what you are asking does not seem possible now does it? Ergo get a precompiled gmake and precompiled c libs, from the same place as you got the aout version of gcc¿ That seems logical enough don't it.


Advertisement