LIBTOOLIZE(1)

πŸ“¦
version 2.6.2 Β· 2 versions
, in nixpkgs unstable

πŸ’… LIBTOOLIZE(1) β€” like, the User Commands manual, bestie

okay so picture this: you've got a package, and it wants to use libtool. libtoolize is the little gremlin that goes in and sets all that up for you. she's giving setup-wizard main character energy and honestly? she ate. 🧚✨


✨ SYNOPSIS ✨

libtoolize [OPTION]...

that's it. that's the whole vibe check. options only, no positional args, no drama. πŸŽ€


🌸 DESCRIPTION 🌸

libtoolize prepares a package to use libtool. literally her whole job. she clocks in, she preps your package, she clocks out. πŸ’…


πŸ”₯ OPTIONS πŸ”₯

  • -c, --copy β€” copy the files instead of symlinking them. no shortcuts, no "we're pointing at the same inode", just real actual copies. 🫢
  • --debug β€” turns on verbose shell tracing. she will narrate everything. 😭
  • -n, --dry-run β€” prints the commands instead of running them. rehearsal mode, nothing gets touched, zero consequences. πŸ™ˆ
  • -f, --force β€” replaces files that already exist. she's not asking, she's telling. πŸ’€
  • -i, --install β€” copies any missing auxiliary files. the ones you forgot? yeah, she's got you. ✨
  • --ltdl[=DIR] β€” installs libltdl sources, and DIR defaults to libltdl. (note the optional-argument brackets, iykyk πŸ‘€)
  • --no-warnings β€” same thing as -Wnone. exact same. don't @ me.
  • --nonrecursive β€” preps ltdl for non-recursive make.
  • -q, --quiet β€” works silently. no commentary, she's just built different. 🀫
  • --recursive β€” preps ltdl for recursive make.
  • --subproject β€” preps ltdl to configure and build independently. she's got her own apartment now. πŸ¦‹
  • -v, --verbose β€” verbosely reports processing. yes bestie, tell me everything. πŸ—£οΈ
  • --version β€” prints version info and exits. short and sweet.
  • -W, --warnings=CATEGORY β€” reports the warnings falling in CATEGORY, and the default is all.
  • -h, --help β€” prints the short help, or the long one. depends on how much you ask.

πŸŽ€ Warning categories include: πŸŽ€

  • 'all' β€” shows all the warnings. every single one. buckle up. πŸ’–
  • 'none' β€” turns off all the warnings. blissful silence.
  • 'error' β€” warnings get treated as fatal errors. so, uh, they're not warnings anymore, they're the whole crisis. 😭
  • 'environment' β€” shows warnings about what's inside LIBTOOLIZE_OPTIONS.
  • 'file' β€” shows warnings about file copying and linking.

🌈 the environment variable era 🌈

the following space or comma delimited options can be passed to libtoolize through the environment variable LIBTOOLIZE_OPTIONS. and like β€” unknown environment options are just ignored. she's not gonna fight you about it. 🫢

  • --debug β€” enables verbose shell tracing.
  • --no-warnings β€” doesn't display warning messages.
  • --quiet β€” works silently.
  • --verbose β€” verbosely reports processing.

🚨 the rules, bestie 🚨

you must cd to the top directory of your package before you run libtoolize. like, top-level. not nested. not vibing in src/. the top. i don't make the rules (i do, actually, well β€” libtool does). πŸ’€

πŸ› when you report a bug πŸ›

please describe a test case that reproduces it, and include the following info, okay? this is the part where you help her help you:

  • host-triplet: x86_64-pc-linux-gnu
  • version: libtoolize (GNU libtool) 2.6.2
  • automake: automake (GNU automake) 1.18.1
  • autoconf: autoconf (GNU Autoconf) 2.73

πŸ‘‘ AUTHOR πŸ‘‘

Written by Gary V. Vaughan <gary@gnu.org>, 2003. an absolute icon, we stan. 🌟


πŸ’œ REPORTING BUGS πŸ’œ


Copyright Β© 2026 Free Software Foundation, Inc. License GPLv2+: GNU GPL version 2 or later <https://gnu.org/licenses/gpl.html>

This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. and yes the caps on NO WARRANTY are load-bearing, that's the legal equivalent of her screaming it. 😀


πŸ¦‹ SEE ALSO πŸ¦‹

the full documentation for libtoolize is maintained as a Texinfo manual. if the info and libtoolize programs are properly installed at your site, this command:

info libtoolize

should give you access to the complete manual. go forth and read, bestie. πŸ“–βœ¨


that's the whole page!! πŸŽ‰ this little gem is from GNU libtool 2.6.2, dated July 2026 β€” mwah, sending you off with a kiss and a working configure.ac πŸ’‹πŸ’–

πŸ“¦ where this page comes from