Jump to content

Build_Clover.command, another Script to build standard Clover (or customized)

Micky1979

By Micky1979,
in Clover

 Share
2,126 posts in this topic

Recommended Posts

Sherlocks
Sherlocks
Posted
Posted

OsxFatBinary.efi is optional now. It is needed only for systems previous to 10.8.

If you want to install it check the driver in Clover package.

Thanks Slice.

I want to know what is difference of osxfatbinary-64 and fat-64. There is no instruction with role of each binary.

 

나의 LG-F800S 의 Tapatalk에서 보냄

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

Thanks Slice.

I want to know what is difference of osxfatbinary-64 and fat-64. There is no instruction with role of each binary.

 

나의 LG-F800S 의 Tapatalk에서 보냄

Fat-64?

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

Fat-64?

Yes. I'm confused each files. You can see this file in clover package.

 

I have two files(osxfatbinary-64 and fat-64) until install r4390.

 

After install r4390, left only fat-64(i never check any extra binary(osxfatbinary-64 and fat-64) after install fresh osx)

 

나의 LG-F800S 의 Tapatalk에서 보냄

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

Thanks Slice.

I want to know what is difference of osxfatbinary-64 and fat-64. There is no instruction with role of each binary.

 

나의 LG-F800S 의 Tapatalk에서 보냄

Fat-64 is a File System FAT32 driver (MSDOS). It can be installed to replace UEFI BIOS Fat driver because those one is quirky. "Thanks" to AMI for his driver!

  • Like 1
Link to comment
Share on other sites
MakAsus
MakAsus
Posted
Posted

Or you could just use the script I made that does everything automated for you.

I do not know what's the matter, but I could to compile AptioMemoryFix and AptioInputFix, only after Install the nasm v2.13.02 into CommandLineTools/usr/bin/

sudo cp ~/Downloads/nasm /Library/Developer/CommandLineTools/usr/bin/
Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted

nasm should be installed in /usr/local/bin/ not /Library/Developer/CommandLineTools/usr/bin/

Sorry but your script cannot work in some systems.. How do you suppose to ensure  nasm is running from "/usr/local/bin/" if you did not even exported that path in $PATH??

The same for mtoc..  users can have something else at the begin of $PATH and or /usr/local/bin missing:

Last login: Sun Jan 21 15:54:44 on console
vectorsigmas-MBP:~ vectorsigma $ echo $PATH
/opt/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/Visual Studio Code copy.app/Contents/Resources/app/bin
vectorsigmas-MBP:~ vectorsigma$

you didn't ensure that. (I have a different nasm version in /opt/local/bin/ and that will be use, but is not what you expected). Fix this and nasm can be where you like.

 

 

tested Build_Clover.command and worked, now I have working NVRAM finally, without emulation  :hyper:, thanks to AptioMemoryFix creators really good job on karls.. impressive!

Link to comment
Share on other sites
Pavo
Pavo
Posted
Posted

Sorry but your script cannot work in some systems.. How do you suppose to ensure  nasm is running from "/usr/local/bin/" if you did not even exported that path in $PATH??

The same for mtoc..  users can have something else at the begin of $PATH and or /usr/local/bin missing:

Last login: Sun Jan 21 15:54:44 on console
vectorsigmas-MBP:~ vectorsigma $ echo $PATH
/opt/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/Visual Studio Code copy.app/Contents/Resources/app/bin
vectorsigmas-MBP:~ vectorsigma$

you didn't ensure that. (I have a different nasm version in /opt/local/bin/ and that will be use, but is not what you expected). Fix this and nasm can be where you like.

 

 

tested Build_Clover.command and worked, now I have working NVRAM finally, without emulation  :hyper:, thanks to AptioMemoryFix creators really good job on karls.. impressive!

Thanks for pointing that out, have fixed the AptioMemoryFix build script.

https://github.com/Pavo-IM/AptioMemFix

Link to comment
Share on other sites
Pavo
Pavo
Posted
Posted

When the script tries to pull AptioFix I get these warnings for each package:

 

Error validating server certificate for 'https://github.com:443':The certificate is not issued by a trusted authority.

 

Yet I don't get these when using the AptioMemoryFix build script. Any idea why?

Don't see how that could happen since in the script its cloning directly from vit9696's repo. Mind posting a screenshot of your terminal output.

git clone -q https://github.com/vit9696/AptioFix.git
Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted

svn over ssh instead of git, I suspect you have some bad ssh settings/permissions. I think you can trust github.com with eyes closed.. also you already know what you are downloading and from.


https://help.github.com/articles/using-ssh-over-the-https-port/

 

type in terminal: 

ssh -T -p 443 git@ssh.github.com

