os161 make error in Solaris 10.

[Database Administrator]

I have installed

* binutils
* gcc
* gdb
* sys161


successfully though I needed to change some configuration(renamed nawk
to awk, renamed gmake to make and make to make.orig).

Now this is the final stage of installation. I extract the
os161-1.11.tar.gz and then cd to extracted dir.

../configure command succeeds.
When I apply make(the last one) command errors occurs. I am little bit
frustrated by so many errors in Solaris and resolving then. If anyone
can identify the problem and give me hints or solutions it will be
greatly appreciated. Here's the output of make command (the error
segment)

$make
make includes
......................................
....................etc.............
......................................
gcc -Wall -W -Wwrite-strings -O2 -I/export/home/Linux/cs161/root/
hostinclude -DHOST -c mksfs.c -o mksfs.ho
In file included from mksfs.c:7:
support.h:32:2: #error "HAS_NO_SIZED_TYPES defined and I don't know
what the sizes should be"
In file included from mksfs.c:8:
/export/home/Linux/cs161/root/hostinclude/kern/sfs.h:36: error: syntax
error before "u_int32_t"
/export/home/Linux/cs161/root/hostinclude/kern/sfs.h:36: warning: no
semicolon at end of struct or union
/export/home/Linux/cs161/root/hostinclude/kern/sfs.h:37: warning: type
defaults to `int' in declaration of `sp_nblocks'
/export/home/Linux/cs161/root/hostinclude/kern/sfs.h:37: warning: data
definition has no type or storage class
/export/home/Linux/cs161/root/hostinclude/kern/sfs.h:39: error: syntax
error before "reserved"
.......... and more errors.............

Please mention if more information is required. I am using Solaris 10
on an Intel x86 machine.

[Database Administrator]

On Wed, 12 Nov 2008 04:00:13 -0800 (PST), Solaris BD wrote:
> I have installed
>
> * binutils
> * gcc
> * gdb
> * sys161
>
>
> successfully though I needed to change some configuration(renamed nawk
> to awk, renamed gmake to make and make to make.orig).

This is not a good idea. In a make environment, you can usually use make
environment variables instead of command names, for instance
AWK = nawk
MAKE = gmake
and so on. This risks breaking nothing, unlike renaming binaries.

> Now this is the final stage of installation. I extract the
> os161-1.11.tar.gz and then cd to extracted dir.
>
> ./configure command succeeds.
> When I apply make(the last one) command errors occurs. I am little bit
> frustrated by so many errors in Solaris and resolving then. If anyone
> can identify the problem and give me hints or solutions it will be
> greatly appreciated. Here's the output of make command (the error
> segment)

I'm not sure what Sun can be expected to do when faced with poorly
written non-portable code. Solaris conforms to SUSv3.

> $make
> make includes
> .....................................
> ...................etc.............
> .....................................
> gcc -Wall -W -Wwrite-strings -O2 -I/export/home/Linux/cs161/root/
> hostinclude -DHOST -c mksfs.c -o mksfs.ho

You are using gcc without -ansi -pedantic. This means that it compiles
GCC C, which may not be standard C. -Wall -Wextra isn't too bad though.

Please post the lines of code pointed to by the errors.

A bientot
Paul
--
Paul Floyd http://paulf.free.fr

[Database Administrator]

I used make=gmake at the first idea. And it didn't work. But if I use
MAKE=gmake it works little bit because $MAKE is at least replaced by
gmake. But if the string make is not replaced. gmake will be only
replaced if $make is found. If you have different ideas please
explain.

Though there is too much linuxism in the code of os161, I had been
able to compile os161 finally. gcc seems to be okay. Can you please
mention the differences you experienced? Because I thought gcc is same
in every platform.

The error was in a header file named support.h where some preprocessor
directives were not declared for archicture x86 (Solaris). After
defining them I was able to build.


Thanks very much for your valuable information.

[Database Administrator]

On 2008-11-13 13:46:04 +0000, Solaris BD said:

> I used make=gmake at the first idea. And it didn't work. But if I use
> MAKE=gmake it works little bit because $MAKE is at least replaced by
> gmake. But if the string make is not replaced. gmake will be only
> replaced if $make is found. If you have different ideas please
> explain.

Use:

export MAKE=gmake
export CC=...
../configure ...
$MAKE

> Though there is too much linuxism in the code of os161, I had been
> able to compile os161 finally. gcc seems to be okay. Can you please
> mention the differences you experienced? Because I thought gcc is same
> in every platform.

No, gcc is different on every platform. On OS X you pass gcc -framework
flags etc etc. Linking is very different on different systems too, so
the flags passed to the linkers are going to be different.

--
Chris