You are not logged in.
- Topics: Active | Unanswered
#1 2009-12-03 00:50:08
- Anikom15
- Banned
- From: United States
- Registered: 2009-04-30
- Posts: 836
- Website
What does the output mean when you're compiling.
Sometimes it's errors, but usually it looks like gibberish, except for the beginning (when it's configure and check) and the end when it's make install. The make part of the building seems to be the CFLAGS printed over and over again. My question is, it goes so fast, what's the point of it?
Personally, I'd rather be back in Hobbiton.
Offline
#2 2009-12-03 00:53:34
- Allan
- Pacman
- From: Brisbane, AU
- Registered: 2007-06-09
- Posts: 11,495
- Website
Re: What does the output mean when you're compiling.
When you do run into an error, it stops and you can then track down the cause.
You get used to the text going by and understand it eventually. All I see now is blonde, brunette, redhead....
Offline
#3 2009-12-03 00:57:51
- foutrelis
- Developer
- From: Athens, Greece
- Registered: 2008-07-28
- Posts: 705
- Website
Re: What does the output mean when you're compiling.
It doesn't mean anything in particular, make just prints the commands used to build the software. cmake on the other hand provides more compact output, only printing what it's doing (compiling/linking) and the filename(s).
Offline
#4 2009-12-03 01:07:50
- sand_man
- Member
- From: Australia
- Registered: 2008-06-10
- Posts: 2,164
Re: What does the output mean when you're compiling.
You get used to the text going by and understand it eventually. All I see now is blonde, brunette, redhead....
I know kung-fu...
Offline
#5 2009-12-03 01:12:47
- olovram
- Member
- Registered: 2008-10-10
- Posts: 110
Re: What does the output mean when you're compiling.
Stop trying to hit me and hit me!
Offline
#6 2009-12-03 01:36:04
- ngoonee
- Forum Fellow
- From: Between Thailand and Singapore
- Registered: 2009-03-17
- Posts: 7,358
Re: What does the output mean when you're compiling.
You're going to have to make a choice... to file a bug-report, OR, NOT to file a bug-report.
The question is... Is there a difference?
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
#7 2009-12-03 01:48:00
- Ranguvar
- Member
- Registered: 2008-08-12
- Posts: 2,563
Re: What does the output mean when you're compiling.
You're going to have to make a choice... to file a bug-report, OR, NOT to file a bug-report.
The question is... Is there a difference?
You're going to have to figure out... is there a difference, or isn't there a difference?
The question is... are the differences different?
Offline
#8 2009-12-03 03:07:22
- skottish
- Forum Fellow
- From: Here
- Registered: 2006-06-16
- Posts: 7,942
Re: What does the output mean when you're compiling.
You're going to have to make a choice... to file a bug-report, OR, NOT to file a bug-report.
The question is... Is there a difference?
There's a certain level of satisfaction that can only be obtained by filing a mission critical bug report and having it ignored by developers. For instance, when I told the Enlightenment developers that their file manager was arbitrarily deleting files... Ahhhh, that felt good.
Offline
#9 2009-12-03 03:26:28
- sand_man
- Member
- From: Australia
- Registered: 2008-06-10
- Posts: 2,164
Re: What does the output mean when you're compiling.
My question is, it goes so fast, what's the point of it?
It makes nerds feel cool. It's all we have.
Offline
#10 2009-12-03 04:28:17
- Trent
- Member
- From: Baltimore, MD (US)
- Registered: 2009-04-16
- Posts: 990
Re: What does the output mean when you're compiling.
When I was installing Gentoo, I actually managed to use make's output to diagnose an odd problem -- xsltproc, I think, was doing something odd, and I managed to narrow it down to that program by watching the output closely.
It's more useful when you have a build that fails and you can pipe the output to a file for later analysis. Not to mention it reassures you that your terminal is doing something and hasn't just locked up on you.
Offline
#11 2009-12-03 14:58:58
- Tjh_
- Member
- From: Waterloo, Canada
- Registered: 2009-11-28
- Posts: 11
- Website
Re: What does the output mean when you're compiling.
To answer the OP's question i think for the most part the output you see is the gcc/g++ commands being used by make. As you may or may not know make is kinda like a script that compiles and links the files, it runs the commands that is set in the makefile, and displayes the commands that is being run at the time. So you may see that a lot of the new commands (or what wouold to most non nerds look like gibberish) have "gcc" or "g++" as the first word and then a whole lot of other junk, which is just options passed to the compiler or linker. And the reason you keep seeing the cflags is cuz it keeps having to pass it to the compiler as options every time it compiles something new, most large programs require a couple of different gcc or g++ commands to get done fully. SO like, compile this file, compile that file, and now link the result together into executable. thats 3 invocations and each one needs to be sent the CFLAGS as options.
Also: allan, i couldn't stop laughing when i read your post lol.
Last edited by Tjh_ (2009-12-03 15:02:04)
Offline