Why does just typing "see comp" cause a segmentation fault? Here are the details:
Welcome to OpenBIOS v1.0 built on Aug 12 2012 20:51
Type 'help' for detailed information
[unix] Booting default not supported.
No valid state has been set by load or init-program
0 > see comp
>r 0 -rot r> bounds (?do) panic: segmentation violation at 56
dict=0xb7e50008 here=0xb7e66eec(dict+0x16ee4) pc=0xb7e52ee4(dict+0x2edc)
dstackcnt=3 rstackcnt=26 instruction=b7e502ec
I am using the target unix if that helps.
I have a cross-compiler chain on 32-bit Windows XP using Cygwin that I use to build OpenBIOS.
Attached are my scripts for ppc64/ppc, sparc64/sparc, s390x/s390, x86_64/x86.
Also attached are two patches for OpenBIOS to build correctly with this Cygwin environment (one is just to set options and point to my cross-compilers but the other more importantly fixes some ldscripts so I can use my 64-bit/32-bit cross-compilers correctly to build the 32-bit OpenBIOS roms instead of linking to the default 64-bit C run-time).
--- On Mon, 8/13/12, Programmingkid <programmingkidx(a)gmail.com> wrote:
From: Programmingkid <programmingkidx(a)gmail.com>
Subject: [OpenBIOS] Building OpenBIOS - OS list
Date: Monday, August 13, 2012, 10:48 AM
Has OpenBIOS been successfully built on anything that isn't Linux? I was wondering if anyone has been able to build it on Mac OS X, Windows, or any thing else that isn't Linux.
Free your System - May the Forth be with you
On Aug 13, 2012, at 12:08 PM, openbios-request(a)openbios.org wrote:
> Message: 1
> Date: Sun, 05 Aug 2012 17:20:49 -0400
> From: Tarl Neustaedter <tarl-b2(a)tarl.net>
> To: The OpenBIOS Mailinglist <openbios(a)openbios.org>
> Subject: Re: [OpenBIOS] Bug in file unix.c
> Message-ID: <501EE3B1.6090407(a)tarl.net>
> Content-Type: text/plain; charset=windows-1252; format=flowed
> On 2012-Aug-5 15:36 , Programmingkid wrote:
>> I was trying to build openbios on Ubuntu 10.10 when I received this error message:
>> CC target/arch/unix/unix.o
>> cc1: warnings being treated as errors
>> ../arch/unix/unix.c: In function ?read_from_disk?:
>> ../arch/unix/unix.c:382: error: ignoring return value of ?read?, declared with attribute warn_unused_result
>> make: *** [target/arch/unix/unix.o] Error 1
>> make: Leaving directory `/home/user/Desktop/openbios-devel/obj-x86'
>> make: *** [build-verbose] Error 1
>> This is the command I used to build openbios:
>> ./config/scripts/switch-arch unix-x86
> That looks like your version of the C compiler has the ultra-pedantic
> errors turned on.
> Ignoring the return value for a function that returns one is (or at
> least used to be) legal C. Some recent compilers have decided to make it
> a fatal error. The fix is to place (void) in front of the particular
> invocation, to signal that yes, you know it returns a value, you've
> thought about it carefully, and you don't give a crap what the value is,
> and you still want to call this function without paying attention to the
> return value.
> As you may have gathered, I'm not a fan of this particular error check.
> It ends up cluttering code with lots of irrelevant casting. Since I
> regard casting as an indication of code weakness, adding piles of
> irrelevant casts (in my opinion) makes the code weaker - because it's
> harder to focus on the areas which actually are weak.
Still, this issue should be fixed. It does sound easy to fix and would make things a lot easier for anyone else who needed to build OpenBIOS on Ubuntu.
I was trying to build openbios on Ubuntu 10.10 when I received this error message:
cc1: warnings being treated as errors
../arch/unix/unix.c: In function ‘read_from_disk’:
../arch/unix/unix.c:382: error: ignoring return value of ‘read’, declared with attribute warn_unused_result
make: *** [target/arch/unix/unix.o] Error 1
make: Leaving directory `/home/user/Desktop/openbios-devel/obj-x86'
make: *** [build-verbose] Error 1
This is the command I used to build openbios: