well, the quick-and-dirty test program I compiled over the weekend produced a file a.out when I did gcc filename.c, so I would assume that this is still the a.out format.
Posted Sep 16, 2008 14:40 UTC (Tue) by proski (subscriber, #104)
[Link]
LOL. You are so funny!
KS2008: Linux 3.0
Posted Sep 16, 2008 14:42 UTC (Tue) by bfields (subscriber, #19510)
[Link]
the quick-and-dirty test program I compiled over the weekend produced a file a.out when I did gcc filename.c, so I would assume that this is still the a.out format.
bfields@pig:~$ cat >test.c
#include <stdio.h>
int main(int argc, char *argv[])
{
printf("hello world\n");
}
bfields@pig:~$ gcc test.c
bfields@pig:~$ file a.out
a.out: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for
GNU/Linux 2.6.8, dynamically linked (uses shared libs), not stripped
(Woah, I just wrote a whole program with "cat >test.c", I must be 133t!)
KS2008: Linux 3.0
Posted Sep 16, 2008 15:19 UTC (Tue) by nix (subscriber, #2304)
[Link]
The real l33t is compiling programs with e.g.
gcc -x c <<'EOF'
...
EOF
:)
KS2008: Linux 3.0
Posted Sep 16, 2008 16:16 UTC (Tue) by im14u2c (subscriber, #5246)
[Link]
What's this "compile" thing folks keep mentioning? The truly l33t prefer to simply "cat > a.out".
KS2008: Linux 3.0
Posted Sep 16, 2008 20:16 UTC (Tue) by nix (subscriber, #2304)
[Link]
Most of us can only *aspire* to be Al Viro.
KS2008: Linux 3.0
Posted Sep 16, 2008 21:20 UTC (Tue) by jengelh (subscriber, #33263)
[Link]
Nah, you can't correct a line once you hit enter. But you can do it in one line: