Sponsored Content
Full Discussion: Make options for wget
Operating Systems BSD Make options for wget Post 302294394 by Neo on Thursday 5th of March 2009 06:12:34 AM
Old 03-05-2009
What does the wget readme file say about make configuration options?
 

8 More Discussions You Might Find Interesting

1. Linux

Error in issuing a make and make install

Hi, Recently I install a package and try to do a make and make install. However, in the make it gives me below error:- make:Nothing to be done for 'install-exec-am' make:Nothing to be done for 'install-data-am' Can anyone please explain to me what does this mean? I have been trying... (1 Reply)
Discussion started by: ahjiefreak
1 Replies

2. UNIX for Dummies Questions & Answers

cant make a http get request using wget

Hi all, Im trying to make an http get request to a web service from a linux machine like below and i get ERROR 500 wget http://10.1.21.236:8585/pns.asmx/Sen...&msgBody=werty 25018 $ --19:06:32-- http://10.1.21.236:8585/pns.asmx/Sen...erName=serverA Connecting to 10.1.21.236:8585...... (1 Reply)
Discussion started by: elthox
1 Replies

3. UNIX for Dummies Questions & Answers

Installing Apache with make options

I am installing apache on freebsd and the screen comes up with make options. Here I would like to deselect DAV and DAV_FS. How can this be done on the command line in order to achieve a silent install? This is what I have currently, but the installation script still enters the menu with the make... (2 Replies)
Discussion started by: figaro
2 Replies

4. Solaris

Gani Network Driver Won't Install - make: Fatal error: Don't know how to make targ...

I attached a README file that I will refer to. I successfully completed everything in the README file until step 4. # pwd /gani/gani-2.4.4 # ls COPYING Makefile.macros gem.c Makefile Makefile.sparc_gcc gem.h Makefile.amd64_gcc ... (1 Reply)
Discussion started by: Bradj47
1 Replies

5. UNIX for Dummies Questions & Answers

Difference between configure/make/make install.

Hi, While installation of apache on linux, we perform the below tasks. 1) Untar 2) configure 3) make 4) make install. I wanted to understand the difference and working of configure/make/make install. Can any one help me understanding this? Thanks in advance. (1 Reply)
Discussion started by: praveen_b744
1 Replies

6. Ubuntu

Kernel boot options removed by fault, no boot options

Hello Everyone, First of all, I highly appreciate all Linux forum members and whole Linux community. http://forums.linuxmint.com/images/smilies/icon_wink.gif. I wish you the best for all of you ! I will try to be short and concise: I am using Linux Mint 10 for 2 months on 2 ws, and all went... (3 Replies)
Discussion started by: cdt
3 Replies

7. Shell Programming and Scripting

How to make sure the input string is one of many options?

How to make sure the input string is one of many options e.g centos-5.5-i386 windows-2003r2-x64 ? The options are dynamic, so "case" condition check doesn't work. I use grep -o -w , it doesn't work every time because - is valid word boundry #word windows-2003 failed the check as expected... (4 Replies)
Discussion started by: honglus
4 Replies

8. Shell Programming and Scripting

Wget - working in browser but cannot download from wget

Hi, I need to download a zip file from my the below US govt link. https://www.sam.gov/SAMPortal/extractfiledownload?role=WW&version=SAM&filename=SAM_PUBLIC_MONTHLY_20160207.ZIP I only have wget utility installed on the server. When I use the below command, I am getting error 403... (2 Replies)
Discussion started by: Prasannag87
2 Replies
Pod::Readme(3pm)					User Contributed Perl Documentation					  Pod::Readme(3pm)

NAME
Pod::Readme - Convert POD to README file SYNOPSIS
use Pod::Readme; my $parser = Pod::Readme->new(); # Read POD from STDIN and write to STDOUT $parser->parse_from_filehandle; # Read POD from Module.pm and write to README $parser->parse_from_file('Module.pm', 'README'); DESCRIPTION
This module is a subclass of Pod::PlainText which provides additional POD markup for generating README files. Why should one bother with this? One can simply use pod2text Module.pm > README A problem with doing that is that the default pod2text converter will add text to links, so that "L<Module>" is translated to "the Module manpage". Another problem is that the README includes the entirety of the module documentation! Most people browsing the README file do not need all of this information. Likewise, including installation and requirement information in the module documentation is not necessary either, since the module is already installed. This module allows authors to mark portions of the POD to be included only in, or to be excluded from the README file. It also allows you to include portions of another file (such as a separate ChangeLog). Markup Special POD markup options are described below: begin/end =begin readme =head1 README ONLY This section will only show up in the README file. =end readme Delineates a POD section that is only available in README file. If you prefer to include plain text instead, add the "text" modifier: =begin readme text README ONLY (PLAINTEXT) This section will only show up in the README file. =end readme Note that placing a colon before the section to indicate that it is POD (e.g. "begin :readme") is not supported in this version. stop/continue =for readme stop All POD that follows will not be included in the README, until a "continue" command occurs: =for readme continue include =for readme include file=filename type=type start=Regexp stop=Regexp =for readme include file=Changes start=^0.09 stop=^0.081 type=text Includes a plaintext file named filename, starting with the line that contains the start "Regexp" and ending at the line that begins with the stop "Regexp". (The start and stop Regexps are optional: one or both may be omitted.) Type may be "text" or "pod". If omitted, "pod" will be assumed. Quotes may be used when the filename or marks contains spaces: =for readme include file="another file.pod" One can also using maintain multiple file types (such as including TODO, or COPYING) by using a modified constructor: $parser = Pod::Readme->new( readme_type => "copying" ); In the above "Markup" commands replace "readme" with the tag specified instead (such as "copying"): =begin copying As of version 0.03 you can specify multiple sections by separating them with a comma: =begin copying,readme There is also no standard list of type names. Some names might be recognized by other POD processors (such as "testing" or "html"). Pod::Readme will reject the following "known" type names when they are specified in the constructor: testing html xhtml xml docbook rtf man nroff dsr rno latex tex code You can also use a "debug" mode to diagnose any problems, such as mistyped format names: $parser = Pod::Readme->new( debug => 1 ); Warnings will be issued for any ignored formatting commands. Example For an example, see the Readme.pm file in this distribution. SEE ALSO
See perlpod, perlpodspec and podlators. AUTHOR
Originally by Robert Rothenberg <rrwo at cpan.org> Now maintained by David Precious <davidp@preshweb.co.uk> Suggestions, Bug Reporting and Contributing This module is developed on GitHub at: http://github.com/bigpresh/Pod-Readme LICENSE
Copyright (c) 2005,2006 Robert Rothenberg. All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. Some portions are based on Pod::PlainText 2.02. perl v5.10.1 2010-12-09 Pod::Readme(3pm)
All times are GMT -4. The time now is 11:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy