Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Taylor <taylor@candd.org>
To: "Daniel Manfis" <dany_100@yahoo.com>
Cc: gdb@sourceware.cygnus.com
Subject: Re: Installing gdb alone and into a distinct directory.
Date: Tue, 22 May 2001 12:07:00 -0000	[thread overview]
Message-ID: <200105221906.PAA12864@houston.candd.org> (raw)

    From: "Daniel Manfis" <dany_100@yahoo.com>
    Date: Tue, 22 May 2001 21:36:33 +0200

    So, to sum up a questions:

    1)How it is possible to build gdb alone without building all the 
    other programs coming with it?

Assuming you want to not build libbfd, libiberty, libreadline, etc.,
but instead use installed versions, then the answer is: Not currently.

    2)If it is impossible to build gdb alone, what could i do so that gdb 
    will get installed into a separate directory, specified as a prefix, 
    while all the others will get installed into other directory (or 
    every one into it's own custom directory)?

    Daniel.

What I would suggest is *first* configure the entire tree to the
"throw away" location, *then* reconfigure those portions you want to
keep to a different location.  From your writeup, it sounded like you
were doing the reverse.

Note: if you want to install just gdb and not the other stuff, then
after a successfull make from the top level, you should be able to
just cd into the gdb subdirectory and type "make install" to have just
the gdb stuff installed without installing libbfd/libreadline/etc.


             reply	other threads:[~2001-05-22 12:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-22 12:07 David Taylor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-22 11:35 Daniel Manfis

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=200105221906.PAA12864@houston.candd.org \
    --to=taylor@candd.org \
    --cc=dany_100@yahoo.com \
    --cc=gdb@sourceware.cygnus.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