Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
luatex
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
TeXLive
luatex
Commits
0c59e68d
Commit
0c59e68d
authored
5 years ago
by
Luigi Scarso
Browse files
Options
Downloads
Patches
Plain Diff
missed buildinfo.sh
parent
4a06a850
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
source/doc/buildinfo.sh
+60
-0
60 additions, 0 deletions
source/doc/buildinfo.sh
with
60 additions
and
0 deletions
source/doc/buildinfo.sh
0 → 100755
+
60
−
0
View file @
0c59e68d
#!/bin/sh
# $Id: buildinfo.sh 51449 2019-06-24 22:12:32Z karl $
# Public domain. Report basics of current system; run from top-level
# Makefile so any make overrides will be taken into account. (And from
# Build.) buildenv.log with full environment dump is also created.
do_config_status
=
true
if
test
"x
$1
"
=
x--no-config-status
;
then
shift
do_config_status
=
false
fi
printf
'UNAME\t"%s"\n'
"
`
uname
-a
`
"
# /etc/issue often contains only placeholders, so don't bother with it.
# Return version identification for $1, by calling it with --version.
# gcc on Macs, when linked to cc, has a useless "Configured with:" as
# the first line. Likely we'll need to generalize for other compilers.
# We intentionally don't quote $1 in case CC was set to something like
# "cc --someopt".
compiler_version
()
{
$1
--version
2>&1 |
grep
-v
'^Configured'
|
sed
1q
}
printf
'MAKE\t"%s"\n'
"
${
MAKE
-make
}
"
printf
'MAKE-v\t"%s"\n'
"
`
${
MAKE
-make
}
-v
2>&1 |
sed
1q
`
"
# BSD make does not give version info with -v, but the
# first line of the usage message is sort of an identifier.
# our configure defaults to using gcc and g++, so we will too.
printf
'CC\t"%s"\n'
"
${
CC
-gcc
}
"
printf
'CFLAGS\t"%s"\n'
"
${
CFLAGS
}
"
printf
'CC-v\t"%s"\n'
"
`
compiler_version
${
CC
-gcc
}
`
"
#
printf
'CXX\t"%s"\n'
"
${
CXX
-g++
}
"
printf
'CXXFLAGS\t"%s"\n'
"
${
CXXFLAGS
}
"
printf
'CXX-v\t"%s"\n'
"
`
compiler_version
${
CXX
-g++
}
`
"
#
printf
'OBJCXX\t"%s"\n'
"
${
OBJCXX
-cc
}
"
printf
'OBJCXXFLAGS\t"%s"\n'
"
${
OBJCXXFLAGS
}
"
#
printf
'LDFLAGS\t"%s"\n'
"
${
LDFLAGS
}
"
# Some Linux-based systems provide this, but don't worry if not there.
# Let's hope that other systems are sufficiently identified by uname,
# don't feel like doing a big system-information hunt. But if we do:
# http://www.datadisk.co.uk/html_docs/misc/unix_commands.htm
if
test
-n
"
`
lsb_release
-a
2>/dev/null
`
"
;
then
printf
'\nLSB_RELEASE\n'
lsb_release
-a
2>&1
fi
# the whole configure line and more, if requested.
# (We want this from make, but not from Build.)
$do_config_status
\
&&
test
-s
config.status
\
&&
(
printf
'\nCONFIG_STATUS\n'
;
./config.status
--version
|
sed
-n
'1,/^$/p'
)
exit
0
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment