All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <Matthew.Wilcox@genedata.com>
To: Alex deVries <adevries@thepuffingroup.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] a question about HPUX's linker
Date: Fri, 11 Jun 1999 09:39:46 +0200	[thread overview]
Message-ID: <19990611093946.P31472@mencheca.ch.genedata.com> (raw)
In-Reply-To: <3760B67A.8D9F3B1F@thepuffingroup.com>; from Alex deVries on Fri, Jun 11, 1999 at 03:10:50AM -0400

On Fri, Jun 11, 1999 at 03:10:50AM -0400, Alex deVries wrote:
> 
> To help us get ahead, I'm trying to get the kernel to build properly
> with HPUX, using HPUX's linker, and gcc.
> 
> Why does the final kernel link use --start-group ... --end-group?
> 
> What's the equivalent syntax for HPUX's ld?
> 
> I'm a bit short on docs in this area...

This is something which happened towards the later days of 2.1
development.  It causes GNU ld to scan through the archives indicated
between --start-group and --end-group until no more symbols are resolved.
It is a GNU extension.  I think _in general_ it's not necessary, but
there are a few corner cases where this is needed.  Try taking it out,
tell us what errors you get.

Of course, this is all due to Linux's lame build scripts and they should
be replaced with something better.  which I don't have time to work on, of
course :-)

-- 
Matthew Wilcox <willy@bofh.ai>
"Windows and MacOS are products, contrived by engineers in the service of
specific companies. Unix, by contrast, is not so much a product as it is a
painstakingly compiled oral history of the hacker subculture." - N Stephenson

  reply	other threads:[~1999-06-11  7:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-11  7:10 [parisc-linux] a question about HPUX's linker Alex deVries
1999-06-11  7:39 ` Matthew Wilcox [this message]
1999-06-11 12:30 ` Alan Cox
1999-06-11 13:13 ` Marcus Thiessel

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=19990611093946.P31472@mencheca.ch.genedata.com \
    --to=matthew.wilcox@genedata.com \
    --cc=adevries@thepuffingroup.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.