In article [EMAIL PROTECTED],
Steve Holden [EMAIL PROTECTED] wrote:
If you are seeing alot of error messages you shoudl really redirect the
standard error to a file to avoid them cluttering up your console.
Surely a better technique would be to fix the errors causing the
messages.
--
In article [EMAIL PROTECTED],
Carl J. Van Arsdall [EMAIL PROTECTED] wrote:
Lawrence D'Oliveiro wrote:
In article [EMAIL PROTECTED],
Carl J. Van Arsdall [EMAIL PROTECTED] wrote:
Well, running the make on the command line seems to work just fine, no
errors at all.
What about
Carl J. Van Arsdall wrote:
I'm not sure the proper way to phrase the question, but let me try.
Basically, I'm working with a script where someone wrote:
kr = string.strip(os.popen('make kernelrelease').read())
And then searches kr to match a regular expression.
This seems to have
I'm not sure the proper way to phrase the question, but let me try.
Basically, I'm working with a script where someone wrote:
kr = string.strip(os.popen('make kernelrelease').read())
And then searches kr to match a regular expression.
This seems to have been working, however lately when this
Hello,
I'm not 100% sure on this but to me it looks like there is a problem in
your make file. I would look in there first, see where 'cat' is
executed, I bet your problem will be around there.
Hope this helps,
Colin
Carl J. Van Arsdall wrote:
I'm not sure the proper way to phrase the
cdecarlo wrote:
Hello,
I'm not 100% sure on this but to me it looks like there is a problem in
your make file. I would look in there first, see where 'cat' is
executed, I bet your problem will be around there.
Hope this helps,
Colin
Well, running the make on the command line seems
kr = string.strip(os.popen('make kernelrelease').read())
If make is being executed, I presume that the python script has rw
access to the location. How about
x=os.system(make kernelrelease my_report 21 )
kr=open(my_report).read()
Just a blind throw.
Good luck
sree
--
In article [EMAIL PROTECTED],
Carl J. Van Arsdall [EMAIL PROTECTED] wrote:
Well, running the make on the command line seems to work just fine, no
errors at all.
What about running it as
make kernelrelease | cat
This way the output goes to a pipe, which is what happens when it's
called
Lawrence D'Oliveiro wrote:
In article [EMAIL PROTECTED],
Carl J. Van Arsdall [EMAIL PROTECTED] wrote:
Well, running the make on the command line seems to work just fine, no
errors at all.
What about running it as
make kernelrelease | cat
This way the output goes to a
