www.delorie.com/archives/browse.cgi   search  
Mail Archives: pgcc/1998/09/26/10:37:32

X-pop3-spooler: POP3MAIL 2.1.0 b 4 980420 -bs-
Message-ID: <19980926113359.A1249@nights.dhis.org>
Date: Sat, 26 Sep 1998 11:33:59 +0200
From: Matthias Dahl <matthew AT nights DOT dhis DOT org>
To: beastium-list AT Desk DOT nl
Subject: Huge Problems with PGCC 1.1 :-(
Reply-To: matthew AT nights DOT dhis DOT org
Mime-Version: 1.0
X-Mailer: Mutt 0.93.1i
X-Operating-System: LinuX 2.0.36pre1
Sender: Marc Lehmann <pcg AT goof DOT com>
Status: RO
X-Status: A
Lines: 68

]/ Howdy folks... \[

*** Please answer to my eMail address, because I'm not on this mailing list.
*** THANKs a lot in advance... :-)

I'm using PGCC since its 1.0.2 version, until now, without any problems.
Everything compiled fine, even the Kernel went through it and worked without
any notable problems.

Now I've *tried* to upgrade to PGCC 1.1 (not 1.1a - why is that older?).
Compiling the whole thing didn't make any trouble, except a few warnings
during the compile time, but it passed all three stages.

After installing the new version, I first tried to compile the Kernel. Both
versions I tried, 2.0.36pre1 as well as 2.0.35, were completely useless,
though they worked perfect with 1.0.3a ...

(Used -O6 -mpentium -march=pentium as optimizations)

Most of the time, loading kernel modules brought me the following message.

kernel: general protection: 0000
kernel: CPU:    0
kernel: EIP:    0010:[serial:register_serial_R3425f38c>]
kernel: EFLAGS: 00010202
kernel: eax: 04852e90   ebx: 00000001   ecx: 0332c214   edx: 00000001
kernel: esi: 02e87a18   edi: 0332c288   ebp: 02e87d18   esp: 02917f34
kernel: ds: 0018   es: 0018   fs: 002b   gs: 002b   ss: 0018
kernel: Process insmod (pid: 371, process nr: 37, stackpage=02917000)
kernel: Stack: 04852ea6 00000001 04853620 00114c60 0292e414 bffffcd4 0805c6c8
bffffc88 
kernel:        02e87a18 0332c288 0332c214 00000001 03333d18 00000101 02917f70
04852e90 
kernel:        04852ecc 00617070 0011054e 0292e414 03d82098 0805d000 00000001
001103e8 
kernel: Call Trace: [<04852ea6>] [<04853620>] [sys_init_module+928/972]
[<04852e90>] [<04852ecc>] [do_page_fault+358/808] [do_page_fault+0/808] 
kernel:        [do_wp_page+0/644] [error_code+64/80] [system_call+85/128] 
kernel: Code: 18 83 a0 03 80 c2 32 03 40 e9 84 04 38 7a e8 02 0b 00 00 00 

Also, depending on whether I had HAIFA enabled in PGCC, during the boot
process of the kernel, the background color changed to red and most of
the programs weren't able anymore to access some files on the harddisk,
this happened only when I had HAIFA disabled.

Are there any known serious bugs in this current release of PGCC? I did
compile PGCC twice on my machine (with & without HAIFA) and also tried it
on another one, but always the same effect, so it must be something with
the compiler itself. :-(

I'm using RedHAT 5.1 on an i586 with PGCC 1.0.3a, GLIBC 2.0.7 - most of
the stuff recompiled with PGCC. Also binutils 2.9.1.0.6 are installed here.

(I also tried the EGCS Kernel 2.0.x Patch, but it had no effect at all,
 except that the warnings were gone <g>)

BTW. Is it possible, that maybe compiling PGCC 1.1 doesn't work if you've
the previous version (1.0.3a) installed?

Thanks 4 any help I get in advance. :-)
(Please answer to my eMail address, as I'm no subscriber to this list! TNX!)

-- 
]\ MATTHEW @ NIGHTS.dhis.org
 / PGP Key @ Request via eMail
 \                                       \        WEB Master of the        /
 / Powered by LINUX 2.0.36pre1           / Dynamic Host Information System \
]\ The Choice of a GNU Generation        \       http://www.dhis.org       /

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019