Mdthbs

When to remove insignificant variables?

UK - Working without a contract. I resign and guy wants to sue me

How does DC work with natural 20?

How to remove this component from PCB

Is there any difference between Т34ВМ1 and КМ1858ВМ1/3?

How do I professionally let my manager know I'll quit over an issue?

Is declining an undergraduate award which causes me discomfort appropriate?

Can there be an UN resolution to remove a country from the UNSC?

How do I farm creepers for XP without them exploding?

Is a single radon-daughter atom in air a solid?

How large would a mega structure have to be to host 1 billion people indefinitely?

What is appropriate short form for "laboratoires" in French?

Constitutionality of U.S. Democratic Presidential Candidate's Supreme Court Suggestion

Am I legally required to provide a (GPL licensed) source code even after a project is abandoned?

Heavily limited premature compiler translates text into excecutable python code

Methodology: Writing unit tests for another developer

Term or phrase for simply moving a problem from one area to another

How can I get my left hand to sound legato when I'm leaping?

How to maintain a closed environment for one person for a long period of time

Why didn't the Cardassians take Terok Nor (Deep Space 9) with them when withdrawing from Bajor?

How does a blind passenger not die, if driver becomes unconscious

What is the highest voltage from the power supply a Raspberry Pi 3 B can handle without getting damaged?

How do I handle a table mixing up the DM and the players' roles too often?

Why are < or > required to use /dev/tcp

How to write exactly bash scripts into Makefiles?

None of the dot-files is sourced when running bash via ssh, part IIWhen is it important to write portable scripts?Using “reserved” codes for exit status of shell scriptsHow to upload a file and then check it and run some other commands using only ssh, cat, and diff in a single SSH session?find -exec not working in bash script but working in terminalBash interactive - entire script writing to historyHow to find why a bash exits with signal 11, Segmentation faultStrategy for forgetting to run a script with `source`?Evaluate command based on variable at bashBash Script general questions

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}

5

3

I love to type bash scripts, but if I prepare multiple tools, project's root directory is filled with so many shell scripts. That's why I prefer using Makefile.

Makefile is good. However I want to build my makefiles just as regular bash scripts.

Eg:

Think that I wrote a bash script very quickly with the following content:

#!/bin/bash

echo "hello"

cd ~

do-some-work.sh my-parameter

I can run this script with $ ./my-important-task.sh.

If I wanted to move that script into makefile, I should do the following:

SHELL := /bin/bash 



my-important-task: 

    echo "hello" ;

    cd ~ ;

    do-some-work.sh my-parameter

but I want the following:

my-important-task: 

    [[copy and paste the my-important-task.sh file]]

Is there anyway to accomplish this goal?

bash make

share|improve this question

edited 27 mins ago

ceremcem

asked Mar 18 '16 at 20:59

ceremcemceremcem

5841624

add a comment | 

5

3

I love to type bash scripts, but if I prepare multiple tools, project's root directory is filled with so many shell scripts. That's why I prefer using Makefile.

Makefile is good. However I want to build my makefiles just as regular bash scripts.

Eg:

Think that I wrote a bash script very quickly with the following content:

#!/bin/bash

echo "hello"

cd ~

do-some-work.sh my-parameter

I can run this script with $ ./my-important-task.sh.

If I wanted to move that script into makefile, I should do the following:

SHELL := /bin/bash 



my-important-task: 

    echo "hello" ;

    cd ~ ;

    do-some-work.sh my-parameter

but I want the following:

my-important-task: 

    [[copy and paste the my-important-task.sh file]]

Is there anyway to accomplish this goal?

bash make

share|improve this question

edited 27 mins ago

ceremcem

asked Mar 18 '16 at 20:59

ceremcemceremcem

5841624

add a comment | 

I love to type bash scripts, but if I prepare multiple tools, project's root directory is filled with so many shell scripts. That's why I prefer using Makefile.

Makefile is good. However I want to build my makefiles just as regular bash scripts.

Eg:

Think that I wrote a bash script very quickly with the following content:

#!/bin/bash

echo "hello"

cd ~

do-some-work.sh my-parameter

I can run this script with $ ./my-important-task.sh.

If I wanted to move that script into makefile, I should do the following:

SHELL := /bin/bash 



