public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "martin dot drab at fjfi dot cvut dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/36213] Wrong search path generation
Date: Fri, 23 May 2008 01:00:00 -0000	[thread overview]
Message-ID: <20080523010002.23835.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36213-8902@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from martin dot drab at fjfi dot cvut dot cz  2008-05-23 01:00 -------
(In reply to comment #5)
> Is there a reason why you are supplying all these weird configure options?
> 
> --exec-prefix=/usr/local/opt/MDL/opt/gcc-4.4 --sysconfdir=/etc
> --libdir=/usr/local/opt/MDL/opt/gcc-4.4/lib64
> --libexecdir=/usr/local/opt/MDL/opt/gcc-4.4/libexec64
> --includedir=/usr/local/opt/MDL/opt/gcc-4.4/include
> --infodir=/usr/local/opt/MDL/opt/gcc-4.4/share/info
> --mandir=/usr/local/opt/MDL/opt/gcc-4.4/share/man 
> 
> The default for them will be based on the prefix.

Just to make sure they are where I want them to be. Basically most of them need
not be there, because they are what they are based on the prefix. That's right.
I just want to make sure, that the 64-bit library and libexec dirs get the *64
at the end (because I use it all over the system that way - Gentoo ;) and I
really hate it when info and man is not generated into the share subdir. Though
I admit, that since I install the entire gcc into a separate directory, i can
probably leave this on automatic based on prefix. That's right.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36213


  parent reply	other threads:[~2008-05-23  1:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-11 19:40 [Bug preprocessor/36213] New: " martin dot drab at fjfi dot cvut dot cz
2008-05-11 19:44 ` [Bug preprocessor/36213] " martin dot drab at fjfi dot cvut dot cz
2008-05-11 19:44 ` martin dot drab at fjfi dot cvut dot cz
2008-05-22 20:08 ` [Bug middle-end/36213] " pinskia at gcc dot gnu dot org
2008-05-22 21:52 ` martin dot drab at fjfi dot cvut dot cz
2008-05-23  0:41 ` martin dot drab at fjfi dot cvut dot cz
2008-05-23  0:45 ` pinskia at gcc dot gnu dot org
2008-05-23  0:50 ` martin dot drab at fjfi dot cvut dot cz
2008-05-23  1:00 ` martin dot drab at fjfi dot cvut dot cz [this message]
2008-05-23  1:10 ` martin dot drab at fjfi dot cvut dot cz
2008-05-23 11:10 ` martin dot drab at fjfi dot cvut dot cz
2008-05-23 15:26 ` Ralf dot Wildenhues at gmx dot de
2008-05-23 16:06 ` martin dot drab at fjfi dot cvut dot cz

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=20080523010002.23835.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).