Linux-Development-Sys Digest #340, Volume #8 Tue, 12 Dec 00 03:13:11 EST
Contents:
Re: Linux GUI programming ("Joshua Schaeffer")
Re: Linux GUI development
Compiling C++ programs with GCC --> no GPL license implications ([EMAIL PROTECTED])
Re: Compiling C++ programs with GCC --> no GPL license implications ("E. Robert
Tisdale")
Re: Compiling C++ programs with GCC --> no GPL license implications (jbs)
usb-storage-question (Konstantinos Agouros)
Re: Compiling C++ programs with GCC --> no GPL license implications (Sam Holden)
Re: Compiling C++ programs with GCC --> no GPL license implications (Kaz Kylheku)
suggest me one which can handle multiple POP3 email addresses? ("news")
Re: suggest me one which can handle multiple POP3 email addresses? (Matthew Palmer)
Re: A faster memcpy and bzero for x86 (Tim Roberts)
Re: missing symbol "_iob" in C libraries ("D. Stimits")
sound recording problem ("Subhash Chandra")
Re: sound recording problem (Kaz Kylheku)
Re: How to optimize the Kernel-Compile (Robert Resch)
Re: how to use raw device (Josef Moellers)
Re: How to optimize the Kernel-Compile (Robert Resch)
Re: missing symbol "_iob" in C libraries (Josef Moellers)
----------------------------------------------------------------------------
From: "Joshua Schaeffer" <[EMAIL PROTECTED]>
Crossposted-To: linux.redhat.development
Subject: Re: Linux GUI programming
Date: Tue, 12 Dec 2000 01:37:43 GMT
> I would like to write a GUI based application, just like I can with
> Windows. As an application and device driver writer, I have been forced
> to use Windows because of the GUI. In all other respects, Linux is
> superior.
As an honest question and not flamebait, why do you feel Linux is superior
to Windows as far as architecture is concerned?
------------------------------
From: <[EMAIL PROTECTED]>
Subject: Re: Linux GUI development
Date: 11 Dec 2000 20:09:16 -0600
> Actually, what you need is a signal processing module that listens to the sound
> card's input and brings down the system when it hears what sounds like a
> sneeze. ;)
Good idea! I should try that with my profs...
==================
john turek
system administrator
computer science department
st. bonaventure university
====== Posted via Newsfeeds.Com, Uncensored Usenet News ======
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
======= Over 80,000 Newsgroups = 16 Different Servers! ======
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.lang.c++,gnu.misc.discuss
Subject: Compiling C++ programs with GCC --> no GPL license implications
Date: Tue, 12 Dec 2000 02:22:15 GMT
Hello All,
I set out on a quest to confirm the licensing that applies to C++
programs compiled with GCC version 2.95.2. The quick answer is
compiling with GCC and linking the GCC libstdc++ library does not cause
the resulting executable to fall under GPL or LGPL. Many of you might
think this was obvious but as you can see from the details below it was
not quite that simple...
Here are the details:
1) Compiling with GCC by itself does not cause any license restrictions
on the resulting binary. This has been well known and can be confirmed
by reading the GPL and LGPL licenses distributed with GCC or posted at
www.gnu.org.
2) However, linking in libraries is a different matter. C++ programs
generally link in libstdc++ and thus the libstdc++ included with GCC
must be checked (FYI: G++ always links in libstdc++)
3) The correct way to verify what license applies to the GCC libstdc++
library is to check all the source files that go into it. [BTW,
uncovering exactly what files go into libstdc++ proved to be somewhat
sticky. I broke the libstdc++.a file into .o files and used the names
of the .o files and the #includes in them to trace all the source files
in libstdc++. An alternative that was suggested to me but which I did
not have time to pursue was to use the -H flag to gcc to list all the
headers included during compilation.]
4) Most of the headers in the GCC libstdc++ sources either have no
license restrictions or, if they are covered by GPL, they contain a
special exception that says:
/* As a special exception, if you link this library with files
compiled with GCC to produce an executable, this does not cause
the resulting executable to be covered by the GNU General Public
License.
This exception does not however invalidate any other reasons why
the executable file might be covered by the GNU General Public
License. */
5) However, I found 1 source file which fell under GPL (./gcc-
2.95.2/include/ansidecl.h) and 2 which fell under LGPL (./gcc-
2.95.2/libio/ioputc.c and ./gcc-2.95.2/libio/stdio/stdio.h) that did
not include any special exception, and thus on the face of it would
cause any executable that linked in libstdc++ to fall under the GPL (as
this is one of the licensing terms within the GPL). This is not good
for commercial programs. [BTW, my .o file name matching mechanism did
lead to one false positive notably: ./gcc-
2.95.2/texinfo/lib/strerror.c. Also there were 5 .o files (cstrio.o,
cstrmain.o, dcomio.o, fcomio.o, ldcomio.o) that were unmatched but
further manual searching of ./gcc/gcc-2.95.2/libstdc++/makefile.in
shows they come from sinst.cc (covered by the "special exception") and
cinst.cc (copyright but no license).]
6) Suspecting these omissions might be an oversight by the creators of
GCC, I contacted [EMAIL PROTECTED] After some back and forth between
myself, [EMAIL PROTECTED], one of the GCC programmers at Redhat, and a
concluding email from Richard Stallman we resolved that:
- these files should have included the special exception,
- at this time we can consider those files to include the special
exception even though it was omitted originally.
Here is the final email reply from Richard Stallman:
>Date: Fri, 8 Dec 2000 09:46:53 -0700 (MST)
>From: Richard Stallman <[EMAIL PROTECTED]>
>To: jason...
>CC: [EMAIL PROTECTED], [EMAIL PROTECTED]
>In-reply-to: <[EMAIL PROTECTED]> (message from
Jason Merrill on 04 Dec 2000 14:11:49 +0000)
>Subject: Re: fwd: licensing: gcc-2.95.2 forces ALL c++ programs to be
GPL?
>
>Jason Merrill on 04 Dec 2000 writes:
>>Ralph Wayland on 01 Dec 2000 writes:
>>> Just to double check, please confirm the following:
>>> 1) The entire libstdc++ library should fall under the
>>> "special exception" clause.
>>
>>Yes.
>>
>>> 2) Which in turn means that all source files that go into libstdc++
>>> should include the "special exception".
>>
>>Yes.
>>
>>> 3) Checking each source file is the correct way to verify licenses
>>> within GCC.
>>
>>Yes.
>>
>>> 4) In a future version of GCC all the files in libstdc++ will
>>> include the "special exception".
>>
>>Yes.
>>
>>> 5) It is ok today for us to consider the entirety of libstdc++
>>> as covered by the "special exception".
>>
>>I would think so, but I can't speak for the FSF on this, and
>>they hold the copyright. Richard?
>
>Yes to all.
>
<remainder of email trimmed for brevity>
Thus if your C++ program does not include any GPL or LGPL code itself,
then compiling with GCC and linking with GCC's libstdc++ does not force
your program to adopt or follow the GPL or LGPL (your program falls
under the special exception clause). QED.
Regards,
Ralph T. Wayland
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: "E. Robert Tisdale" <[EMAIL PROTECTED]>
Crossposted-To: comp.lang.c++,gnu.misc.discuss
Subject: Re: Compiling C++ programs with GCC --> no GPL license implications
Date: Tue, 12 Dec 2000 02:57:13 +0000
[EMAIL PROTECTED] wrote:
> Thus, if your C++ program does not include any GPL or LGPL code itself,
> then compiling with GCC and linking with GCC's libstdc++
> does not force your program to adopt or follow the GPL or LGPL
> (your program falls under the special exception clause). QED.
Unfortunately, you are not the final authority on this.
If you distribute an executable which was compiled with GCC
and linked to the GNU libraries someone may still sue you
to force you to disclose your source code as well.
You may be obliged to defend your right
to prevent other people from exploiting your source code
and you may even be obliged to defend your right
to exploit your own source code. The court will decide.
And, until some court does decide such a case,
Richard Stallman is just expressing his opinion
about what the GPL and the LGPL mean.
------------------------------
From: jbs <[EMAIL PROTECTED]>
Crossposted-To: comp.lang.c++,gnu.misc.discuss
Subject: Re: Compiling C++ programs with GCC --> no GPL license implications
Date: Mon, 11 Dec 2000 19:09:46 -0800
"E. Robert Tisdale" wrote:
> If you distribute an executable which was compiled with GCC
> and linked to the GNU libraries someone may still sue you
> to force you to disclose your source code as well.
Who has legitimate standing to sue you? Doesn't FSF hold the copyright
on those files?
------------------------------
From: [EMAIL PROTECTED] (Konstantinos Agouros)
Subject: usb-storage-question
Date: 11 Dec 2000 21:17:16 +0100
Hi,
I just tried my Casio-Digi-Cam which has USB-Support together with the
usb-storage module. It is recognized, but how do I mount/access the data?
Konstantin
--
Dipl-Inf. Konstantin Agouros aka Elwood Blues. Internet: [EMAIL PROTECTED]
Otkerstr. 28, 81547 Muenchen, Germany. Tel +49 89 69370185
============================================================================
"Captain, this ship will not sustain the forming of the cosmos." B'Elana Torres
------------------------------
From: [EMAIL PROTECTED] (Sam Holden)
Crossposted-To: comp.lang.c++,gnu.misc.discuss
Subject: Re: Compiling C++ programs with GCC --> no GPL license implications
Date: 12 Dec 2000 04:03:12 GMT
Reply-To: [EMAIL PROTECTED]
On Tue, 12 Dec 2000 02:57:13 +0000, E. Robert Tisdale <[EMAIL PROTECTED]> wrote:
>[EMAIL PROTECTED] wrote:
>
>> Thus, if your C++ program does not include any GPL or LGPL code itself,
>> then compiling with GCC and linking with GCC's libstdc++
>> does not force your program to adopt or follow the GPL or LGPL
>> (your program falls under the special exception clause). QED.
>
>Unfortunately, you are not the final authority on this.
>If you distribute an executable which was compiled with GCC
>and linked to the GNU libraries someone may still sue you
>to force you to disclose your source code as well.
>You may be obliged to defend your right
>to prevent other people from exploiting your source code
>and you may even be obliged to defend your right
>to exploit your own source code. The court will decide.
>And, until some court does decide such a case,
>Richard Stallman is just expressing his opinion
>about what the GPL and the LGPL mean.
The FSF owns the copyright (I believe). RMS's opinion in this
case can presumably be taken to be the FSF opinion.
If the copyright holder says that the special exception clause
applies, then it applies...
--
Sam Holden
------------------------------
From: [EMAIL PROTECTED] (Kaz Kylheku)
Crossposted-To: comp.lang.c++,gnu.misc.discuss
Subject: Re: Compiling C++ programs with GCC --> no GPL license implications
Reply-To: [EMAIL PROTECTED]
Date: Tue, 12 Dec 2000 04:08:51 GMT
On 12 Dec 2000 04:03:12 GMT, Sam Holden <[EMAIL PROTECTED]> wrote:
>On Tue, 12 Dec 2000 02:57:13 +0000, E. Robert Tisdale <[EMAIL PROTECTED]> wrote:
>>to exploit your own source code. The court will decide.
>>And, until some court does decide such a case,
>>Richard Stallman is just expressing his opinion
>>about what the GPL and the LGPL mean.
>
>The FSF owns the copyright (I believe). RMS's opinion in this
>case can presumably be taken to be the FSF opinion.
>
>If the copyright holder says that the special exception clause
>applies, then it applies...
Tisdale is a known troll. Save your keystrokes.
------------------------------
From: "news" <[EMAIL PROTECTED]>
Subject: suggest me one which can handle multiple POP3 email addresses?
Date: Tue, 12 Dec 2000 13:11:22 +0900
I have installed RedHat 6. It's working fine. The KDE can handle dialup very
efficiently. But I need an email client. I have visited the site.
can anyone suggest me one which can handle multiple POP3 email addresses?
Thank you in advance.
Joarder
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Matthew Palmer)
Subject: Re: suggest me one which can handle multiple POP3 email addresses?
Reply-To: [EMAIL PROTECTED]
Date: 12 Dec 2000 16:24:08 +1100
news is of the opinion:
>I have installed RedHat 6. It's working fine. The KDE can handle dialup very
>efficiently. But I need an email client. I have visited the site.
>
>can anyone suggest me one which can handle multiple POP3 email addresses?
fetchmail does quite nicely for me.
--
=======================================================================
#include <disclaimer.h>
Matthew Palmer
[EMAIL PROTECTED]
------------------------------
From: Tim Roberts <[EMAIL PROTECTED]>
Subject: Re: A faster memcpy and bzero for x86
Date: Mon, 11 Dec 2000 22:30:02 -0800
[EMAIL PROTECTED] (bill davidsen) wrote:
>
> Clock speed comparisons between two chips based on totally diferent
>cores, even if they execute the same instructions, is essentially
>meaningless. We heard that about the Pentium and 486 as well, only no
>one ran their pentium at 66MHz.
Sure they did. The first Pentiums were 60MHz, 66Mhz and 75MHz.
>And I suspect by that definition the 486
>would beat the P-III today, if you ran them at the same speed.
Actually, this one is demonstrably untrue. The 486 required multiple
cycles for almost every instruction. Even at identical clock rates, the
Pentium gets more done per cycle.
--
- Tim Roberts, [EMAIL PROTECTED]
Providenza & Boekelheide, Inc.
------------------------------
Date: Mon, 11 Dec 2000 23:33:18 -0700
From: "D. Stimits" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: missing symbol "_iob" in C libraries
Mohammad Donyaee wrote:
>
> Hi guys,
> I am trying to port my application from Venix(a System V flavor OS) to Linux
> Redhat 6.0, this application uses a library to do DOS operation, but I do
> not have library source code, just I have the archive file, libdos.a, using
> a utility I converted object files in this library from XCOFF to ELF, then
> Linux can read the object files, but during link, it looks for some missing
> symbols such as "_iob", "_flsbuf", "_filbuf","__fltused", apparently these
Typical is for functions starting with underscore "_" to be
non-portable. Your library itself must make calls to linux libararies,
and conversion of format does not mean the functions actually exist.
> symbols do not exist in C libraries of Linux. any idea is welcome on the
> following:
> 1) Am I wrong to try to convert this library and use it on another OS?
Very unlikely to work. Maybe if you run it under an emulator in its
native format, but not directly.
> 2) Where can I find information about the job of those missing symbols?
See the man pages for ld; related utilities ldd, objdump, and nm.
Missing symbols are functions that must be implemented somewhere. Linux
doesn't implement the non-portable Venix or DOS functions (POSIX
functions you have a good bet they are implemented).
> 3) Any idea to compile my application without having to write DOS library
> from scratch?
Find out what those functions do. Possibly you could get away with just
writing those (the symbols are functions). But they sound like they may
not have any public information on them. You're probably out of luck
with a direct approach; if an emulator is available you might be in
luck.
> In advance thanks to all experts who contribute to the newsgroup.
> Regards
> MDonyaee
------------------------------
From: "Subhash Chandra" <[EMAIL PROTECTED]>
Subject: sound recording problem
Date: Tue, 12 Dec 2000 12:11:07 +0530
Hi,
I have sb pci 128 sound card (ES1371) on red hat 6.2 (2.2.14).
All the playback is taking place properly. But I am unable to record from
the micro phone.
even following commands are not working.
cat /dev/dsp > myvoice
then cat myvoice > /dev/dsp
Some noise is getting recorded. I used few application to record but the
result is same.
Some one pls tell me what is wrong?
Thanx,
Subhash.
------------------------------
From: [EMAIL PROTECTED] (Kaz Kylheku)
Subject: Re: sound recording problem
Reply-To: [EMAIL PROTECTED]
Date: Tue, 12 Dec 2000 06:43:24 GMT
On Tue, 12 Dec 2000 12:11:07 +0530, Subhash Chandra <[EMAIL PROTECTED]> wrote:
>Hi,
>
>I have sb pci 128 sound card (ES1371) on red hat 6.2 (2.2.14).
>All the playback is taking place properly. But I am unable to record from
>the micro phone.
Perhaps the microphone input is not enabled or the gain is too low or muted.
Use a mixer program like aumix to enable recording and adjust the gain.
------------------------------
From: Robert Resch <[EMAIL PROTECTED]>
Subject: Re: How to optimize the Kernel-Compile
Date: Tue, 12 Dec 2000 08:36:27 +0100
[EMAIL PROTECTED] wrote:
>
> Robert Resch <[EMAIL PROTECTED]> wrote:
> > I want to use a 486 DX-2-66 as a router. For a little more performance i
> > want to compile the Kernel for 486.
> > I've modified all Makefile 's from '-O2' to '-O9 -march=i486 -mcpu=i486'
> > but the kernel doesn't start.
>
> > What modification options can be used in a 2.2.17 Kernel?
>
> There is, in fact, an option to select the cpu type in 'make config'
> (or whatever configuration target you used).
That's not the opton i'm searching for - i've already fount the one you
mention.
i want to optimize for 486 with the _best_ speed- and memory options.
Robert
------------------------------
From: Josef Moellers <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps,linux.dev.kernel
Subject: Re: how to use raw device
Date: Tue, 12 Dec 2000 08:31:39 +0100
Marty wrote:
> =
> I would like to ask how to use the raw device to read/write ???
> =
> I have used the raw function on a SCSI hard disk like this : raw
> /dev/raw/raw1 /dev/sda1
> =
> then, how do I issue read/write call on this raw device?
> I have tried to issue the conventional system call open and read but fa=
iled.
> =
> fd =3D open("/dev/raw/raw1", O_RDONLY);
> read(fd, buf, 4096);
> =
> what is the correct way to read/write ???
ca depend, as the French use to say.
It depends on which kernel version you use. 2.2 kernels don't have raw
devices. If you checked the return value of the open call, you'd get the
message:
fd =3D open("/dev/raw/raw1", O_RDONLY);
if (fd =3D=3D -1)
{
perror("/dev/raw/raw1");
return; /* or exit(1) or whatever */
}
Apparently 2.4 kernels do have raw devices, so read() and write() should
both work.
Again, you should check the return values from open() and read(), this
time.
-- =
Josef M=F6llers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize (T. Pratchett)
------------------------------
From: Robert Resch <[EMAIL PROTECTED]>
Subject: Re: How to optimize the Kernel-Compile
Date: Tue, 12 Dec 2000 08:35:01 +0100
juergen Heinzl wrote:
>
> In article <[EMAIL PROTECTED]>, Robert Resch wrote:
> >Hi!
> >
> >I want to use a 486 DX-2-66 as a router. For a little more performance i
> >want to compile the Kernel for 486.
> >I've modified all Makefile 's from '-O2' to '-O9 -march=i486 -mcpu=i486'
> >but the kernel doesn't start.
> [-]
> You can modify the Makefile's until the cows come home, but -O3 is the
> limit anyway.
>
> >What modification options can be used in a 2.2.17 Kernel?
> [-]
> You might have triggered a compiler bug and the next question is which
> compiler do you use to compile the kernel ? At least 2.7.2.3 does not
> understand -march=... -mcpu=... and I can't remember whether egcs-1.n.m
> does.
I use the GCC 2.95.2. The Compiler recognizes the flags but the kernel
won't boot...
Optimizing in the 'make menuconfig' Script does only use the
'-mcpu='-flag in the shorter Version '-m486'
but i want to optimize for my 486 in everything and not only the
scheduler as the -m486 does.
Robert
------------------------------
From: Josef Moellers <[EMAIL PROTECTED]>
Subject: Re: missing symbol "_iob" in C libraries
Date: Tue, 12 Dec 2000 08:49:01 +0100
Mohammad Donyaee wrote:
> =
> Hi guys,
> I am trying to port my application from Venix(a System V flavor OS) to =
Linux
> Redhat 6.0, this application uses a library to do DOS operation, but I =
do
> not have library source code, just I have the archive file, libdos.a, u=
sing
> a utility I converted object files in this library from XCOFF to ELF, t=
hen
> Linux can read the object files, but during link, it looks for some mis=
sing
> symbols such as "_iob", "_flsbuf", "_filbuf","__fltused", apparently th=
ese
> symbols do not exist in C libraries of Linux. any idea is welcome on th=
e
> following:
> 1) Am I wrong to try to convert this library and use it on another OS?
> 2) Where can I find information about the job of those missing symbols?=
> 3) Any idea to compile my application without having to write DOS libra=
ry
> from scratch?
> In advance thanks to all experts who contribute to the newsgroup.
> Regards
> MDonyaee
Very often, these libraries implement UN*X style functions, i.e. the
system calls (read(), write(), open(), close(), ...), and library
functions (printf(), strchr(), ...)
The symbols you mention (_iob, _flsbuf, _filbuf) come from the stdio
context. I guess that __fltused is just an identifier signalling to some
function that your application uses floating point math. =
The first approach would be to try and see if you can compile and link
the application without linking in your library. It may work.
If not, it may help looking at the symbol table of the unlinked object
modules (running "nm" on the .o files and filtering this through fgrep
to find the unresolved externals: fgrep ' U ') or just leaving out the
old library and looking at the error messages of the linker will tell
you what functions you might need. In the extreme case you will have to
sift through your application's code to see what external functions it
uses and how it uses them. =
This last step may even be necessary anyway because porting an
application from DOS to Linux is more than just recompiling the source
code. Porting from one 32 bit environment to another is a minor hassle
compared to porting from a 16 bit environment with a visable segmented
memory architecture to a 32 bit environment with a flat memory
structure, which is a major project. DOS programs not only explicitly
handle segment numbers (look for SEG() macros and "far" attributes to
pointers), they also assume that ints and pointers are 16 bits. These
subtleties tend to hide in places where you don't expect them.
I sincerely wish you good luck and ... be carefull,
-- =
Josef M=F6llers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize (T. Pratchett)
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list by posting to the
comp.os.linux.development.system newsgroup.
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Development-System Digest
******************************
