Shermin Anwar wrote:
> Hi,
> I am trying to compile rastertoescp.c file in CUPS DDK 1.2.3.Its a
> default filter with cups.I just wanted to compile that filter file .I am
> using Fedora 7.I am sure that these errors are due to include path
> changes not with the file since it is a already compiled file.I have gcc
> working in my machine.But filter is not compiling.
Oh dear, that's a shame.
You've really not given us _anything_ to go on.. I'd ask again but I'm out of
energy.. really..
I'll note you apparently did not read the document I pointed you towards.. I'll
quote two passages
from it that I suspect might be worth your while.
<Quote 1>
Be precise and informative about your problem
* Describe the symptoms of your problem or bug carefully and clearly.
* Describe the environment in which it occurs (machine, OS, application,
whatever). Provide
your vendor's distribution and release level (e.g.: “Fedora Core 7”, “Slackware
9.1”, etc.).
* Describe the research you did to try and understand the problem before
you asked the question.
* Describe the diagnostic steps you took to try and pin down the problem
yourself before you
asked the question.
* Describe any possibly relevant recent changes in your computer or
software configuration.
Do the best you can to anticipate the questions a hacker will ask, and answer
them in advance in
your request for help.
</Quote 1>
<Quote 2>
Describe the problem's symptoms, not your guesses
It's not useful to tell hackers what you think is causing your problem. (If
your diagnostic theories
were such hot stuff, would you be consulting others for help?) So, make sure
you're telling them the
raw symptoms of what goes wrong, rather than your interpretations and theories.
Let them do the
interpretation and diagnosis. If you feel it's important to state your guess,
clearly label it as
such and describe why that answer isn't working for you.
Stupid:
I'm getting back-to-back SIG11 errors on kernel compiles, and suspect a
hairline crack on one
of the motherboard traces. What's the best way to check for those?
Smart:
My home-built K6/233 on an FIC-PA2007 motherboard (VIA Apollo VP2 chipset)
with 256MB Corsair
PC133 SDRAM starts getting frequent SIG11 errors about 20 minutes after
power-on during the course
of kernel compiles, but never in the first 20 minutes. Rebooting doesn't
restart the clock, but
powering down overnight does. Swapping out all RAM didn't help. The relevant
part of a typical
compile session log follows.
Since the preceding point seems to be a tough one for many people to grasp,
here's a phrase to
remind you: "All diagnosticians are from Missouri." That US state's official
motto is "Show me"
(earned in 1899, when Congressman Willard D. Vandiver said "I come from a
country that raises corn
and cotton and cockleburs and Democrats, and frothy eloquence neither convinces
nor satisfies me.
I'm from Missouri. You've got to show me.") In diagnosticians' case, it's not a
matter of
skepticism, but rather a literal, functional need to see whatever is as close
as possible to the
same raw evidence that you see, rather than your surmises and summaries. Show
us.
</Quote 2>
Brad (Walks away whistling "Always look on the bright side of life" fully
anticipating a detailed
description of the problem, how it's invoked and what it says - knowing full
well he's liable to be
sorely disappointed)
--
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/dubailug/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/dubailug/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