my-important-task: 

    echo "hello" ;

    cd ~ ;

    do-some-work.sh my-parameter

but I want the following:

my-important-task: 

    [[copy and paste the my-important-task.sh file]]

Is there anyway to accomplish this goal?

bash make

share|improve this question

edited 27 mins ago

ceremcem

asked Mar 18 '16 at 20:59

ceremcemceremcem

5841624

#!/bin/bash

echo "hello"

cd ~

do-some-work.sh my-parameter

SHELL := /bin/bash 



my-important-task: 

    echo "hello" ;

    cd ~ ;

    do-some-work.sh my-parameter

my-important-task: 

    [[copy and paste the my-important-task.sh file]]

share|improve this question

edited 27 mins ago

ceremcem

asked Mar 18 '16 at 20:59

ceremcemceremcem

5841624

share|improve this question

edited 27 mins ago

ceremcem

asked Mar 18 '16 at 20:59

ceremcemceremcem

5841624

asked Mar 18 '16 at 20:59

ceremcemceremcem

5841624

asked Mar 18 '16 at 20:59

ceremcemceremcem

5841624

4 Answers
4

active

oldest

votes

12

If you really want to “write exactly bash scripts into Makefiles” then you'll need to do it a bit indirectly. If you just paste the script after the target line, then you'll run into two problems that just cannot be bypassed: the command lines need to be indented with a tab, and dollar signs need to be escaped.

If you use GNU make (as opposed to BSD make, Solaris make, etc.), then you can define your script as a variable using the multi-line definition syntax, and then use the value function to use the raw value of the variable, bypassing expansion.

In addition, as explained by skwllsp, you need to tell make to execute the command list for each target as a single shell script rather than line by line, which you can do in GNU make by defining a .ONESHELL target.

define my_important_task =

# script goes here

endef



my-important-task: ; $(value my_important_task)



.ONESHELL:

share|improve this answer

edited Apr 13 '17 at 12:36

Community♦

1

answered Mar 18 '16 at 22:29

GillesGilles

559k13411521657

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Would you mind taking a look at this file: gist.github.com/ceremcem/a380bb92cbd03c34aba5
  
  – ceremcem
  Mar 19 '16 at 0:37
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @ceremcem You need .ONESHELL as well.
  
  – Gilles
  Mar 19 '16 at 11:34
  

  
  
  
  

add a comment | 

5

https://www.gnu.org/software/make/manual/html_node/One-Shell.html

If the .ONESHELL special target appears anywhere in the makefile then
all recipe lines for each target will be provided to a single
invocation of the shell.

You will still need to put a tab character at the beginning of each line, and to double all dollar signs (i.e. replace $ by $$ everywhere in the script).

share|improve this answer

edited Mar 18 '16 at 22:22

Gilles

559k13411521657

answered Mar 18 '16 at 21:09

Sergei KurenkovSergei Kurenkov

2,1541218

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  it's almost what I'm looking for. would you mind helping me debug the following test code which doesn't work as is: gist.github.com/ceremcem/9b6e8e90928ff4afc569
  
  – ceremcem
  Mar 18 '16 at 21:53
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @ceremcem You need to escape the dollar signs.
  
  – Gilles
  Mar 18 '16 at 22:23
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  It still produces an error: make: /bin/bash : Command not found Makefile:5: recipe for target 'test' failed make: *** [test] Error 127
  
  – ceremcem
  Mar 19 '16 at 1:03
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @ceremcem, what make version do you use? See this: stackoverflow.com/questions/32153034/…
  
  – Sergei Kurenkov
  Mar 19 '16 at 10:15
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Gilles I use GNU Make 4.1
  
  – ceremcem
  Mar 19 '16 at 10:34
  
  
  

  
  
  
  

add a comment | 

5

If the problem is that your top-level project directory is cluttered with dozens of scripts, then the obvious solution is to create a subdirectory (e.g. called scripts) to put them in.

Run them as ./scripts/scriptname and/or add the scripts directory to your PATH.

If you still want a Makefile to run them with, just create Makefile entries that run ./scripts/scriptname for those targets. e.g.

my-important-task: 

    ./scripts/my-important-task.sh my-parameter

NOTE: If the scripts in ./scripts call other scripts in the same directory, they'll need to either specify the full path to the script, or have the scripts directory in the PATH.