then accept and so type yes.  


Most of the times is symptom that you used sudo to do something with ssh previously (like call git with sudo somehow), strictly discouraged otherwise generated keys will not be valid since the root user and you are not the same man. If that is the case you should repair permissions on ~/.subversion/auth

  • Like 1
Link to comment
Share on other sites
MakAsus
MakAsus
Posted
Posted

Sorry but your script cannot work in some systems.. How do you suppose to ensure  nasm is running from "/usr/local/bin/" if you did not even exported that path in $PATH??

The same for mtoc..  users can have something else at the begin of $PATH and or /usr/local/bin missing:

Last login: Sun Jan 21 15:54:44 on console
vectorsigmas-MBP:~ vectorsigma $ echo $PATH
/opt/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/Visual Studio Code copy.app/Contents/Resources/app/bin
vectorsigmas-MBP:~ vectorsigma$

you didn't ensure that. (I have a different nasm version in /opt/local/bin/ and that will be use, but is not what you expected). Fix this and nasm can be where you like.

 

 

tested Build_Clover.command and worked, now I have working NVRAM finally, without emulation  :hyper:, thanks to AptioMemoryFix creators really good job on karls.. impressive!

Sorry, but my export path contains this:

echo $PATH
/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin

But the script did not work properly until I replaced nasm in the folder /Library/Developer/CommandLineTools/usr/bin/. In the MacOS Sierra, all works without manual intervention. I do not understand what is the difference.

Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted

Sorry, but my export path contains this:

echo $PATH
/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin

But the script did not work properly until I replaced nasm in the folder /Library/Developer/CommandLineTools/usr/bin/. In the MacOS Sierra, all works without manual intervention. I do not understand what is the difference.

Hi Sir, first of all your $PATH is wrong, and I'm sure of that, because '/usr/local/bin' is at the end instead of the beginning of the string so it will continue using the nasm shipped with macOS at '/usr/bin'.

Secondly I have no idea why is not working for you, so I think that you should ask the guys who made Build_Clover.command, always that you are referring to this script and not to anything else, as for the title of the Topic I hope. Otherwise you are off topic I guess.

Link to comment
Share on other sites
  • 2 weeks later...
Matgen84
Matgen84
Posted
Posted

Hi 

 

I've issue with Build_clover.command 4.6.8.

 

Each time with mtoc.New in user/local/bin

gettext check:
                             <--------------------------------------------------
found gettext at /Users/mathieu-gentile/src/opt/local/bin
mtoc.NEW symlink not found, installing...Password:
 

And after

boot6
                             <--------------------------------------------------
TOOLCHAIN_DIR: /Users/mathieu-gentile/src/opt/local
Installing mtoc.NEW
Password:
ln: /usr/local/bin/mtoc.NEW: File exists

o_Ops, ./ebuild.sh exited with error(s), aborting..
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted

Matin84.

Remove the mtoc.NEW  from /usr/local/bin/ and run the script again.

Thanks. I do that and all work.

 

But I don't understand: previous mtoc.NEW is version 2016 (159k) in usr/local/bin. Now for compiling, the script use src/EDK2/Clover/BuildTools/usr/local/bin/mtoc.new version 2014 (167k)

Link to comment
Share on other sites
Philip Petev
Philip Petev
Posted
Posted

The script installs in /usr/local/bin symlinks to the one, bundled with Clover. If you have another version in /usr/local/bin (actual binary and not symlink), that's another story. But I see a problem here: the current mtoc code looks for symlink. What if there is a binary in that folder....

 

EDIT: I've just uploaded a new version. The script will now allow other mtoc versions in /usr/local/bin (at your responsibility of course).

Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted

The script installs in /usr/local/bin symlinks to the one, bundled with Clover. If you have another version in /usr/local/bin (actual binary and not symlink), that's another story. But I see a problem here: the current mtoc code looks for symlink. What if there is a binary in that folder....

 

EDIT: I've just uploaded a new version. The script will now allow other mtoc versions in /usr/local/bin (at your responsibility of course).

Thanks. The script work well so I don't need /usr/local/bin for another version.

 

About my question, I only want to understand what avoids making mistakes  :)

Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted

You should probably have used the build script, bundled with AptioFixPkg. It installs mtoc (also bundled with AptioFixPkg) in /usr/local/bin and that interfere with the symlinks, made there by ebuild.sh/Build_Clover.command.

Thanks a lot. Have a nice day 

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

i report one

7) enter Developers mode (only for devs)

and tested all options

but always made pkg build. i can't build only binary files(3/4 option)

 

i also tested that removed src folder and updated edk2 all. but still happen same issue. i don't know since some script version developers mode broken.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...