Skip to content

Navigation Menu

Explore
By size
By industry
By use case
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

leto / plparrot Public

Notifications You must be signed in to change notification settings
Fork 5
Star 27

Code
Issues 24
Pull requests
Actions
Projects
Wiki
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Wiki
Security
Insights

Breadcrumbs

plparrot

/

HACKING.parrot

Latest commit

History

7 lines (5 loc) · 327 Bytes

Breadcrumbs

plparrot

/

HACKING.parrot

File metadata and controls

7 lines (5 loc) · 327 Bytes

1

2

3

4

5

6

7

Here's a way to have fresh parrots.

Figure out what to put in instead of -j4 by figuring out how many

cores are available. On Linux, you can cat /proc/cpuinfo.

export PATH=$HOME/installed_parrot/bin:$PATH

alias new_parrot="make realclean; perl Configure.pl --optimize --prefix=$HOME/installed_parrot && nice -n20 gmake -j4"

Footer

© 2024 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.