share|improve this answer

answered Mar 19 '16 at 1:35

cascas

40.2k457107

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Maybe that would be an appropriate solution. But writing down in a single file would make things speed up in most cases. We were talking about a proposal yesterday though...
  
  – ceremcem
  Mar 19 '16 at 10:49
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  somehow i doubt very much that having make parse a Makefile, search for a target, and then fork a shell to run some shell commands could possibly be faster than just running a shell script. not that the startup speed of make plus a bunch of shell commands or a shell script is at all significant on any modern-ish machine (say, less than 20 years old) unless run thousands of times in a loop.
  
  – cas
  Mar 19 '16 at 11:33
  

  
  
  
  

add a comment | 

0

Why don't you use aliases and functions defined in your .bashrc (and possibly .bash_alaiases`)?

share

answered 4 mins ago

xenoidxenoid

3,5091928

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

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

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f270778%2fhow-to-write-exactly-bash-scripts-into-makefiles%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

12

If you really want to “write exactly bash scripts into Makefiles” then you'll need to do it a bit indirectly. If you just paste the script after the target line, then you'll run into two problems that just cannot be bypassed: the command lines need to be indented with a tab, and dollar signs need to be escaped.

If you use GNU make (as opposed to BSD make, Solaris make, etc.), then you can define your script as a variable using the multi-line definition syntax, and then use the value function to use the raw value of the variable, bypassing expansion.

In addition, as explained by skwllsp, you need to tell make to execute the command list for each target as a single shell script rather than line by line, which you can do in GNU make by defining a .ONESHELL target.

define my_important_task =

# script goes here

endef



my-important-task: ; $(value my_important_task)



.ONESHELL:

share|improve this answer

edited Apr 13 '17 at 12:36

Community♦

1

answered Mar 18 '16 at 22:29

GillesGilles

559k13411521657

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Would you mind taking a look at this file: gist.github.com/ceremcem/a380bb92cbd03c34aba5
  
  – ceremcem
  Mar 19 '16 at 0:37
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @ceremcem You need .ONESHELL as well.
  
  – Gilles
  Mar 19 '16 at 11:34
  

  
  
  
  

add a comment | 

12

If you really want to “write exactly bash scripts into Makefiles” then you'll need to do it a bit indirectly. If you just paste the script after the target line, then you'll run into two problems that just cannot be bypassed: the command lines need to be indented with a tab, and dollar signs need to be escaped.

If you use GNU make (as opposed to BSD make, Solaris make, etc.), then you can define your script as a variable using the multi-line definition syntax, and then use the value function to use the raw value of the variable, bypassing expansion.

In addition, as explained by skwllsp, you need to tell make to execute the command list for each target as a single shell script rather than line by line, which you can do in GNU make by defining a .ONESHELL target.

define my_important_task =

# script goes here

endef



my-important-task: ; $(value my_important_task)



.ONESHELL:

share|improve this answer

edited Apr 13 '17 at 12:36

Community♦

1

answered Mar 18 '16 at 22:29

GillesGilles

559k13411521657

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Would you mind taking a look at this file: gist.github.com/ceremcem/a380bb92cbd03c34aba5
  
  – ceremcem
  Mar 19 '16 at 0:37
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @ceremcem You need .ONESHELL as well.
  
  – Gilles
  Mar 19 '16 at 11:34
  

  
  
  
  

add a comment | 

If you really want to “write exactly bash scripts into Makefiles” then you'll need to do it a bit indirectly. If you just paste the script after the target line, then you'll run into two problems that just cannot be bypassed: the command lines need to be indented with a tab, and dollar signs need to be escaped.

If you use GNU make (as opposed to BSD make, Solaris make, etc.), then you can define your script as a variable using the multi-line definition syntax, and then use the value function to use the raw value of the variable, bypassing expansion.

In addition, as explained by skwllsp, you need to tell make to execute the command list for each target as a single shell script rather than line by line, which you can do in GNU make by defining a .ONESHELL target.

define my_important_task =

# script goes here

endef



my-important-task: ; $(value my_important_task)



.ONESHELL:

share|improve this answer

edited Apr 13 '17 at 12:36

Community♦

1

answered Mar 18 '16 at 22:29

GillesGilles

559k13411521657

define my_important_task =

# script goes here

endef



