Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Paul Bame <bame@endor.fc.hp.com>
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] building a glibc-based tool chain
Date: Tue, 11 Apr 2000 09:50:55 -0600	[thread overview]
Message-ID: <E12f2wJ-0002l4-00@endor.fc.hp.com> (raw)
In-Reply-To: Your message of "09 Apr 2000 12:17:13 EDT." <87em8fjlkm.fsf@tarwebok.thepuffingroup.com>

= > So, crtbegin/crtend are related to constructors and destructors for C++.  I

I've been editing them out of the spec file by hand, but I suspect that
configure --disable-shared and setting the gcc configure languages list
to dis-include C++ might work too.  (If the lang list only had C in it,
the build might be faster too)

Another thing which is handy is to 'cd gcc; ln -s ../binutils .'
After this, the configure/make/make-install inside the gcc directory
properly handles binutils, so you don't have to do it separately and
it solves some of the installation problems I had before.

The linker problem is always where I end up stuck.  I tried mangling
the vmlinux.lds to link my hello world and that didn't work either,
but I'm NO linker expert.  FYI I added an assert() (it's in CVS) which
catches the linker segfault (binutils/bfd/elf32something) if anyone
wants to become a linker expert and figure it out :-)

	-P

  parent reply	other threads:[~2000-04-11 15:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-06 18:05 [parisc-linux] building a glibc-based tool chain Paul Bame
2000-04-09  6:06 ` Bdale Garbee
2000-04-09  7:27   ` Bdale Garbee
2000-04-09 16:17     ` David Huggins-Daines
2000-04-09 16:56       ` Bdale Garbee
2000-04-11 15:50       ` Paul Bame [this message]
2000-04-13 23:38         ` Paul Bame
2000-04-14 21:48           ` David Huggins-Daines

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=E12f2wJ-0002l4-00@endor.fc.hp.com \
    --to=bame@endor.fc.hp.com \
    --cc=parisc-linux@thepuffingroup.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