Anant Aneja | 2 Mar 18:20 2003

Inerupts handling

My problem is i was using turbo c++ compiler before and 
frequently
used ROM-BIOS interupts for
certain functions ( like handling the screen, calling the mouse
etc all in dos based programs
using 386 based registers like ah al etc).

Now I've started using gcc and find that even a basic screen
clearing function requires me to use the
"ncurses" library. this i did but it handles the screen only 
using
windows and does not treat the console as an
unlimited buffer.

I dont wanna use the library therefore. plus it was a lot easier
calling interupts for most simple tasks.
I've read somewhere that Linux does not allow BIOS interupts 
since
it runs in 'protected' mode.
therefore, I cant do simple stuff like clearing a screen myself.

Is there some way to do the above task easily (with or without
assembly ?)

Please help.
Anant

Jamie Risk | 5 Mar 21:34 2003
Picon

warnings appearing during preprocessor string concatenation (##)

I have the following line in my code,

#define FEATURE(select)     feature_structure. ## select ## .member
  ...
   FEATURE(test);

and when I run it through the compiler (gcc 3.2.2 on Linux x86) I get the
_warning_

  file.c:111:32: warning: pasting "." and "test" does not give a valid
preprocessing token
  file.c:111:32: warning: pasting "test" and "." does not give a valid
preprocessing token

If I look at the preprocessor output, (gcc's -E option) it produces what I'm
hoping for, although I'd like to avoid the warning.  Suggestions?

- Jamie

Reply to "gmane.linux.c-programming" or me directly.

-
To unsubscribe from this list: send the line "unsubscribe linux-gcc" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Robert Schiele | 6 Mar 14:10 2003
Picon

Re: warnings appearing during preprocessor string concatenation (##)

On Wed, Mar 05, 2003 at 03:34:39PM -0500, Jamie Risk wrote:
> I have the following line in my code,
> 
> #define FEATURE(select)     feature_structure. ## select ## .member
>   ...
>    FEATURE(test);
> 
> and when I run it through the compiler (gcc 3.2.2 on Linux x86) I get the
> _warning_
> 
>   file.c:111:32: warning: pasting "." and "test" does not give a valid
> preprocessing token
>   file.c:111:32: warning: pasting "test" and "." does not give a valid
> preprocessing token
> 
> If I look at the preprocessor output, (gcc's -E option) it produces what I'm
> hoping for, although I'd like to avoid the warning.  Suggestions?

Just remove the '##' operator.  The preprocessor is right here, there
is nothing to concatenate to a token in your example.

Robert

--

-- 
Robert Schiele			Tel.: +49-621-181-2517
Dipl.-Wirtsch.informatiker	mailto:rschiele <at> uni-mannheim.de
Mathur, Shobhit | 20 Mar 02:06 2003

gcc: linker input file unused since linking not done

Hello,

I am facing a problem in compiling my source code with the library
[static library ], which I have created.
Upon specifying the appropriate Include-paths,  Lib-paths, and the
appropriate ".a" to which the programs
should link, I get the error from gcc as mentioned in the subject :

gcc: -ltcfg: linker input file unused since linking not done

where, ltcfg  points to  libtcfg.a, which is a static library generated
by me, whose path is specified by  the "-L" directive.

I would like to know why the above message  appears from  gcc.  If so,
what is the remedy to this problem ?

- Please do let me know what is missing

- Thank you

- Shobhit
-
To unsubscribe from this list: send the line "unsubscribe linux-gcc" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

H. J. Lu | 21 Mar 17:11 2003

Linux binutils 2.13.90.0.20 is released

This is the beta release of binutils 2.13.90.0.20 for Linux, which is
based on binutils 2003 0319 in CVS on sourecs.redhat.com plus various
changes. It is purely for Linux.

The Linux/mips support is added. You have to use

# rpm --target=[mips|mipsel] -ta binutils-xx.xx.xx.xx.xx.tar.gz

to build it. Or you can read mips/README in the source tree to apply
the mips patches and build it by hand.

FYI, the binutils man pages now are generated from the texinfo files
during the build. As the result, those man pages may be changed for
each build even if you only have done

# ..../configure ...
# make

That means you may have many failures on the man pages when you apply
the binutils diffs next time. Those failures can be safely ignored.
You should remove all those man pages from your source tree by

# find -name *.1 | xargs rm -f
# find -name *.1.rej | xargs rm -f
# find -name *.man | xargs rm -f
# find -name *.man.rej | xargs rm -f

Please report any bugs related to binutils 2.13.90.0.20 to hjl <at> lucon.org.

For arm-linux targets, there are some important differences in behaviour 
(Continue reading)

Luciano Moreira - igLnx | 28 Mar 18:08 2003
Picon

Detecting running deamons

I have a application that run like a deamon, which write in a file its PID,
that is used to stop it later by others programs. But, I ve noted that my
users send signal 9 to stop deamons, and my application cannot remove its
PID file, because it cannot handle singal 9, keeping its PID file at HD
(FileSystem).

Can someone sugest me a way to know the deamon's PID, without write it to a
file ?
OR
How can I do to know if my deamon is running and get its PID ?

Thanks,

Luciano

-
To unsubscribe from this list: send the line "unsubscribe linux-gcc" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

J. | 28 Mar 20:18 2003
Picon
Picon

Re: Detecting running deamons

On Fri, 28 Mar 2003, Luciano Moreira - igLnx wrote:

> I have a application that run like a deamon, which write in a file its PID,
> that is used to stop it later by others programs. But, I ve noted that my
> users send signal 9 to stop deamons, and my application cannot remove its
> PID file, because it cannot handle singal 9, keeping its PID file at HD
> (FileSystem).
> 
> Can someone sugest me a way to know the deamon's PID, without write it to a
> file ?
> OR
> How can I do to know if my deamon is running and get its PID ?
> 
On the command-line:
 pidof `which program_name`
or:
 ps aux | grep program_name
or perhaps interactive?:
 top

> Thanks,

No problemo

> Luciano

J.

-
To unsubscribe from this list: send the line "unsubscribe linux-gcc" in
(Continue reading)


Gmane