linux-gcc-digest Friday, 26 February 1999 Volume 01 : Number 362
In this issue:
Re: FTP site for crypt code
Re: Question about new software (free web space)
Re: FTP site for crypt code
Re. array access
RE: Re. array access
Re: Re. array access
Re: Re. array access
RE: Re. array access
RE: Re. array access
Notice to all Mobile Phone Users!
Device Driver Info
Re: Device Driver Info
Re: Device Driver Info
Re: Device Driver Info
The New Bible of Dating!! (x11)
Re: C++ Destructor Question
Re: C++ Destructor Question
RE: C++ Destructor Question
Re: C++ Destructor Question
gdb 4.17.0.11 is released.
ADV: ALASKAN TRAVEL
How can get users' information of linux server?
: undefined symbol: __register_frame_info
Re: : undefined symbol: __register_frame_info
gcc-2.8.x & Linux 2.2
Re: gcc-2.8.x & Linux 2.2
Re: : undefined symbol: __register_frame_info
2.2.1 header conflicts
Re: 2.2.1 header conflicts
Re: 2.2.1 header conflicts
Re: 2.2.1 header conflicts
How can I set DNS server?
binutils 2.9.1.0.21 is released.
pointers on how to write device driver?
Re: pointers on how to write device driver?
binutils 2.9.1.0.22b is released.
See the end of the digest for information on subscribing to the linux-gcc
or linux-gcc-digest mailing lists.
----------------------------------------------------------------------
From: Geoff Keating <[EMAIL PROTECTED]>
Date: Tue, 9 Feb 1999 16:57:40 +1100
Subject: Re: FTP site for crypt code
> Date: Mon, 8 Feb 1999 16:33:29 +0100 (MET)
> From: Torsten Duwe <[EMAIL PROTECTED]>
> Cc: GNU libc testers <[EMAIL PROTECTED]>,
> VGER gcc list <[EMAIL PROTECTED]>
> Reply-to: [EMAIL PROTECTED]
>
>
> Ulrich> Hi, I'm ready to release glibc 2.1 for now three days but can't
> Ulrich> do this because we don't have the crypt add-on in place.
> [...]
> Ulrich> So, if you have a non-US FTP server large enough to handle a few
> [...]
>
> What is your problem ? Does glibc-crypt contain more than DES ? In case you
> missed it -- US export restrictions have been loosened last fall, up to 56
> bit encryptions are free to go, unless the downloader sits in Cuba, the Iraq,
> Iran, Libya or the like.
You need to re-read the actual regulations.
Let's see. You probably mean the December changes, not the September
ones which only applied to financial institutions (the December
changes were announced in September). In that case, the clause you're
looking for is CFR 740.17 (a) (3) (ii):
(ii) Eligible commodities and software. (A) Mass market and non-
mass market encryption commodities and non-mass market software having
symmetric algorithms with key lengths up to and including 56-bits, such
as DES or equivalent (such as RC2, RC4, RC5, and CAST) which are
classified as a result of a technical review (see paragraph (c) of this
section). The commodity or software must not allow the alteration of
the cryptographic functionality by the user or any other program.
Encryption chips, integrated circuits, toolkits and executable or
linkable modules are not authorized for export under the provisions of
paragraph (a)(3).
Since the GNU C library is, by definition, a toolkit and/or a linkable
module, and it most certainly allows the user to alter its
functionality, it would not be permitted to be exported under this
licence exemption.
- --
Geoffrey Keating <[EMAIL PROTECTED]>
------------------------------
From: Andre Majorel <[EMAIL PROTECTED]>
Date: Tue, 09 Feb 1999 09:17:28
Subject: Re: Question about new software (free web space)
At 11:11 1999.02.08 -0800, Adam Wiggins wrote:
>If you don't have your own web space, there are several of sites which are
>devoted to giving space to open source projects. I don't know any right
>off hand, but I've seen them listed on slashdot.org in the past.
Linuxbox. They're commercial but they offer free services for logiciel
libre (a.k.a. free software a.k.a. open source software) The exact URL
is (I think) http://rocko.linuxbox.com/.
Andr� Majorel <[EMAIL PROTECTED]>
http://www.teaser.fr/~amajorel/
------------------------------
From: Torsten Duwe <[EMAIL PROTECTED]>
Date: Tue, 9 Feb 1999 11:01:08 +0100 (MET)
Subject: Re: FTP site for crypt code
Geoff> You need to re-read the actual regulations.
Hm, looks like, apparently.
Geoff> clause you're looking for is CFR 740.17 (a) (3) (ii):
That's right, I thought I was referring to that.
Geoff> paragraph (c) of this section). The commodity or software must not
Geoff> allow the alteration of the cryptographic functionality by the
Geoff> user or any other program. Encryption chips, integrated circuits,
Geoff> toolkits and executable or linkable modules are not authorized for
Geoff> export under the provisions of paragraph (a)(3).
I only read "Encryption chips" and ICs; "Toolkits and [...] modules" escaped
my attention. Anyone who wonders how that can happen is encouraged to read
the whole Register entry in all of it's beauty :-)
Geoff> Since the GNU C library is, by definition, a toolkit and/or a
Geoff> linkable module, and it most certainly allows the user to alter
Geoff> its functionality, it would not be permitted to be exported under
Geoff> this licence exemption.
Obviously, yes. -- Sigh -- Sometimes I wonder how many working hours
world-wide are wasted by this silly regulation. Hopefully the Wassenaar
treaty will ease our work; it promises to free "software in the public
domain", which in their terms includes BSD and GPL copyrights. Let's wait
and see.
Thanks for the correction.
Torsten
------------------------------
From: "S.R.Sathe" <[EMAIL PROTECTED]>
Date: Tue, 09 Feb 1999 16:15:31 +0400
Subject: Re. array access
Dear sir,
I would like to use lage dimensional arrays in gcc. I am unable to
access
an array of dimension int a[1000][1000]. Please help
Bye,
S.R.Sathe-
- -----------------------------------------------------------------------------
S.R.Sathe Phone.No. Office: 223710
Asstt. Professor
Deptt. of Electronics and Computer Science Res. :
224511
Visvesvaraya Regional College of Engineering Fax: 223230
Nagpur - 440 011 E-mail: [EMAIL PROTECTED]
- -----------------------------------------------------------------------------
------------------------------
From: Kurt Wall <[EMAIL PROTECTED]>
Date: Tue, 09 Feb 1999 07:07:24 -0700 (MST)
Subject: RE: Re. array access
Highly placed sources report that S.R.Sathe wrote:
> Dear sir,
>
> I would like to use lage dimensional arrays in gcc. I am unable to
> access
> an array of dimension int a[1000][1000]. Please help
Just for grins, the program below compiled without error, but generated
a bus error when executed. Machine in question is a Pentium II 266 with 128
MB RAM. What kind of machine do you have? What version of GCC? What error(s)
do you get?
#include <stdio.h>
#include <stdlib.h>
int main(void)
{
int i[1000][1000];
int j, k;
for(j = 0; j < 1000; ++j) {
for(k = 0; k < 1000; ++k) {
i[j][k] = (j + k);
}
}
printf("i[1000][1000] = %ld\n", i[1000][1000]);
exit(0);
}
Kurt
- --
Informix on Linux FAQ
http://www.xmission.com/~kwall/iolfaq/english/iolfaq.html
http://www.xmission.com/~kwall/iolfaq/spanish/iolfaq.html (Spanish)
http://www.xmission.com/~kwall/iolfaq/romanian/iolfaq.html (Romanian)
------------------------------
From: Eivind Tagseth <[EMAIL PROTECTED]>
Date: Tue, 9 Feb 1999 15:19:22 +0100
Subject: Re: Re. array access
On Tue, Feb 09, 1999 at 07:07:24AM -0700, Kurt Wall wrote:
>
> Highly placed sources report that S.R.Sathe wrote:
> > Dear sir,
> >
> > I would like to use lage dimensional arrays in gcc. I am unable to
> > access
> > an array of dimension int a[1000][1000]. Please help
>
> Just for grins, the program below compiled without error, but generated
> a bus error when executed. Machine in question is a Pentium II 266 with 128
> MB RAM. What kind of machine do you have? What version of GCC? What error(s)
> do you get?
> int i[1000][1000];
> printf("i[1000][1000] = %ld\n", i[1000][1000]);
^^^^ ^^^^ ^^^^ ^^^^
Those should be 999.
If the program still crashes, check the stack-limit:
$ ulimit -a
core file size (blocks) unlimited
data seg size (kbytes) unlimited
file size (blocks) unlimited
max memory size (kbytes) unlimited
stack size (kbytes) 2048
cpu time (seconds) unlimited
max user processes 256
pipe size (512 bytes) 8
open files 1024
virtual memory (kbytes) 2099199
$ ./test
Segmentation fault (core dumped)
$ ulimit -s 8196
$ ./test
i[999][999] = 1998
Eivind
------------------------------
From: Kurt Wall <[EMAIL PROTECTED]>
Date: Tue, 09 Feb 1999 07:39:43 -0700 (MST)
Subject: Re: Re. array access
Highly placed sources report that Eivind Tagseth wrote:
> On Tue, Feb 09, 1999 at 07:07:24AM -0700, Kurt Wall wrote:
>>
>> Highly placed sources report that S.R.Sathe wrote:
>> > Dear sir,
>> >
>> > I would like to use lage dimensional arrays in gcc. I am unable to
>> > access
>> > an array of dimension int a[1000][1000]. Please help
>>
>> Just for grins, the program below compiled without error, but generated
>> a bus error when executed. Machine in question is a Pentium II 266 with 128
>> MB RAM. What kind of machine do you have? What version of GCC? What
>> error(s)
>> do you get?
>
>> int i[1000][1000];
>
>> printf("i[1000][1000] = %ld\n", i[1000][1000]);
> ^^^^ ^^^^ ^^^^ ^^^^
>
> Those should be 999.
Dohh! Stupid me, wasn't paying attention. Changed "1000" to "999" and "%ld"
to "%d" and it runs without problems. So, I have no idea what's going on with
the original poster's system.
> If the program still crashes, check the stack-limit:
> $ ulimit -a
> core file size (blocks) unlimited
> data seg size (kbytes) unlimited
> file size (blocks) unlimited
> max memory size (kbytes) unlimited
> stack size (kbytes) 2048
> cpu time (seconds) unlimited
> max user processes 256
> pipe size (512 bytes) 8
> open files 1024
> virtual memory (kbytes) 2099199
$ ulimit -a
core file size (blocks) 0
data seg size (kbytes) unlimited
file size (blocks) unlimited
max memory size (kbytes) unlimited
stack size (kbytes) 8192
cpu time (seconds) unlimited
max user processes 256
pipe size (512 bytes) 8
open files 256
virtual memory (kbytes) 2105343
After I changed the array bounds to correct values, it ran just fine. I
suppose I should change the core file size for my mortal user's account, but
it's generally not a problem.
> $ ./test
> Segmentation fault (core dumped)
> $ ulimit -s 8196
> $ ./test
> i[999][999] = 1998
Kurt
- --
Informix on Linux FAQ
http://www.xmission.com/~kwall/iolfaq/english/iolfaq.html
http://www.xmission.com/~kwall/iolfaq/spanish/iolfaq.html (Spanish)
http://www.xmission.com/~kwall/iolfaq/romanian/iolfaq.html (Romanian)
------------------------------
From: [EMAIL PROTECTED]
Date: Tue, 9 Feb 1999 17:32:33 +0300
Subject: RE: Re. array access
Dear Sir,
>> printf("i[1000][1000] = %ld\n", i[1000][1000]);
You try to access memory beyon the array's bound, so SIGSEGV is normal
reaction.
With best wishes,
Alex Romadinoff, Lead Software Develope (Mac department) , OpenTeach
Software, Ltd.
------------------------------
From: Kurt Wall <[EMAIL PROTECTED]>
Date: Tue, 09 Feb 1999 12:21:00 -0700 (MST)
Subject: RE: Re. array access
Highly placed sources report that [EMAIL PROTECTED] wrote:
> Dear Sir,
>
>>> printf("i[1000][1000] = %ld\n", i[1000][1000]);
> You try to access memory beyon the array's bound, so SIGSEGV is normal
> reaction.
Which I corrected and fixed the SIGSEGV; also fixed the "%ld" to "%d". I still
want to know what problems the original poster had.
Kurt
- --
Informix on Linux FAQ
http://www.xmission.com/~kwall/iolfaq/english/iolfaq.html
http://www.xmission.com/~kwall/iolfaq/spanish/iolfaq.html (Spanish)
http://www.xmission.com/~kwall/iolfaq/romanian/iolfaq.html (Romanian)
------------------------------
From: <[EMAIL PROTECTED]>
Date: Thu, 11 Feb 1999 06:46:54
Subject: Notice to all Mobile Phone Users!
Hi,
You have been referred to us as someone that would benefit from
the following information.
If you are a mobile phone user then you may be interested to
learn about the following.
___________________________________________________________
"Don't pay more for your mobile phone than you have to"
___________________________________________________________
We are an independent mobile phone consultancy based in
Hertfordshire that has been formed as a result of the increased
competition between the UK's four mobile phone networks. Our
team have an extensive and personal understanding of how mobile
phone networks compete for your business.
Our dedicated team of consultants are available to offer you the
cheapest possible package from your existing mobile phone
operator.
A number of our colleagues are former employees of one of the
UK's leading mobile phone networks. Their knowledge and expertise
will prove to be a valuabe commodity.
1. We will show you how it is possible to reduce your existing
monthly line rental charge by between 10% to 50%.
2. We will show you how you can upgrade your phone at a
discounted price or in some cases, FREE.
3. We will show you how to go about obtaining a credit on your
account.
4. We will show you how it is possible to transfer from one
network to another taking your existing mobile phone
number with you and receiving upto �100.00 for your trouble.
5. We will show you how you can take advantage of free local and
national calls day and night.
6. We will show you how to achieve cheaper international calls.
7. We will show you how to receive a discounted memorable mobile
number.
8. We will show you how you can have two numbers running side by
side and pay just one line rental charge.
______________________________
This and a whole lot more!
______________________________
If you require more information regarding the above and what we
can offer you then please send an e.mail stating your name,
contact number, e.mail address, the network you are with and
length of time you have been with them to
[EMAIL PROTECTED] Alternatively, you can contact us
on 01438 234961 or send a fax to 0171 681-3495.
Please forward this e.mail to other mobile phone users you know.
We look forward to hearing from you!
Kindest Regards and Best Wishes.
Christopher Scott
Managing Director
------------------------------
From: holotko <[EMAIL PROTECTED]>
Date: Thu, 11 Feb 1999 05:07:19 +0000
Subject: Device Driver Info
I am interested in learning more about kernel internals and how to
design device drivers. I just acquired a book by O'Reiley titled
"LINUXDevice Drivers" . I was wondering if anyone can recommend any
other books that deal with these topics that may also be useful and
helpful...
/John
- --
email: [EMAIL PROTECTED]
Local mailserver <landreau.ruffe.edu> , remote <ns.computer.net>
"I'll bet ya that thing WON'T GO!!!" - the jerk from the station.
------------------------------
From: Balbir Singh <[EMAIL PROTECTED]>
Date: Thu, 11 Feb 1999 10:50:31 +0530 (IST)
Subject: Re: Device Driver Info
Hi,
This message should actually be posted on linux-kernel.
Anyway, I am no longer on that list. There are a lot of web sites you
would like to browse through, like Redhat Kernel Hackers Guide (KHG).
See some issues of Linux Journal, I think issues #23, #24, #25, #26, etc.
They all carry articles from A Rubini on Linux Device Drivers. Also,
get a feel of writing device drivers on other platforms, the DDI/DKI
specs, etc.
regards,
Balbir Singh.
On Thu, 11 Feb 1999, holotko wrote:
> I am interested in learning more about kernel internals and how to
> design device drivers. I just acquired a book by O'Reiley titled
> "LINUXDevice Drivers" . I was wondering if anyone can recommend any
> other books that deal with these topics that may also be useful and
> helpful...
>
> /John
>
>
> --
> email: [EMAIL PROTECTED]
> Local mailserver <landreau.ruffe.edu> , remote <ns.computer.net>
>
> "I'll bet ya that thing WON'T GO!!!" - the jerk from the station.
>
------------------------------
From: Rick <[EMAIL PROTECTED]>
Date: Wed, 10 Feb 1999 23:21:03 -0600
Subject: Re: Device Driver Info
There's good online book at LDP called The Linux Kernel. Also, if you have
recent 2.2.x kernels look in linux/Documentation/kernel-docs.txt file. There
is also the book Linux Kernel Internals, i do not have it but i've heard good
things.
------------------------------
From: Sharad Joshi <[EMAIL PROTECTED]>
Date: Thu, 11 Feb 1999 11:10:27 +0530 (IST)
Subject: Re: Device Driver Info
lkmpg (linux kernel module programming guide) and tlk (linux kernel) at
http://www.metalab.unc.edu/LDP/LDP are excellent to start with.
On Wed, 10 Feb 1999, Rick wrote:
> There's good online book at LDP called The Linux Kernel. Also, if you have
> recent 2.2.x kernels look in linux/Documentation/kernel-docs.txt file. There
> is also the book Linux Kernel Internals, i do not have it but i've heard good
> things.
------------------------------
From: "BSB Publishing Com." <[EMAIL PROTECTED]>
Date: 11 Feb 1999 10:37:03 -0800
Subject: The New Bible of Dating!! (x11)
Women all over America have said, "Burn This Book!!!"
CALL TO ORDER YOUR COPY - (800) 830-2047 [24hrs]
How To Juggle Women:
Without Getting Killed or Going Broke
by Stefan Feller
ISBN:0-9658299-4-4
Price: $12.00
This book is an essential guide for the seasoned dating
man who needs help organizing the women in his life.
Women are constantly grabbing your interest and attention.
Do you have to choose on over the other? Of Course not!
Stop letting opportunities like these go to waste.
Why not date them all?
This is a must-read for men who are active on the dating
scene. Not only will you learn how to juggle several
females at a time, you will also improve your overall
chances with women, including where to meet them and
how to do the little things to keep them happy.
You will learn time-saving techniques that will maximize
your availability, and allow you to spend time with several
ladies a day. The author details scheduling methods so you
never have two dates at the same time. You will also learn
money-saving tips so you can date aggressively and still
have money left to buy life's other necessities.
Forget the saying,"For every man there is a woman out
there." Now it will be, "For every man there are at
least three women."
- --------------------------------------------------------
CHAPTER TITLES
Chapter One - Getting to Know You
Chapter Two - Categories of Women
Chapter Three - Where to Find Them
Chapter Four - The Rotation
Chapter Five - Prior Planning
Chapter Six - How to Keep Them Happy and Away From Each Other
Chapter Seven - Fiscally Fit
Chapter Eight - Personnel Changes
- --------------------------------------------------------
Juggling Women:
Without Getting Killed or Going Broke
by Stefan Feller
ISBN:0-9658299-4-4
Price: $12.00
$3.00 Shipping individuals - COD Charges are free for a limited time.
Wholesale Discounts Available
- ---------------------------------------------------------
Order by Phone
1 (800)830-2047
24 hours a day
- ---------------------------------------------------------
------------------------------
From: "Prasanna Bose" <[EMAIL PROTECTED]>
Date: Fri, 12 Feb 1999 06:09:10 PST
Subject: Re: C++ Destructor Question
Anything that is allocated with a
new classtype[] should be deleted with a delete[].
A pointer which is allocated with a "new classtype[]" actually points
to an array in the memory( heap ). Thus a delete[] is necessory to
deallocated the allocated mem. A "delete" on the contrary might
deallocate only one sizeof( classtype ) bytes from the memory.
We can have a,
class Microsoft *BG;
BG = new Microsoft;
delete BG; // This is Valid , and its dead !!!
This is also valid, a *x points to only one block on the heap with
size = sizeof( A )
Note : when a new[] is done, the amount of mem blocks allocated are
internally maintained by C++ so that delete[], deallocates the right no
of blocks.
vive,
Prasanna
>From [EMAIL PROTECTED] Wed Feb 3 22:34:20 1999
>Received: from computer.net ([EMAIL PROTECTED] [127.0.0.1])
> by landreau.ruffe.edu (8.8.7/8.8.7) with ESMTP id RAA08124;
> Wed, 3 Feb 1999 17:26:45 -0500
>Sender: [EMAIL PROTECTED]
>Message-ID: <>
>Date: Wed, 03 Feb 1999 22:26:42 +0000
>From: holotko <[EMAIL PROTECTED]>
>Reply-To: holotko <[EMAIL PROTECTED]>
>Organization: The Ruffe' School
>X-Mailer: Mozilla 4.5 [en] (X11; U; Linux 2.0.32 i586)
>X-Accept-Language: en
>MIME-Version: 1.0
>To: Prasanna Bose <[EMAIL PROTECTED]>
>CC: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>,
> Linux C Programming <[EMAIL PROTECTED]>
>Subject: Re: C++ Destructor Question
>References: <>
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
>Prasanna Bose wrote:
>>
>> Actually the destructor should be
>> ~Foo()
>> { delete[] word; } // as an array has been allocated.
>>
>> vive,
>> Prasanna subash
>>
>
>Actually, although I didn'tshow it in the example but I defined the
>variable "word" at the beginning of the class as:
>
> private:
>
> char *word;
>As a pointer.
>Thus, when the allocated memory is killed can'tit be done as :
>
> delete word;
>Or is it still required that it be done in array format as:
> delete[] word; ???
>
>
>
>/John <[EMAIL PROTECTED]>
>
>
>> >Hi,
>> >The destructor is automatically called when the
>> >object in question is no longer needed. Such as
>> >an object is created inside a function locally and
>> >when the function returns the object gets killed with
>> >the destructor executed. Hence we dont call the
>> >destructor explicitly.
>> >
>> >And in java I feel the garbage collection concept is
>> >implemented quite strong and rarely do we use explicit
>> >deallocation.
>> >
>> >Cheers,
>> >Suresh
>> >Wipro-Nortel Networks
>> >Bangalore
>> >>
>> >>
>> >>Being spoiled by Java's garbage collector leads me to this quick
>> >>question again concerning constructors in C++.
>> >>
>> >>If I allocate memory via "new" using a constructor
>> >>
>> >>i.e.
>> >>
>> >> class Foo
>> >> {
>> >> Foo()
>> >> { word = new char[LENGTH + 1]; }
>> >>
>> >> ~Foo()
>> >> { delete word; }
>> >>
>> >> ...
>> >> }
>> >>
>> >>When I create an object of class Foo memory will be allocated for
the
>> >>char buffer "word". Now when the object is no longer needed must I
>> >>make an explicit call to the destructor ~Foo() to destroy the
object
>> >>and subsequently call "delete", or, is the destructor somehow
called
>> >>automatically when the object is no longer needed,i.e. outside of
>> >>it's scope?
>> >>
>> >>Even in Java there are times when it is up to you to destroy an
object
>> >>and/or free memory used for that object, depending on how the
object
>> >>is/was created and an method equivalent of a destructor is
required...
>> >>The garbage collector is not always adequate.
>> >>
>> >>Thanks...
>> >>
>> >>Sincerely,
>> >>
>> >>/John <[EMAIL PROTECTED]>
>> >>
>> >>
>> >>--
>> >>email: [EMAIL PROTECTED]
>> >>Local mailserver <landreau.ruffe.edu> , remote <ns.computer.net>
>> >>
>> >>There is a great alternative to war, it's called Peace.
>> >>
>> >
>> >
>> >--
>>
>> ______________________________________________________
>> Get Your Private, Free Email at http://www.hotmail.com
>
>--
>email: [EMAIL PROTECTED]
>Local mailserver <landreau.ruffe.edu> , remote <ns.computer.net>
>
>"I don't like dictatorship of the rich" - Alan Ginsberg.
>
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
------------------------------
From: Peter Schuller <[EMAIL PROTECTED]>
Date: Fri, 12 Feb 1999 23:36:44 +0100 (CET)
Subject: Re: C++ Destructor Question
This message is in MIME format
- --_=XFMail.1.3.p0.Linux:990212221313:5251=_
Content-Type: text/plain; charset=iso-8859-1
> Anything that is allocated with a
> new classtype[] should be deleted with a delete[].
Does anyone know if the C++ language specification actually states that that is
true?
I've read in books etc that delete[] is supposed to be used, but I don't
think I've EVER seen it used in the real world. I never use delete[] myself, and
I have no problems with memory leaks.r
/ Peter Schuller
Technical support guy: Microsoft support, how may I help you?
Newbie: Well, I am having problems with my computer.
Tech guy: So what's the problem?
Newbie: Windows keeps crashing on me.
[3 second pause]
Tech guy: And?
- ---
PGP userID: 0x5584BD98 or 'Peter Schuller <[EMAIL PROTECTED]>'
E-Mail: [EMAIL PROTECTED]
Web: http://hem.passagen.se/petersch
- --_=XFMail.1.3.p0.Linux:990212221313:5251=_
Content-Type: application/pgp-signature
- -----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
MessageID: OIH6fJtd5gmU4NRSPVQZjiqwGebgqXRJ
iQA/AwUBNsSZacBfJ1FVhL2YEQKlwQCffakMvyqqW5kb7XOJqKwh/2hzbVcAoKVQ
sNO3yTA1UBgklDrsFNKsPRGd
=cDue
- -----END PGP SIGNATURE-----
- --_=XFMail.1.3.p0.Linux:990212221313:5251=_--
End of MIME message
------------------------------
From: "Michael Traffanstead" <[EMAIL PROTECTED]>
Date: Fri, 12 Feb 1999 16:51:53 -0600
Subject: RE: C++ Destructor Question
>From "C++ Programing Language : Third Edition" - Stroustrup
Section 6.2.6.1 Arrays
...
The "plain" operator delete is used to delete individual objects;
delete[] is used to delete arrays.
...
traff
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Peter Schuller
> Sent: Friday, February 12, 1999 4:37 PM
> To: Prasanna Bose
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: Re: C++ Destructor Question
>
>
> > Anything that is allocated with a
> > new classtype[] should be deleted with a delete[].
>
> Does anyone know if the C++ language specification actually
> states that that is
> true?
>
> I've read in books etc that delete[] is supposed to be used, but I don't
> think I've EVER seen it used in the real world. I never use
> delete[] myself, and
> I have no problems with memory leaks.r
>
> / Peter Schuller
>
> Technical support guy: Microsoft support, how may I help you?
> Newbie: Well, I am having problems with my computer.
> Tech guy: So what's the problem?
> Newbie: Windows keeps crashing on me.
> [3 second pause]
> Tech guy: And?
>
> ---
> PGP userID: 0x5584BD98 or 'Peter Schuller <[EMAIL PROTECTED]>'
> E-Mail: [EMAIL PROTECTED]
> Web: http://hem.passagen.se/petersch
>
>
>
------------------------------
From: [EMAIL PROTECTED] (Zygo Blaxell)
Date: 13 Feb 1999 15:27:42 -0500
Subject: Re: C++ Destructor Question
In article <>,
Peter Schuller <[EMAIL PROTECTED]> wrote:
>> Anything that is allocated with a
>> new classtype[] should be deleted with a delete[].
>
>Does anyone know if the C++ language specification actually states that that is
>true?
>
>I've read in books etc that delete[] is supposed to be used, but I don't
>think I've EVER seen it used in the real world. I never use delete[] myself, and
>I have no problems with memory leaks.r
That's because you've never used delete to delete a new[]ed array of objects
which deallocate memory in their destructor.
delete[] calls the destructor for each element of an array of objects.
delete calls the destructor only once for the object pointed to.
- --
Zygo Blaxell, Linux Engineer, Corel Corporation, [EMAIL PROTECTED] (work),
[EMAIL PROTECTED] (play). It's my opinion, I tell you! Mine! All MINE!
Size of 'diff -Nurw [...] winehq corel' as of Sat Feb 13 15:14:00 EST 1999
Lines/files: In 10558 / 114, Out 6460 / 77, Both 14451 / 162
------------------------------
From: [EMAIL PROTECTED] (H.J. Lu)
Date: Sun, 14 Feb 1999 13:49:59 -0800 (PST)
Subject: gdb 4.17.0.11 is released.
Hi,
Here is gdb 4.17.0.11. Enjoy.
- --
H.J. Lu ([EMAIL PROTECTED])
- ---
Hi, Folks,
This is the beta release of gdb 4.17.0.11, which is based on gdb 4.17
plus Linux/x86 hardware watchpoint/FPU, glibc 2 pthread and Linux/PPC
support. You need linux 2.0.35 or above, or 2.1.xx to get the x86 FPU
to work correctly. The Linux/x86 binary works with all recent kernels
and C libraries, and the x86 FPU support is enabled at the run-time,
depending on the kernel version.
To debug LinuxThreads in glibc 2.1, you need to apply the patch,
glibc-2.1-linuxthreads-gdb.diff.gz.
Please report any bugs related to gdb 4.17.0.11 to [EMAIL PROTECTED]
Problems:
Because most of system calls in glibc 2 are written in assembly without
frame pointer, gdb may not be able to debug nor get stack trace system
calls on glibc-based 2 systems. Due to this, "make check" may fail in
FAIL: gdb.base/a1-selftest.exp: backtrace through signal handler
FAIL: gdb.base/signals.exp: bt in signals.exp
with glibc 2.
Also, it is normal to see
FAIL: gdb.base/interrupt.exp: continue (timeout)
FAIL: gdb.base/interrupt.exp: echo data (timeout)
if there is
XPASS: gdb.base/interrupt.exp: send_gdb end of file
Due to the new cplus-dem.c from egcs 1.1.1, you will get a few
FAIL: gdb.c++/demangle.exp: maint demangle __xxxxxxxxxx
Changes from gdb 4.17.0.10:
1. Support LinuxThreads in glibc 2.1 in binaries compiled under glibc
2.0 and libc 5.
2. Support LinuxThreads on alpha.
3. Support Solaris 2.7/x86.
Changes from gdb 4.17.0.9:
1. Fix support for glibc 2.1 pthread. Need the latest glibc 2.1, newer
than 16:30pm PST of 19990-02-03.
2. Fix deleting the hardware watchpoint on x86.
Changes from gdb 4.17.0.8:
1. The new cplus-dem.c from egcs 1999-01-12 with a bug fix.
2. Add support for deleting the hardware watchpoint on x86.
3. Update support for glibc 2.1 pthread.
4. Fix C++ testsuite.
Changes from gdb 4.17.0.6:
1. Support for glibc 2.1 pthread. But it doesn't work, probably due
to the CLONE_PTRACE change to pthread in glibc 2.1.
2. Add support for the older Linux C libraries.
3. Add -static support for glibc 2.1.
Changes from gdb 4.17.0.5:
1. Support for glibc 2.0 pthread. It doesn't work with glibc 2.1.
2. The Linux/PPC support.
3. The Linux/Sparc support. Untested.
Changes from gdb 4.17.0.4:
1. Fix the Intel FPU tag code handling.
Changes from gdb 4.17.0.3:
1. Fix testcases for FPU.
2. Fix x86 hardware watchpoint support.
Changes from gdb 4.17.0.2:
1. Fake FP registers on older kernels.
Changes from gdb 4.17:
1. Linux/x86 FPU support is added. You can debug floating point numbers
just like integers.
2. x86 hardware watchpoint is extended to long long, double and long
double.
3. More information on x86 CPU status register.
4. Fix a bug when reading beyond the memory boundary.
The file list:
1. gdb-4.17-4.17.0.11.diff.gz. Patch against gdb 4.17.
2. gdb-4.17.0.10-4.17.0.11.diff.gz. Patch against gdb 4.17.0.10.
3. gdb-4.17.0.11.x86.gz. Precompiled Linux/x86 statically linked binary.
4. gdb-4.17.0.11.spec. A RPM spec file for RedHat 5.2.
5. glibc-2.1-linuxthreads-gdb.diff.gz. A patch for glibc 2.1.
The ftp sites for my gdb patches:
ftp://ftp.varesearch.com/pub/support/hjl/gdb
ftp://ftp.yggdrasil.com/private/hjl
ftp://ftp.kernel.org/pub/linux/devel/gcc
gdb 4.17 source code is available at
ftp://ftp.gnu.org/pub/gnu
To install the precompiled binary,
# gunzp gdb-4.17.0.11.x86.gz
# cp gdb-4.17.0.11.x86 /usr/bin/gdb
H.J.
[EMAIL PROTECTED]
02/13/1999
------------------------------
From: [EMAIL PROTECTED]
Date: Sun, 14 Feb 1999 20:18:20
Subject: ADV: ALASKAN TRAVEL
ALASKA MAGAZINE in their July 98 issue says "The best source of
information on snowmachining is Alaska's Snowmachiners'
Directory. Published once a year, this glossy magazine is loaded
with information vital to planning a winter vacation in Alaska"
Alaska's Snowmachiners' Directory is the ultimate travel guide
for snowmobiling in Alaska. Alaska's Snowmachiners' Directory is
the most comprehensive guide ever published covering the State of
Alaska, with regards to snowmobiling. It is a full color, glossy
publication filled with over 100 pages of information for anyone
wanting to travel or ever thought of traveling to Alaska in the
winter time.
Inside you will find Directories for; Lodges, Snowmobile Tour
Companies, Snowmobile Rentals, Motorhome Rentals, Snowmobile
Clubs, Trail Systems, Events unique to Alaska along with phone
numbers and websites. You can order yours for only $5.95 + S/H.
For more info and to order, check us out at
http://www.mustgohere.com/aksnowmachiner
<a href="http://www.mustgohere.com/aksnowmachiner">Click Here</a>
Reply with remove to be removed.
MediaWeb AA,MI48103 7346698750
------------------------------
From: Hanbing Yan <[EMAIL PROTECTED]>
Date: Mon, 15 Feb 1999 09:38:43 -0500
Subject: How can get users' information of linux server?
How can I know how long one user using the linux and other information?
May I save these information in a database directly when user log in? So
I can manipulate these data through database application when I need?
How can I do that? Thank you.
Best Regards,
Hanbing Yan
------------------------------
From: "Marty Leisner" <[EMAIL PROTECTED]>
Date: Tue, 16 Feb 1999 01:29:00 -0500
Subject: : undefined symbol: __register_frame_info
The binary I found (pkgview) was built on a redhat 5.1 system.
I have a 5.2 system.
This program won't load on my system, I get:
./pkgview: error in loading shared libraries
: undefined symbol: __register_frame_info
In gcc 2.8.1, its in libgcc2...
Any advice?
Marty Leisner
[EMAIL PROTECTED]
------------------------------
From: Horvath Akos <[EMAIL PROTECTED]>
Date: Thu, 18 Feb 1999 00:31:23 +0000 (/etc/localtime)
Subject: Re: : undefined symbol: __register_frame_info
On Tue, 16 Feb 1999, Marty Leisner wrote:
> The binary I found (pkgview) was built on a redhat 5.1 system.
> I have a 5.2 system.
> This program won't load on my system, I get:
> ./pkgview: error in loading shared libraries
> : undefined symbol: __register_frame_info
Hello,
compile this to a little shared lib
__register_frame_info() {}
__unregister_frame_info() {}
with gcc -shared -o /usr/local/lib/libfix.so something.c
And then you will be able to run this binaries with
LD_PRELOAD=/usr/local/lib/libfix.so pkgview
bye
MaXX
------------------------------
From: Yotam Medini <[EMAIL PROTECTED]>
Date: 17 Feb 1999 23:41:59 -0800
Subject: gcc-2.8.x & Linux 2.2
The following message is a courtesy copy of an article
that has been posted as well.
Hello Linux & gcc gurus.
If coming Linux distribution are ready to use gcc-2.8.x and
nothing earlier, then please ignore this post.
Both Linux and gcc are advancing fast. Both projects, that is
Linux-kernel and the gcc's egcs project are very valuable to
the software community.
I haven't been following the technical details, but I understand
that there were (still are?) problems using gcc-2.8.1 (or higher)
compiling the kernel.
The improvements in the C++ part of gcc (g++) are very significant.
Serious C++ programmers who use STL cannot stay with or go back to gcc-2.7.x.
Having active installed variants of gcc in Linux environment
is a hassle in terms of Makefile maintenance for developers,
and environment variables setting for run time shared libraries.
Please let me beg:
May the coming major Linux distribution, with kernel >= 2.2
have the necessary patches for gcc-2.8.x.y so a single installed
gcc with libgcc could compile and run the kernel and
perform well with C++ templates in general and specifically with STL.
- -- yotam
.--------------------------------------------------------------------------,
< Yotam Medini [EMAIL PROTECTED] http://www.blueneptune.com/~yotam/ >
`--------------------------------------------------------------------------'
------------------------------
From: "J.H.M. Dassen" <[EMAIL PROTECTED]>
Date: Thu, 18 Feb 1999 12:19:41 +0100
Subject: Re: gcc-2.8.x & Linux 2.2
[Cc-s left intact; please cut when appropriate.]
[For those not familiar with Debian development, I'm a member of
<[EMAIL PROTECTED]>, the group of Debian developers that maintains
the Debian compiler packages (gcc and EGCS).]
On Wed, Feb 17, 1999 at 23:41:59 -0800, Yotam Medini wrote:
> If coming Linux distribution are ready to use gcc-2.8.x and nothing
> earlier, then please ignore this post.
To the best of my knowledge, most up to date distributions (Debian, Red Hat,
Slackware, and presumably SuSE too) follow a dual track compiler-wise:
- - For C: FSF gcc 2.7.2.x as it's the only version with which Linux 2.0.x
can be compiled safely.
- - For C++, Fortran etc.: EGCS.
> I haven't been following the technical details, but I understand that
> there were (still are?) problems using gcc-2.8.1 (or higher) compiling the
> kernel.
These problems affect Linux 2.0.x kernels only (Florian La Roche has
collected patches for the known problems at
http://www.suse.de/~florian/kernel+egcs.html).
Linux 2.2.x (the latest stable kernel series) has no problems with gcc 2.8.1
or EGCS.
> The improvements in the C++ part of gcc (g++) are very significant.
> Serious C++ programmers who use STL cannot stay with or go back to
> gcc-2.7.x.
This is part of the reason Debian decided last year to go with EGCS as the
C++ compiler.
> Please let me beg:
> May the coming major Linux distribution, with kernel >= 2.2 have the
> necessary patches for gcc-2.8.x.y so a single installed gcc with libgcc
> could compile and run the kernel and perform well with C++ templates in
> general and specifically with STL.
The current Debian version (2.0, "hamm") ships with EGCS 1.0.3a for C++ and
Fortran.
Debian 2.1 ("slink"), which is planned for release next month, will ship
with EGCS 1.1.1 for C++, Fortran and Pascal compilation, and FSF gcc 2.7.2.3
for C compilation, as the default kernel shipped with Debian 2.1 kernel will
still be a 2.0.x one. (Debian 2.1 will be largely 2.2.x ready; see
http://www.debian.org/~rcw/2.2/warnings.html for details).
I expect Debian 2.2 ("potato") will ship with a 2.2.x kernel by default. We
will consider switching to EGCS as the default C compiler by then.
Debian at the moment has no FSF gcc 2.8.1 packages.
We see very few signs of active development of FSF gcc, and numerous reports
of bugs that are fixed in EGCS.
In our experience EGCS is quite actively maintained, produces reliable
well-integrated releases and has vast improvements in C++ support over FSF
gcc. Debian itself is a bazaar-style project, and many within Debian (myself
included) believe that bazaar-style development as practiced with EGCS is
the way to go for the development of the GNU compiler.
I hope the FSF will reconsider its position wrt EGCS and bless it as the
standard gcc.
Ray
- --
Obsig: developing a new sig
------------------------------
From: "Marty Leisner" <[EMAIL PROTECTED]>
Date: Thu, 18 Feb 1999 14:01:02 -0500
Subject: Re: : undefined symbol: __register_frame_info
> On Tue, 16 Feb 1999, Marty Leisner wrote:
> > The binary I found (pkgview) was built on a redhat 5.1 system.
> > I have a 5.2 system.
> > This program won't load on my system, I get:
> > ./pkgview: error in loading shared libraries
> > : undefined symbol: __register_frame_info
>
> Hello,
>
> compile this to a little shared lib
>
> __register_frame_info() {}
> __unregister_frame_info() {}
>
> with gcc -shared -o /usr/local/lib/libfix.so something.c
> And then you will be able to run this binaries with
>
> LD_PRELOAD=/usr/local/lib/libfix.so pkgview
>
> bye
>
> MaXX
OK, this worked (thanx).
But can I have a little bit of background information...I'm not sure
what is going on...this function is in libgcc.a for 2.8.1, but not
in 2.7.2.3.. (I needed to use 2.7.2.3 to compile). When I got the pkgview
binary build on a redhat-5.1, I needed to do this trick...
Marty Leisner
------------------------------
From: "Daniel C. Nurmi" <[EMAIL PROTECTED]>
Date: Fri, 19 Feb 1999 11:19:25 -0600 (EST)
Subject: 2.2.1 header conflicts
Greetings,
When trying to compile the following simple program:
- ------------------------------
#include <fcntl.h>
#include <sys/types.h>
#include <unistd.h>
#include <string.h>
#include <stdio.h>
#include <stdlib.h>
#include <errno.h>
#include <sys/vfs.h>
#include <linux/nfs_fs.h>
main()
{
return 0;
}
- ------------------------------
..with gcc 2.7.2.3.f.1 and kernel version 2.2.1, the errors at the end of
this message were given.
It seems as though there might be a conflict here. Is the preceding
simple program false?
thank you,
- -Dan
- -------------------------------
In file included from /usr/include/linux/sched.h:69,
from /usr/include/linux/nfs_fs.h:13,
from /tmp/test.c:9:
/usr/include/linux/time.h:69: warning: `FD_SET' redefined
/usr/include/sys/select.h:60: warning: this is the location of the previous definition
/usr/include/linux/time.h:70: warning: `FD_CLR' redefined
/usr/include/sys/select.h:61: warning: this is the location of the previous definition
/usr/include/linux/time.h:71: warning: `FD_ISSET' redefined
/usr/include/sys/select.h:62: warning: this is the location of the previous definition
/usr/include/linux/time.h:72: warning: `FD_ZERO' redefined
/usr/include/sys/select.h:63: warning: this is the location of the previous definition
In file included from /usr/include/linux/signal.h:5,
from /usr/include/linux/nfs_fs.h:12,
from /tmp/test.c:9:
/usr/include/asm/siginfo.h:48: parse error before `clock_t'
/usr/include/asm/siginfo.h:48: warning: no semicolon at end of struct or union
/usr/include/asm/siginfo.h:48: warning: no semicolon at end of struct or union
/usr/include/asm/siginfo.h:49: warning: no semicolon at end of struct or union
/usr/include/asm/siginfo.h:50: warning: data definition has no type or storage class
/usr/include/asm/siginfo.h:62: parse error before `}'
/usr/include/asm/siginfo.h:62: warning: data definition has no type or storage class
/usr/include/asm/siginfo.h:63: parse error before `}'
/usr/include/asm/siginfo.h:63: warning: data definition has no type or storage class
In file included from /usr/include/linux/vfs.h:4,
from /usr/include/linux/fs.h:14,
from /usr/include/linux/capability.h:13,
from /usr/include/linux/binfmts.h:5,
from /usr/include/linux/sched.h:8,
from /usr/include/linux/nfs_fs.h:13,
from /tmp/test.c:9:
/usr/include/asm/statfs.h:12: redefinition of `struct statfs'
In file included from /usr/include/linux/sched.h:13,
from /usr/include/linux/nfs_fs.h:13,
from /tmp/test.c:9:
/usr/include/linux/times.h:5: parse error before `clock_t'
/usr/include/linux/times.h:5: warning: no semicolon at end of struct or union
/usr/include/linux/times.h:6: warning: data definition has no type or storage class
/usr/include/linux/times.h:7: parse error before `tms_cutime'
/usr/include/linux/times.h:7: warning: data definition has no type or storage class
/usr/include/linux/times.h:8: parse error before `tms_cstime'
/usr/include/linux/times.h:8: warning: data definition has no type or storage class
In file included from /usr/include/linux/sched.h:14,
from /usr/include/linux/nfs_fs.h:13,
from /tmp/test.c:9:
/usr/include/linux/timex.h:159: field `time' has incomplete type
In file included from /usr/include/linux/sched.h:17,
from /usr/include/linux/nfs_fs.h:13,
from /tmp/test.c:9:
/usr/include/asm/semaphore.h:134: warning: `struct task_struct' declared inside
parameter list
/usr/include/asm/semaphore.h:134: warning: its scope is only this definition or
declaration,
/usr/include/asm/semaphore.h:134: warning: which is probably not what you want.
/usr/include/asm/semaphore.h: In function `waking_non_zero':
/usr/include/asm/semaphore.h:141: `PAGE_MASK' undeclared (first use this function)
/usr/include/asm/semaphore.h:141: (Each undeclared identifier is reported only once
/usr/include/asm/semaphore.h:141: for each function it appears in.)
/usr/include/linux/time.h: At top level:
In file included from /usr/include/linux/sched.h:69,
from /usr/include/linux/nfs_fs.h:13,
from /tmp/test.c:9:
/usr/include/linux/time.h:9: redefinition of `struct timespec'
/usr/include/linux/time.h:51: parse error before `suseconds_t'
/usr/include/linux/time.h:51: warning: no semicolon at end of struct or union
/usr/include/linux/time.h:88: field `it_interval' has incomplete type
/usr/include/linux/time.h:89: field `it_value' has incomplete type
In file included from /usr/include/linux/sched.h:71,
from /usr/include/linux/nfs_fs.h:13,
from /tmp/test.c:9:
/usr/include/linux/resource.h:22: field `ru_utime' has incomplete type
/usr/include/linux/resource.h:23: field `ru_stime' has incomplete type
In file included from /usr/include/linux/sched.h:74,
from /usr/include/linux/nfs_fs.h:13,
from /tmp/test.c:9:
/usr/include/asm/processor.h:278: warning: `struct task_struct' declared inside
parameter list
/usr/include/asm/processor.h:282: warning: `struct task_struct' declared inside
parameter list
In file included from /usr/include/linux/nfs_fs.h:14,
from /tmp/test.c:9:
/usr/include/linux/in.h:110: parse error before `sa_family_t'
/usr/include/linux/in.h:110: warning: no semicolon at end of struct or union
/usr/include/linux/in.h:117: parse error before `}'
In file included from /usr/include/linux/nfs_fs.h:18,
from /tmp/test.c:9:
/usr/include/linux/nfs_mount.h:34: field `addr' has incomplete type
- ---------------------
------------------------------
From: Philip Blundell <[EMAIL PROTECTED]>
Date: Fri, 19 Feb 1999 19:00:37 +0000
Subject: Re: 2.2.1 header conflicts
>#include <fcntl.h>
>#include <sys/types.h>
>#include <unistd.h>
>#include <string.h>
>#include <stdio.h>
>#include <stdlib.h>
>#include <errno.h>
>#include <sys/vfs.h>
>#include <linux/nfs_fs.h>
You mustn't mix headers from the kernel with those from libc. They aren't
intended to work together.
p.
------------------------------
From: [EMAIL PROTECTED] (Guest section DW)
Date: Fri, 19 Feb 1999 20:30:31 +0100 (MET)
Subject: Re: 2.2.1 header conflicts
From: "Daniel C. Nurmi" <[EMAIL PROTECTED]>
Greetings,
When trying to compile the following simple program:
------------------------------
...
#include <linux/nfs_fs.h>
...
------------------------------
..with gcc 2.7.2.3.f.1 and kernel version 2.2.1, the errors at the end of
this message were given.
Yes. Includes <linux/foo.h> are for the kernel, not for user space.
------------------------------
From: Trevor Johnson <[EMAIL PROTECTED]>
Date: Fri, 19 Feb 1999 14:52:05 -0500 (EST)
Subject: Re: 2.2.1 header conflicts
> #include <linux/nfs_fs.h>
>
> main()
> {
> return 0;
> }
> It seems as though there might be a conflict here. Is the preceding
> simple program false?
Hi, Dan. Usually it's best to use the kernel's headers (<scsi/...>,
<net/...>, <linux/...> and <asm/...>) only within the kernel or modules,
and the libc's headers only for applications. If you need something
that's not in the libc headers (and of course this simple program does
not), then one approach is to borrow just that section and put it in your
own header file (#include "my_nfs_stuff.h"), with a check that __linux__
is defined if you're using a Linux-specific feature. If it's something
that's only available in certain versions of Linux, you might check the
UTS_RELEASE or LINUX_VERSION_CODE in <linux/version.h>, making the
assumptions that the program will be run on the same system where it's
being compiled and that the headers in place reflect the kernel that's
being run. You might also offer it to the libc folks if you think it'll
be used much.
You might have a look at ddstar and autofs as examples.
__
Trevor Johnson
------------------------------
From: Hanbing Yan <[EMAIL PROTECTED]>
Date: Fri, 19 Feb 1999 19:08:10 -0500
Subject: How can I set DNS server?
I have installed the RedHat5.2 and Bind. But the DNS server seems not
work properly.
My setting list below:
/etc/hosts
127.0.0.1 localhost localhostlocaldomain
100.100.100.10 .qginet.com
100.100.100.10 ns.qginet.com ; Name Server
100.100.100.10 www.qginet.com ; Web Server
/etc/resolv.conf
search qginet.com
nameserver 100.100.100.10
/etc/named.conf
options {
directory "/var/named";
};
zone "." {
type hint;
file "localname.ca";
};
zone "0.0.127.in-addr.arpa" {
type master;
file "localname";
};
/etc/named.boot
......
; Add
primary qginet.com qginet.db
secondary 100.100.100.in-addr.arpa qginet.rev
I hope to set name server and web server on one machine. I run ">ndc
restart", then I used nslookup command to check it. Command nslookup
can't find any ip address on there. Should I have to connect the linux
server to internet or network to do this check? Does anyone can give any
suggestion about that? Thanks.
Hanbing
------------------------------
From: [EMAIL PROTECTED] (H.J. Lu)
Date: Sat, 20 Feb 1999 17:52:59 -0800 (PST)
Subject: binutils 2.9.1.0.21 is released.
Hi,
I made 2.9.1.0.21 without merging with the gas snapshot due to the
ARM/ELF issue. I will see what I can do for 2.9.1.0.22. I want to
support Alpha EV6. But the patch I got from Richard is for the gas
snapshot. I am also looking at a IBM 370 patch. I may or may not go
with the the gas snapshot, depending on ARM/ELF and other things.
Thanks.
- --
H.J. Lu ([EMAIL PROTECTED])
- ---
WARNING: This release does not support Linux/PPC. Please don't use
it on Linux/PPC.
This should be final release for binutils 2.9.1.0.x based on binutils
2.9.1. I am planning to release to public this weekend. Please test it
as much as you can. Thanks.
This is the beta release of binutils 2.9.1.0.21 for Linux, which is
based on binutils 2.9.1 plus Linux/ARM support, some x86 assembler
changes, some PPC bug fixes, some alpha bug fixes and an exception
frame optimization bug fix.
Due to the exception frame optimization bug fix, it is highly
recommended that you recompile all your C++ codes. Otherwise,
exception handling may not work right when an exception is thrown.
Since I no longer have machine running libc 5, starting from this
release, there will be no pre-compiled binaries for libc 5.
There was some problem on Linux/alpha. The binaries generated by the
new binituls may not run correctly on Linux/alpha. It turned out it was
a bug in the alpha dynamic linker in glibc 2.0.6. The current glibc 2.1
and glibc 2.0.7 should be ok.
This release should work on linux/x86/alpha. There are some ELF bug
fixes. But I don't know if it fixes all the bugs reported on
linux/sparc, Linux/MIPS and linux/PPC. I'd like to hear reports on them.
I'd like to release it to public soon. Please test it as much as you
can.
Please report any bugs related to binutils 2.9.1.0.21 to [EMAIL PROTECTED]
Changes from binutils 2.9.1.0.21:
1. Ada demangle support.
2. Don't merge weak undefined symols with definitions from a shared
object when building shared object. Only for ELF.
3. Fix a 16bit x86 gas bug.
Changes from binutils 2.9.1.0.20:
1. Enable ld for Solaris/x86.
2. Fix an ELF/i386 bfd/linker bug.
3. Fix a BFD bug.
4. Fix the ELF aligment.
5. Fix an AMD 3DNow! bug.
6. Fix ELF/x86 8/16-bit relocation bug.
7. Add --redefine-sym=old_form=new_form to objcopy.
8. Update cplus-dem.c from the egcs snapshot.
9. Support new Pentium II instructions.
10. Add --demangle/--no-demangle to ld.
Changes from binutils 2.9.1.0.20:
1. A PPC DWARF2 EH patch for gas.
Changes from binutils 2.9.1.0.19:
1. Allow '.' in the middle of a symbol name for the versioning script.
Changes from binutils 2.9.1.0.17:
1. An ELF bug fix.
Changes from binutils 2.9.1.0.16:
1. Some Linux/Sparc64 patches.
2. A shared library linking patch.
3. Update cplus-dem.c from egcs 1.1.1 release.
Changes from binutils 2.9.1.0.15:
1. Update cplus-dem.c from egcs 1.1.1 prerelease.
2. Fix ARM bugs.
3. Fix MIPS/ELF bugs.
4. Fix an objdump bug.
Changes from binutils 2.9.1.0.14:
1. Update the program header handling bug fix from the binutils
snapshot.
2. Added AMD 3DNow! support to disassembler.
Changes from binutils 2.9.1.0.13:
1. An ELF bug fix for program header handling.
2. Added AMD 3DNow! support.
3. Add some vxworks suppport.
4. Fix ld on none-linux platforms.
Changes from binutils 2.9.1.0.12:
1. An ELF/alpha bug fix for creating large shared libraries.
2. An ELF/PPC bug fix.
Changes from binutils 2.9.1.0.11:
1. Use the real fix from Ian for the exception frame optimization bug.
Changes from binutils 2.9.1.0.10:
1. Fix an exception frame optimization bug.
Changes from binutils 2.9.1.0.9:
1. Fix another -Bsymbolic bug for Linux/alpha.
Changes from binutils 2.9.1.0.7:
1. Fix -Bsymbolic for Linux/alpha.
2. Fix a 16bit x86 gas bug.
Changes from binutils 2.9.1.0.6:
1. Fix various ARM bugs.
Changes from binutils 2.9.1.0.5:
1. A MIPS assembler ".align" bug is fixed.
2. bfd.h, bfd.h and bfdlink.h are included in the binary package.
Changes from binutils 2.9.1.0.4:
1. 2 x86 16bit mode assembler bugs, "ret" and "movb $35,0x4(%di)", are
fixed.
IMPORTANT:
The .plt format that the Alpha was using was not thread safe. So I
changed it. The new format is *not* binary compatible with the old,
thus you must use glibc 2.0.4 to get an ld.so that can understand it.
Note that the new ld.so knows how to deal with the old .plt format, so
old libraries will still work, but they should be relinked eventually
for performance reasons.
The file list:
1. binutils-2.9.1.0.21.tar.gz. Source code.
2. binutils-2.9.1.0.20-2.9.1.0.21.diff.gz. Patch against the previous
beta source code.
3. binutils-2.9.1.0.21-glibc.x86.tar.gz. Precompiled Linux/x86 binaries
for libc 6 (glibc 2.0.7 1998-12-11 or above).
4. binutils-2.9.1.0.21-alpha.tar.gz. Precompiled Linux/alpha binaries
for glibc 2.0.7 1998-12-11 or above.
The primary ftp sites for the Linux binutils are:
1. ftp://ftp.varesearch.com/pub/support/hjl/binutils
2. ftp://ftp.kernel.org/pub/linux/devel/gcc
3. ftp://tsx-11.mit.edu/pub/linux/packages/GCC
4. ftp://sunsite.unc.edu/pub/Linux/GCC
The beta directory is in private/tofu under the GCC directory.
To install the binary package, please follow the procedure very closely.
Please backup/save all the files you are instructed to delete and you
should do
gzip -dc binutils-2.9.1.0.21-glibc.x86.tar.gz | tar tvvf -
or
gzip -dc binutils-2.9.1.0.21-alpha.tar.gz | tar tvvf -
to see what is in there.
Please do back up before you remove things.
To install for libc 6 (glibc 2.0.5c or above), PLEASE DO
1. su root
2. cd /
3. rm -f /usr/bin/encaps /usr/bin/nm
4. gzip -dc binutils-2.9.1.0.21-glibc.x86.tar.gz | tar xvvf -
5. ldconfig
Now you have the new gas/binutils under /usr/bin and
/usr/ix86-linuxaout/bin. You have to use
/usr/ix86-linuxaout/bin/as
and
/usr/ix86-linuxaout/bin/ld -m i386linux
if you want to use a.out as and ld directly.
To install for alpha, PLEASE DO
1. su root
2. cd /
3. gzip -dc binutils-2.9.1.0.21-alpha.tar.gz | tar xvvf -
4. ldconfig
I have changed the target names for Linux/x86 and Linux/x86 (a.out)
to ix86-linux and ix86-linuxaout respectively. The precompiled
binaries are installed under /usr/ix86-linux and /usr/ix86-linuxaout.
You should make appropriate symbolic links if you have a different
name for the Linux/x86 target, like i586-unknown-linux.
The target name for Linux/alpha is alpha-linux. The precompiled alpha
binaries are installed under /usr/alpha-linux. You should make
appropriate symbolic links if you have a different name for the
Linux/alpha target, like alpha-redhat-linux.
If you have an old linux library in the a.out format and you cannot
obtain the newer version in the ELF format for whatever reason, you
can try "objcopy --remove-leading-char" on the a.out library and see
if it can link with your code in ELF.
Thanks.
H.J. Lu
[EMAIL PROTECTED]
02/20/99
------------------------------
From: Lei Miao <[EMAIL PROTECTED]>
Date: Wed, 24 Feb 1999 10:21:33 +1100
Subject: pointers on how to write device driver?
Hi all,
Could someone give me some pointers on how to write Linux
device drivers? eg. web pages, good books.
TIA,
Lei
PS: please reply via email to [EMAIL PROTECTED], thanks.
------------------------------
From: Balbir Singh <[EMAIL PROTECTED]>
Date: Wed, 24 Feb 1999 08:40:56 +0530 (IST)
Subject: Re: pointers on how to write device driver?
Hi Lei,
You could try Linux Journal Issuse 23, 24, 25, 26 and some more.
There is a book by Alessandro Rubini on Linux Device Drivers.
You can also go through LDP (Linux Documentation Project) and KHG
(Kernel Hackers Guide) at Redhat web-site.
Theres a wealth of information out there.
regards,
Balbir Singh.
On Wed, 24 Feb 1999, Lei Miao wrote:
> Hi all,
>
> Could someone give me some pointers on how to write Linux
> device drivers? eg. web pages, good books.
>
> TIA,
> Lei
> PS: please reply via email to [EMAIL PROTECTED], thanks.
>
------------------------------
From: [EMAIL PROTECTED] (H.J. Lu)
Date: Fri, 26 Feb 1999 11:52:42 -0800 (PST)
Subject: binutils 2.9.1.0.22b is released.
Hi,
Not all ftp sites have been updated yet. It may take a while. The alpha
binary is not there yet. I will upload the alpha binary this weekend.
The main thing in binutils 2.9.1.0.22b is the Pentium III support.
Please check it out and report any bugs back to me.
Thanks.
- --
H.J. Lu ([EMAIL PROTECTED])
- ---
WARNING: This release does not support Linux/PPC. Please don't use
it on Linux/PPC.
This should be final release for binutils 2.9.1.0.x based on binutils
2.9.1. I am planning to release to public this weekend. Please test it
as much as you can. Thanks.
This is the beta release of binutils 2.9.1.0.22b for Linux, which is
based on binutils 2.9.1 plus Linux/ARM support, some x86 assembler
changes, some PPC bug fixes, some alpha bug fixes and an exception
frame optimization bug fix.
Due to the exception frame optimization bug fix, it is highly
recommended that you recompile all your C++ codes. Otherwise,
exception handling may not work right when an exception is thrown.
Since I no longer have machine running libc 5, starting from this
release, there will be no pre-compiled binaries for libc 5.
There was some problem on Linux/alpha. The binaries generated by the
new binituls may not run correctly on Linux/alpha. It turned out it was
a bug in the alpha dynamic linker in glibc 2.0.6. The current glibc 2.1
and glibc 2.0.7 should be ok.
This release should work on linux/x86/alpha. There are some ELF bug
fixes. But I don't know if it fixes all the bugs reported on
linux/sparc, Linux/MIPS and linux/PPC. I'd like to hear reports on them.
I'd like to release it to public soon. Please test it as much as you
can.
Please report any bugs related to binutils 2.9.1.0.22b to [EMAIL PROTECTED]
Changes from binutils 2.9.1.0.21:
1. Add Pentium III support.
2. Add IBM 370 suppport.
3. Fix the weak undefined symbol handling.
Changes from binutils 2.9.1.0.20:
1. Ada demangle support.
2. Don't merge weak undefined symols with definitions from a shared
object when building shared object. Only for ELF.
3. Fix a 16bit x86 gas bug.
Changes from binutils 2.9.1.0.19a:
1. Enable ld for Solaris/x86.
2. Fix an ELF/i386 bfd/linker bug.
3. Fix a BFD bug.
4. Fix the ELF aligment.
5. Fix an AMD 3DNow! bug.
6. Fix ELF/x86 8/16-bit relocation bug.
7. Add --redefine-sym=old_form=new_form to objcopy.
8. Update cplus-dem.c from the egcs snapshot.
9. Support new Pentium II instructions.
10. Add --demangle/--no-demangle to ld.
Changes from binutils 2.9.1.0.21:
1. A PPC DWARF2 EH patch for gas.
Changes from binutils 2.9.1.0.19:
1. Allow '.' in the middle of a symbol name for the versioning script.
Changes from binutils 2.9.1.0.17:
1. An ELF bug fix.
Changes from binutils 2.9.1.0.16:
1. Some Linux/Sparc64 patches.
2. A shared library linking patch.
3. Update cplus-dem.c from egcs 1.1.1 release.
Changes from binutils 2.9.1.0.15:
1. Update cplus-dem.c from egcs 1.1.1 prerelease.
2. Fix ARM bugs.
3. Fix MIPS/ELF bugs.
4. Fix an objdump bug.
Changes from binutils 2.9.1.0.14:
1. Update the program header handling bug fix from the binutils
snapshot.
2. Added AMD 3DNow! support to disassembler.
Changes from binutils 2.9.1.0.13:
1. An ELF bug fix for program header handling.
2. Added AMD 3DNow! support.
3. Add some vxworks suppport.
4. Fix ld on none-linux platforms.
Changes from binutils 2.9.1.0.12:
1. An ELF/alpha bug fix for creating large shared libraries.
2. An ELF/PPC bug fix.
Changes from binutils 2.9.1.0.11:
1. Use the real fix from Ian for the exception frame optimization bug.
Changes from binutils 2.9.1.0.10:
1. Fix an exception frame optimization bug.
Changes from binutils 2.9.1.0.9:
1. Fix another -Bsymbolic bug for Linux/alpha.
Changes from binutils 2.9.1.0.7:
1. Fix -Bsymbolic for Linux/alpha.
2. Fix a 16bit x86 gas bug.
Changes from binutils 2.9.1.0.6:
1. Fix various ARM bugs.
Changes from binutils 2.9.1.0.5:
1. A MIPS assembler ".align" bug is fixed.
2. bfd.h, bfd.h and bfdlink.h are included in the binary package.
Changes from binutils 2.9.1.0.4:
1. 2 x86 16bit mode assembler bugs, "ret" and "movb $35,0x4(%di)", are
fixed.
IMPORTANT:
The .plt format that the Alpha was using was not thread safe. So I
changed it. The new format is *not* binary compatible with the old,
thus you must use glibc 2.0.4 to get an ld.so that can understand it.
Note that the new ld.so knows how to deal with the old .plt format, so
old libraries will still work, but they should be relinked eventually
for performance reasons.
The file list:
1. binutils-2.9.1.0.22b.tar.gz. Source code.
2. binutils-2.9.1.0.21-2.9.1.0.22b.diff.gz. Patch against the previous
beta source code.
3. binutils-2.9.1.0.22b-glibc.x86.tar.gz. Precompiled Linux/x86 binaries
for libc 6 (glibc 2.0.7 1998-12-11 or above).
4. binutils-2.9.1.0.22b-alpha.tar.gz. Precompiled Linux/alpha binaries
for glibc 2.0.7 1998-12-11 or above.
5. binutils.spec. A RPM spec file for RedHat 5.2.
The primary ftp sites for the Linux binutils are:
1. ftp://ftp.varesearch.com/pub/support/hjl/binutils
2. ftp://ftp.kernel.org/pub/linux/devel/gcc
3. ftp://tsx-11.mit.edu/pub/linux/packages/GCC
4. ftp://sunsite.unc.edu/pub/Linux/GCC
The beta directory is in private/tofu under the GCC directory.
To install the binary package, please follow the procedure very closely.
Please backup/save all the files you are instructed to delete and you
should do
gzip -dc binutils-2.9.1.0.22b-glibc.x86.tar.gz | tar tvvf -
or
gzip -dc binutils-2.9.1.0.22b-alpha.tar.gz | tar tvvf -
to see what is in there.
Please do back up before you remove things.
To install for libc 6 (glibc 2.0.5c or above), PLEASE DO
1. su root
2. cd /
3. rm -f /usr/bin/encaps /usr/bin/nm
4. gzip -dc binutils-2.9.1.0.22b-glibc.x86.tar.gz | tar xvvf -
5. ldconfig
Now you have the new gas/binutils under /usr/bin and
/usr/ix86-linuxaout/bin. You have to use
/usr/ix86-linuxaout/bin/as
and
/usr/ix86-linuxaout/bin/ld -m i386linux
if you want to use a.out as and ld directly.
To install for alpha, PLEASE DO
1. su root
2. cd /
3. gzip -dc binutils-2.9.1.0.22b-alpha.tar.gz | tar xvvf -
4. ldconfig
I have changed the target names for Linux/x86 and Linux/x86 (a.out)
to ix86-linux and ix86-linuxaout respectively. The precompiled
binaries are installed under /usr/ix86-linux and /usr/ix86-linuxaout.
You should make appropriate symbolic links if you have a different
name for the Linux/x86 target, like i586-unknown-linux.
The target name for Linux/alpha is alpha-linux. The precompiled alpha
binaries are installed under /usr/alpha-linux. You should make
appropriate symbolic links if you have a different name for the
Linux/alpha target, like alpha-redhat-linux.
If you have an old linux library in the a.out format and you cannot
obtain the newer version in the ELF format for whatever reason, you
can try "objcopy --remove-leading-char" on the a.out library and see
if it can link with your code in ELF.
Thanks.
H.J. Lu
[EMAIL PROTECTED]
02/26/99
------------------------------
End of linux-gcc-digest V1 #362
*******************************
To subscribe to linux-gcc-digest, send the command:
subscribe linux-gcc-digest
in the body of a message to "[EMAIL PROTECTED]". If you want
to subscribe something other than the account the mail is coming from,
such as a local redistribution list, then append that address to the
"subscribe" command; for example, to subscribe "local-linux-gcc":
subscribe linux-gcc-digest [EMAIL PROTECTED]
A non-digest (direct mail) version of this list is also available; to
subscribe to that instead, replace all instances of "linux-gcc-digest"
in the commands above with "linux-gcc".