my-important-task: ; $(value my_important_task)



.ONESHELL:

share|improve this answer

edited Apr 13 '17 at 12:36

Community♦

1

answered Mar 18 '16 at 22:29

GillesGilles

559k13411521657

edited Apr 13 '17 at 12:36

Community♦

1

edited Apr 13 '17 at 12:36

Community♦

1

answered Mar 18 '16 at 22:29

GillesGilles

559k13411521657

answered Mar 18 '16 at 22:29

GillesGilles

559k13411521657

5

https://www.gnu.org/software/make/manual/html_node/One-Shell.html

If the .ONESHELL special target appears anywhere in the makefile then
all recipe lines for each target will be provided to a single
invocation of the shell.

You will still need to put a tab character at the beginning of each line, and to double all dollar signs (i.e. replace $ by $$ everywhere in the script).

share|improve this answer

edited Mar 18 '16 at 22:22

Gilles

559k13411521657

answered Mar 18 '16 at 21:09

Sergei KurenkovSergei Kurenkov

2,1541218

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  it's almost what I'm looking for. would you mind helping me debug the following test code which doesn't work as is: gist.github.com/ceremcem/9b6e8e90928ff4afc569
  
  – ceremcem
  Mar 18 '16 at 21:53
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @ceremcem You need to escape the dollar signs.
  
  – Gilles
  Mar 18 '16 at 22:23
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  It still produces an error: make: /bin/bash : Command not found Makefile:5: recipe for target 'test' failed make: *** [test] Error 127
  
  – ceremcem
  Mar 19 '16 at 1:03
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @ceremcem, what make version do you use? See this: stackoverflow.com/questions/32153034/…
  
  – Sergei Kurenkov
  Mar 19 '16 at 10:15
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Gilles I use GNU Make 4.1
  
  – ceremcem
  Mar 19 '16 at 10:34
  
  
  

  
  
  
  

add a comment | 

5

https://www.gnu.org/software/make/manual/html_node/One-Shell.html

If the .ONESHELL special target appears anywhere in the makefile then
all recipe lines for each target will be provided to a single
invocation of the shell.

You will still need to put a tab character at the beginning of each line, and to double all dollar signs (i.e. replace $ by $$ everywhere in the script).

share|improve this answer

edited Mar 18 '16 at 22:22

Gilles

559k13411521657

answered Mar 18 '16 at 21:09

Sergei KurenkovSergei Kurenkov

2,1541218

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  it's almost what I'm looking for. would you mind helping me debug the following test code which doesn't work as is: gist.github.com/ceremcem/9b6e8e90928ff4afc569
  
  – ceremcem
  Mar 18 '16 at 21:53
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @ceremcem You need to escape the dollar signs.
  
  – Gilles
  Mar 18 '16 at 22:23
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  It still produces an error: make: /bin/bash : Command not found Makefile:5: recipe for target 'test' failed make: *** [test] Error 127
  
  – ceremcem
  Mar 19 '16 at 1:03
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @ceremcem, what make version do you use? See this: stackoverflow.com/questions/32153034/…
  
  – Sergei Kurenkov
  Mar 19 '16 at 10:15
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Gilles I use GNU Make 4.1
  
  – ceremcem
  Mar 19 '16 at 10:34
  
  
  

  
  
  
  

add a comment | 

https://www.gnu.org/software/make/manual/html_node/One-Shell.html

If the .ONESHELL special target appears anywhere in the makefile then
all recipe lines for each target will be provided to a single
invocation of the shell.

You will still need to put a tab character at the beginning of each line, and to double all dollar signs (i.e. replace $ by $$ everywhere in the script).

share|improve this answer

edited Mar 18 '16 at 22:22

Gilles

559k13411521657

answered Mar 18 '16 at 21:09

Sergei KurenkovSergei Kurenkov

2,1541218

share|improve this answer

edited Mar 18 '16 at 22:22

Gilles

559k13411521657

answered Mar 18 '16 at 21:09

Sergei KurenkovSergei Kurenkov

2,1541218

edited Mar 18 '16 at 22:22

Gilles

559k13411521657

edited Mar 18 '16 at 22:22

Gilles

559k13411521657

answered Mar 18 '16 at 21:09

Sergei KurenkovSergei Kurenkov

2,1541218

