public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: John Matthews <jvmatthe@math.duke.edu>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] ebuild question
Date: 26 Jul 2002 10:54:30 -0400	[thread overview]
Message-ID: <1027695270.2327.8.camel@ph4tp1p3> (raw)

[-- Attachment #1: Type: text/plain, Size: 1623 bytes --]

I finally got a Crystal Space ebuild that I can deal with. Unf. there is
one step I need assistance with.

When issuing a "make install", the system looks at either the default
destination directory or the one you set. I've been trying
/usr/local/crystal and if I use that, then "make install" gets a sandbox
violation. If, however, I use ${D}/usr/local/crystal then it installs
but right before that step it rewrites the cs-config script (like
sdl-config, gtk-config, etc.) to say that the location of the CS libs
and headers is /var/tmp/portage/crystal-0.94-r2/image//usr/local/crystal
(or something like that, I don't have it in front of me right now). Of
course, that'll be a bogus location when the package is actually
installed.

Do I need to do some sed magic to fix that somehow, by twiddling with
the cs-config file that's been installed in the image? Or is there some
sort of standard clever way to get around this problem with
non-./configure-style packages?

Random other info:
Meanwhile, I'm still in a position where I can't build optimized builds
with gcc 3.x and I can't use assembler at all. I've been told that CS
requires a special version of nasm or something like that, but haven't
found a direct reference for what works yet. Building a debug build with
no assembler gets me a working install image, I believe, on gcc 3.x and
gcc 2.95.

Regards and thanks,
matt

-- 
Matt Matthews     \ ph: 919.660.2811        \ Use GNU/Linux  _o) w00t
Duke Univ., Postdoc\ jvmatthe@math.duke.edu  \____________   /\\
Dept. of Mathematics\ http://www.math.duke.edu/~jvmatthe/ \ _\_V

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]

             reply	other threads:[~2002-07-26 14:54 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-26 14:54 John Matthews [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-03  3:40 [gentoo-dev] ebuild question pepone pepone
2005-03-03  3:47 ` Jeremy Hanmer
2005-03-03 10:26   ` Aaron Walker
2005-03-03 20:23     ` Jeremy Hanmer
2005-03-04  0:42       ` Aaron Walker
2003-09-19 14:57 Philippe Lafoucrière
2003-09-19 15:03 ` Georgi Georgiev
2003-09-19 15:12   ` Philippe Lafoucrière
2003-09-19 15:26     ` Georgi Georgiev
2003-09-19 15:05 ` Thomas de Grenier de Latour
2003-09-19 15:15   ` Philippe Lafoucrière
2003-06-10 14:25 MAL
2003-06-12 11:34 ` Amiel Martin
2003-05-30 15:17 William Hubbs
2003-05-30 15:27 ` Grant Goodyear
2003-05-31  3:00   ` Georgi Georgiev
2003-05-30 11:15 MAL
2003-05-30 11:29 ` Alastair Tse
2003-05-30 14:22   ` MAL
2003-05-30 14:33     ` Alastair Tse
2003-05-30 14:40       ` Todd Berman
2003-05-30 14:55         ` Jon Portnoy
2003-05-30 15:08           ` MAL
2003-05-30 14:39     ` Seemant Kulleen
2003-05-30 15:09       ` Seemant Kulleen
2002-11-26 21:27 Per Wigren
2002-11-26 21:23 ` Dan Armak
2002-11-27  0:03   ` Per Wigren
2002-04-18  6:13 Avi Schwartz
2002-04-18  6:59 ` George Shapovalov
2002-04-18  7:15 ` Tod M Neidt
2002-04-17  5:21 Richard Jackson
2002-04-17  5:02 ` Jared H. Hudson
2002-04-17  6:05   ` Richard Jackson
2002-04-17  5:21     ` Jared H. Hudson
2002-02-07  3:44 Edward Muller
2002-02-07  4:43 ` Tod M Neidt
2001-08-05 15:50 Craig Joly
2001-08-05 17:07 ` Daniel Robbins

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=1027695270.2327.8.camel@ph4tp1p3 \
    --to=jvmatthe@math.duke.edu \
    --cc=gentoo-dev@gentoo.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