Where is “gcc_tooldirâ€
Multi tool use
Clash Royale CLAN TAG#URR8PPP
up vote
2
down vote
favorite
Under Cross-Compiler-Specific Options, it says:
The default value, in case
--with-sysrootis not given an argument, is
$gcc_tooldir/sys-root.
but it appears that gcc_tooldir is not defined. Is this a nickname for
something else, and also where is it "normally"?
compiling gcc gnu configure
asked May 3 at 1:08
Steven Penny
2,28821635
add a comment |Â
up vote
2
down vote
favorite
Under Cross-Compiler-Specific Options, it says:
The default value, in case
--with-sysrootis not given an argument, is
$gcc_tooldir/sys-root.
but it appears that gcc_tooldir is not defined. Is this a nickname for
something else, and also where is it "normally"?
compiling gcc gnu configure
asked May 3 at 1:08
Steven Penny
2,28821635
Just to be clear: it is your intention to build a cross-compiling version of GCC, but not to build the GNU C library from the same source tree, yes? Because that's the use case for the--with-sysrootoption.
– John Bollinger
May 7 at 15:56
@JohnBollinger yes github.com/svnpenn/glade/blob/master/mingw-w64-x86-64/gcc/…
– Steven Penny
May 7 at 16:56
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
Under Cross-Compiler-Specific Options, it says:
The default value, in case
--with-sysrootis not given an argument, is
$gcc_tooldir/sys-root.
but it appears that gcc_tooldir is not defined. Is this a nickname for
something else, and also where is it "normally"?
compiling gcc gnu configure
asked May 3 at 1:08
Steven Penny
2,28821635
Under Cross-Compiler-Specific Options, it says:
The default value, in case
--with-sysrootis not given an argument, is
$gcc_tooldir/sys-root.
but it appears that gcc_tooldir is not defined. Is this a nickname for
something else, and also where is it "normally"?
compiling gcc gnu configure
asked May 3 at 1:08
Steven Penny
2,28821635
asked May 3 at 1:08
Steven Penny
2,28821635
asked May 3 at 1:08
Steven Penny
2,28821635
asked May 3 at 1:08
Steven Penny
2,28821635
2,28821635
Just to be clear: it is your intention to build a cross-compiling version of GCC, but not to build the GNU C library from the same source tree, yes? Because that's the use case for the--with-sysrootoption.
– John Bollinger
May 7 at 15:56
@JohnBollinger yes github.com/svnpenn/glade/blob/master/mingw-w64-x86-64/gcc/…
– Steven Penny
May 7 at 16:56
add a comment |Â
Just to be clear: it is your intention to build a cross-compiling version of GCC, but not to build the GNU C library from the same source tree, yes? Because that's the use case for the--with-sysrootoption.
– John Bollinger
May 7 at 15:56
@JohnBollinger yes github.com/svnpenn/glade/blob/master/mingw-w64-x86-64/gcc/…
– Steven Penny
May 7 at 16:56
Just to be clear: it is your intention to build a cross-compiling version of GCC, but not to build the GNU C library from the same source tree, yes? Because that's the use case for the
--with-sysroot option.– John Bollinger
May 7 at 15:56
Just to be clear: it is your intention to build a cross-compiling version of GCC, but not to build the GNU C library from the same source tree, yes? Because that's the use case for the
--with-sysroot option.– John Bollinger
May 7 at 15:56
@JohnBollinger yes github.com/svnpenn/glade/blob/master/mingw-w64-x86-64/gcc/…
– Steven Penny
May 7 at 16:56
@JohnBollinger yes github.com/svnpenn/glade/blob/master/mingw-w64-x86-64/gcc/…
– Steven Penny
May 7 at 16:56
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
but it appears that gcc_tooldir is not defined. Is this a nickname for something else, and also where is it "normally"?
gcc_tooldir is a make variable. You should find that within the scope of a GCC build, it has a value that is functionally equivalent to that of the $(tooldir) make variable, but somewhat different in form. You are not meant to set it by hand, though you may of course use the --with-sysroot configure option to choose your own directory for the target tools. Per the GCC build documentation:
When installing cross-compilers, GCC’s executables are not only installed into
bindir, that is,exec-prefix/bin, but additionally intoexec-prefix/target-alias/bin, if that directory exists. Typically, such tooldirs hold target-specific binutils, including assembler and linker.
(Emphasis in the original.)
The standard tooldir name is thus something of the form '/usr/x86_64-w64-mingw32', to lift one from the Glade example you presented in comments.
answered May 7 at 19:25
John Bollinger
2168
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
but it appears that gcc_tooldir is not defined. Is this a nickname for something else, and also where is it "normally"?
gcc_tooldir is a make variable. You should find that within the scope of a GCC build, it has a value that is functionally equivalent to that of the $(tooldir) make variable, but somewhat different in form. You are not meant to set it by hand, though you may of course use the --with-sysroot configure option to choose your own directory for the target tools. Per the GCC build documentation:
When installing cross-compilers, GCC’s executables are not only installed into
bindir, that is,exec-prefix/bin, but additionally intoexec-prefix/target-alias/bin, if that directory exists. Typically, such tooldirs hold target-specific binutils, including assembler and linker.
(Emphasis in the original.)
The standard tooldir name is thus something of the form '/usr/x86_64-w64-mingw32', to lift one from the Glade example you presented in comments.
answered May 7 at 19:25
John Bollinger
2168
add a comment |Â
up vote
1
down vote
accepted
but it appears that gcc_tooldir is not defined. Is this a nickname for something else, and also where is it "normally"?
gcc_tooldir is a make variable. You should find that within the scope of a GCC build, it has a value that is functionally equivalent to that of the $(tooldir) make variable, but somewhat different in form. You are not meant to set it by hand, though you may of course use the --with-sysroot configure option to choose your own directory for the target tools. Per the GCC build documentation:
When installing cross-compilers, GCC’s executables are not only installed into
bindir, that is,exec-prefix/bin, but additionally intoexec-prefix/target-alias/bin, if that directory exists. Typically, such tooldirs hold target-specific binutils, including assembler and linker.
(Emphasis in the original.)
The standard tooldir name is thus something of the form '/usr/x86_64-w64-mingw32', to lift one from the Glade example you presented in comments.
answered May 7 at 19:25
John Bollinger
2168
add a comment |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
but it appears that gcc_tooldir is not defined. Is this a nickname for something else, and also where is it "normally"?
gcc_tooldir is a make variable. You should find that within the scope of a GCC build, it has a value that is functionally equivalent to that of the $(tooldir) make variable, but somewhat different in form. You are not meant to set it by hand, though you may of course use the --with-sysroot configure option to choose your own directory for the target tools. Per the GCC build documentation:
When installing cross-compilers, GCC’s executables are not only installed into
bindir, that is,exec-prefix/bin, but additionally intoexec-prefix/target-alias/bin, if that directory exists. Typically, such tooldirs hold target-specific binutils, including assembler and linker.
(Emphasis in the original.)
The standard tooldir name is thus something of the form '/usr/x86_64-w64-mingw32', to lift one from the Glade example you presented in comments.
answered May 7 at 19:25
John Bollinger
2168
but it appears that gcc_tooldir is not defined. Is this a nickname for something else, and also where is it "normally"?
gcc_tooldir is a make variable. You should find that within the scope of a GCC build, it has a value that is functionally equivalent to that of the $(tooldir) make variable, but somewhat different in form. You are not meant to set it by hand, though you may of course use the --with-sysroot configure option to choose your own directory for the target tools. Per the GCC build documentation:
When installing cross-compilers, GCC’s executables are not only installed into
bindir, that is,exec-prefix/bin, but additionally intoexec-prefix/target-alias/bin, if that directory exists. Typically, such tooldirs hold target-specific binutils, including assembler and linker.
(Emphasis in the original.)
The standard tooldir name is thus something of the form '/usr/x86_64-w64-mingw32', to lift one from the Glade example you presented in comments.
answered May 7 at 19:25
John Bollinger
2168
answered May 7 at 19:25
John Bollinger
2168
answered May 7 at 19:25
John Bollinger
2168
answered May 7 at 19:25
John Bollinger
2168
2168
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f441431%2fwhere-is-gcc-tooldir%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Just to be clear: it is your intention to build a cross-compiling version of GCC, but not to build the GNU C library from the same source tree, yes? Because that's the use case for the
--with-sysrootoption.– John Bollinger
May 7 at 15:56
@JohnBollinger yes github.com/svnpenn/glade/blob/master/mingw-w64-x86-64/gcc/…
– Steven Penny
May 7 at 16:56