answered Mar 18 '16 at 21:09

Sergei KurenkovSergei Kurenkov

2,1541218

5

If the problem is that your top-level project directory is cluttered with dozens of scripts, then the obvious solution is to create a subdirectory (e.g. called scripts) to put them in.

Run them as ./scripts/scriptname and/or add the scripts directory to your PATH.

If you still want a Makefile to run them with, just create Makefile entries that run ./scripts/scriptname for those targets. e.g.

my-important-task: 

    ./scripts/my-important-task.sh my-parameter

NOTE: If the scripts in ./scripts call other scripts in the same directory, they'll need to either specify the full path to the script, or have the scripts directory in the PATH.

share|improve this answer

answered Mar 19 '16 at 1:35

cascas

40.2k457107

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Maybe that would be an appropriate solution. But writing down in a single file would make things speed up in most cases. We were talking about a proposal yesterday though...
  
  – ceremcem
  Mar 19 '16 at 10:49
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  somehow i doubt very much that having make parse a Makefile, search for a target, and then fork a shell to run some shell commands could possibly be faster than just running a shell script. not that the startup speed of make plus a bunch of shell commands or a shell script is at all significant on any modern-ish machine (say, less than 20 years old) unless run thousands of times in a loop.
  
  – cas
  Mar 19 '16 at 11:33
  

  
  
  
  

add a comment | 

5

If the problem is that your top-level project directory is cluttered with dozens of scripts, then the obvious solution is to create a subdirectory (e.g. called scripts) to put them in.

Run them as ./scripts/scriptname and/or add the scripts directory to your PATH.

If you still want a Makefile to run them with, just create Makefile entries that run ./scripts/scriptname for those targets. e.g.

my-important-task: 

    ./scripts/my-important-task.sh my-parameter

NOTE: If the scripts in ./scripts call other scripts in the same directory, they'll need to either specify the full path to the script, or have the scripts directory in the PATH.

share|improve this answer

answered Mar 19 '16 at 1:35

cascas

40.2k457107

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Maybe that would be an appropriate solution. But writing down in a single file would make things speed up in most cases. We were talking about a proposal yesterday though...
  
  – ceremcem
  Mar 19 '16 at 10:49
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  somehow i doubt very much that having make parse a Makefile, search for a target, and then fork a shell to run some shell commands could possibly be faster than just running a shell script. not that the startup speed of make plus a bunch of shell commands or a shell script is at all significant on any modern-ish machine (say, less than 20 years old) unless run thousands of times in a loop.
  
  – cas
  Mar 19 '16 at 11:33
  

  
  
  
  

add a comment | 

If the problem is that your top-level project directory is cluttered with dozens of scripts, then the obvious solution is to create a subdirectory (e.g. called scripts) to put them in.

Run them as ./scripts/scriptname and/or add the scripts directory to your PATH.

If you still want a Makefile to run them with, just create Makefile entries that run ./scripts/scriptname for those targets. e.g.

my-important-task: 

    ./scripts/my-important-task.sh my-parameter

NOTE: If the scripts in ./scripts call other scripts in the same directory, they'll need to either specify the full path to the script, or have the scripts directory in the PATH.

share|improve this answer

answered Mar 19 '16 at 1:35

cascas

40.2k457107

my-important-task: 

    ./scripts/my-important-task.sh my-parameter

share|improve this answer

answered Mar 19 '16 at 1:35

cascas

40.2k457107

answered Mar 19 '16 at 1:35

cascas

40.2k457107

answered Mar 19 '16 at 1:35

cascas

40.2k457107

0

Why don't you use aliases and functions defined in your .bashrc (and possibly .bash_alaiases`)?

share

answered 4 mins ago

xenoidxenoid

3,5091928

add a comment | 

0

Why don't you use aliases and functions defined in your .bashrc (and possibly .bash_alaiases`)?

share

answered 4 mins ago

xenoidxenoid

3,5091928

add a comment | 

Why don't you use aliases and functions defined in your .bashrc (and possibly .bash_alaiases`)?

share

answered 4 mins ago

xenoidxenoid

3,5091928

share

answered 4 mins ago

xenoidxenoid

3,5091928

answered 4 mins ago

xenoidxenoid

3,5091928

answered 4 mins ago

xenoidxenoid

3,5091928