From: Mikael Hallendal <hallski@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] make install suggestion/question
Date: Wed Jun 13 00:31:02 2001 [thread overview]
Message-ID: <87ofrsok8h.fsf@codefactory.se> (raw)
In-Reply-To: <992415733.15682.0.camel@atomic>
Aaron Blew <ablew@internetcds.com> writes:
> I have question/suggestion. Is it really necessary to put mozilla,
> gnome and others in /opt? I know it keeps it a bit more organzed and
> such, but it really makes it a pain when compiling things. Some
> programs, despite what they're told to use via the configure script
> insist on using includes from /usr/include instead of
> /opt/gnome/include. If not changing it, at least provide sympolic
> links or something (ie ln -s /usr/gnome/include/* /usr/include/ ). I
> think it would solve quite a few problems.
Hi!
I think it is wonderful to have a distribution that finally *does* put
things this way. I think it is better to fix those programs that
doesn't compile when GNOME (or KDE, mozilla) is located in other
locations than /usr since they are broken. They should be using
'gnome-config' in there Makefile (if they don't use auto*).
gnome-config --cflags libgnomeui for includes
gnome-config --libs libgnomeui for libs
If the configure-script is broken you can try to execute it with:
CFLAGS="-I/opt/gnome/include" LDFLAGS="-L/opt/gnome/lib" ./configure
Regards,
Mikael Hallendal
next prev parent reply other threads:[~2001-06-13 6:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 18:03 [gentoo-dev] make install suggestion/question Aaron Blew
2001-06-12 18:22 ` Thilo Bangert
2001-06-13 1:40 ` Aaron Blew
2001-06-13 1:41 ` Aaron Blew
2001-06-13 9:57 ` Holger Brueckner
2001-06-13 10:43 ` Ben Lutgens
2001-06-14 5:01 ` Achim Gottinger
2001-06-13 0:31 ` Mikael Hallendal [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-12 18:04 Aaron Blew
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=87ofrsok8h.fsf@codefactory.se \
--to=hallski@gentoo.org \
--cc=gentoo-dev@cvs.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