public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Riker <TimR@CalderaSystems.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] building the toolchain
Date: Wed, 23 Feb 2000 07:10:10 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678204965@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678204943@msgid-missing>

One should keep in mind that source RPMs tipically do both. They use one
prefix when building so that all binaries get the right paths as Jim
mentioned. An then they install with a different prefix so that the
files get installed into a prefixed virtual tree that can be packaged.
When the package is unpacked the files are unpacked into the correct
locations that the binaries are expecting.

build prefix might be /usr and install prefix /tmp/package-version/usr
and so on.

Jim Wilson wrote:
> 
>         The only trouble I had was with 'make install prefix=/usr/local/ia64/'
>         command, where the Makefile in build/itcl/iwidgets3.0.0/unix needed to be
>         fixed a bit, to point to the TCL and TK directories within the top-level src
>         directory.
> 
> The recommended way to build the toolchain is to specify prefix when
> configuring, not when installing.  E.g., something like
>         configure --prefix=/usr/local/ia64 ...
>         make all
>         make install
> If you give the prefix at configure time, then programs with builtin pathnames
> will have the correct pathnames.  If you give the prefix at install time,
> some programs may fail to work, unless you set an environment variable or
> use a command line option to override the default pathnames.
> 
> If you did not specify a prefix to configure, this may explain why
> itcl/iwidgets3.0.0/unix got confused.  configure thought you were building
> something for /usr/local by default, it noticed that there was already tcl/tk
> stuff in /usr/local, and tried to use it.  This stuff is obviously wrong for
> a cross compiler though.  And it is also wrong because you ended up with
> pathnames pointing to someone else's tcl/tk source tree.
> 
>         What I haven't yet seen is a glibc release (with include files) that lets
>         you build even simple IA64 apps.
> 
> This is unfortunate.
> 
> However, there are glibc sources in /usr/src on the OS CD-rom.  If you are
> feeling adventurous, you could try to compile them yourself.  I haven't
> tried this myself.  I'll probably wait until the linux distributors have
> something ready.
> 
> Jim
> 
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64

-- 
Tim Riker - http://rikers.org/ - short SIGs! <g>
All I need to know I could have learned in Kindergarten
... if I'd just been paying attention.



      parent reply	other threads:[~2000-02-23  7:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-20 19:32 [Linux-ia64] building the toolchain Tim Riker
2000-02-20 20:18 ` Uros Prestor
2000-02-21  4:00 ` Matt_Domsch
2000-02-21 21:35 ` Jim Wilson
2000-02-22 10:34 ` Jes Sorensen
2000-02-23  5:07 ` Jim Wilson
2000-02-23  7:10 ` Tim Riker [this message]

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=marc-linux-ia64-105590678204965@msgid-missing \
    --to=timr@calderasystems.com \
    --cc=linux-ia64@vger.kernel.org \
    /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