The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Pat.Villani@hp.com (Pat Villani)
Subject: 32V update (was Re: [TUHS] While on the subject of 32V ...)
Date: Tue, 04 Nov 2003 08:51:24 -0500	[thread overview]
Message-ID: <3FA7AEDC.3000602@hp.com> (raw)
In-Reply-To: <200311042256.50072.wes.parish@paradise.net.nz>

For what you're doing, I think you'll want to add -nostdinc, and 
-nodefaultlibs to your gcc command line.  The -nostdinc option stops the 
compiler from looking at the standard include path files, and the 
-nodefaultlibs option causes the compiler to not use any of the gcc 
libraries while still using the standard startup file.  You'll have to 
supply the paths to the headers and libraries yourself.

In case I'm wrong, and you need to supply your own startup code as well, 
change the -nodefaultlibs option to -nostdlib.  That drops all standard 
startup code and libraries from the build.  It's the set of options I'm 
using in the current kernel build (to be released next week some time).

According to the gcc docs, the compiler may generate calls to memcmp, 
memset, and memcpy.  That means they'll be the first calls you'll have 
to implement in your libraries.

Pat

Wesley Parish wrote:
> I'm trying to work out whether or not gcc takes a look at its own header files 
> before or after it looks at the ones I've set it to look at - I got some 
> weird warnings and error messages before I expanded the -I to 
> 
> gcc -I./../../include -I./../../include/sys -I./../sys/h
> 
> Still need the *.s files in the libraries dealt with, and as before, I know 
> nothing of the VAX assembler syntax and mostly x86 in Intel syntax.
> 
> If anyone wants to join in with this, I would be very, very grateful.
> 
> Wesley Parish
> 
> P.S.  I've got to redo the utilities - I think that once I get the libraries 
> sorted out, the utilities will be easy meat.
> 
> On Tue, 04 Nov 2003 04:34, Pat Villani wrote:
> 
>>Good progress.  I'll probably use a linux like system call mechanism, so
>>expect an inline function for the system calls.
>>
>>Pat
>>
>>Wesley Parish wrote:
>>
>>>Just an update - I'm now compiling ~/[...]/32V/usr/src/libc/gen to *.o
>>>using gcc set with -I../../include .  Most of them compile smoothly.
>>>
>>>I hope I'll have most of the library compiled to *.o soon, enough for
>>>using as the basis for compiling the utilities to 32I.
>>>
>>>Wesley Parish
> 
> 




  reply	other threads:[~2003-11-04 13:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-20 13:35 [TUHS] While on the subject of 32V Pat Villani
2003-10-21  0:50 ` Wesley Parish
2003-10-21 14:00   ` Pat Villani
2003-10-22  8:10     ` Wesley Parish
2003-10-24 13:41       ` Pat Villani
2003-10-29  9:01         ` Wesley Parish
2003-10-30 12:56         ` 32V update (was Re: [TUHS] While on the subject of 32V ...) Pat Villani
2003-10-31 10:13           ` Wesley Parish
2003-10-31 14:26             ` Pat Villani
2003-11-05  2:22           ` Greg Lehey
2003-11-05 12:53             ` Pat Villani
     [not found] ` <200311022346.34747.wes.parish@paradise.net.nz>
     [not found]   ` <oprx0h6gtdrveh1e@smtp.borf.com>
2003-11-03 10:48     ` Wesley Parish
2003-11-03 15:34       ` Pat Villani
2003-11-04  9:56         ` Wesley Parish
2003-11-04 13:51           ` Pat Villani [this message]
2003-10-31 22:37 Robertdkeys
2003-10-31 23:53 ` Gregg C Levine
2003-11-04 18:18 macbiesz
2003-11-05 10:23 ` Wesley Parish

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3FA7AEDC.3000602@hp.com \
    --to=pat.villani@hp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).