Jump to content
30960 posts in this topic

Recommended Posts

50 minutes ago, arsradu said:

Nope. ftp or ftps makes no difference. It doesn't work with either one of them.

What's your ISP that block port 21 and port 22?

 

50 minutes ago, arsradu said:

Also, if you remember, we did have the exact same issue before with buildgettext.sh. And it was fixed exactly the same way by Zenith.

Was no longer in my head, but you too had the same concern about ftp and why not https, maybe for a simply reason... like an authenticated account: 

1902201546_Screenshot2019-10-07at22_00_34.png.396bc218ab8d52e718ccdab85583373d.png

or just because adviced by GNU for some reasons... and anyway before doing that I have to understand why the gnu links are not resolved for me with https...  why I asked you to try to open port 21 in your router's firewall... why I'm reluctant (i.e. to make you happy I've to make me crying).

22 hours ago, vector sigma said:

What's your ISP that block port 21 and port 22?

 

Was no longer in my head, but you too had the same concern about ftp and why not https, maybe for a simply reason... like an authenticated account: 

1902201546_Screenshot2019-10-07at22_00_34.png.396bc218ab8d52e718ccdab85583373d.png

or just because adviced by GNU for some reasons... and anyway before doing that I have to understand why the gnu links are not resolved for me with https...  why I asked you to try to open port 21 in your router's firewall... why I'm reluctant (i.e. to make you happy I've to make me crying).

 

It's not my router. It's at work. :) I've got no control over ports and such. Works fine at home. But at home, I've got no restriction on the ports.  I don't know about authentication pop-up. I'm guessing switching to https will make that pop-up not show up anymore...? I don't know...

 

Thing is, it was fixed exactly like that before. :)) And it's exactly the same issue. So...if it wasn't an issue before to simply switch to https, why would it be an issue now? :))

 

Anyway, I don't want to make you cry. So, if this is causing issues for other people, I'll just make a backup of those 3 edited files, and replace them whenever I want to compile Clover. Simple as that. :)

 

Thank you very much for your feedback. :) Aaaand..happy downloading, if you're planning on upgrading to final version of Catalina (build 19A583) tonight.

Edited by arsradu
6 minutes ago, arsradu said:

Thing is, it was fixed exactly like that before. :)) And it's exactly the same issue. So...if it wasn't an issue before to simply switch to https, why would it be an issue now? :))

Because of me? I'm a dog?:blush:

quip

6 minutes ago, arsradu said:

Anyway, I don't want to make you cry. So, if this is causing issues for other people, I'll just make a backup of those 3 edited files, and replace them whenever I want to compile Clover. Simple as that

I've to understand why and how to fix it...  

Edited by vector sigma
Just now, vector sigma said:

Because of me? I'm a dog?:blush:

 

Your profile picture says you're a cat! I'm confused. :P 

 

Vector, look, it's ok man. I don't wanna cause anyone any troubles. And if changing this causes you other issues (although, again, the same exact thing has been done for compiling with buildgettext), and you seem to be ok with that...then let's just leave it.

1 minute ago, arsradu said:

Your profile picture says you're a cat! I'm confused. :P 

a bad cat:cat: Lol.

 

3 minutes ago, arsradu said:

(although, again, the same exact thing has been done for compiling with buildgettext

It's a light year I didn't compile it as I have the same problem. Installed it using homebrew. Wait! ...something tells me that switching back to ftp...

11 minutes ago, vector sigma said:

I've to understand why and how to fix it...  

 

If you're looking for an alternative fix for this...well, I don't know. And unfortunately I can't help you with that. :))

 

The issue is the restricted ports. And a valid workaround is simply using https in front of the URLs instead of ftp.

 

There might be other ways to fix this... But as I said, unfortunately that's the easiest fix I could find. :)) For a more "professional" fix...I'm not the guy to ask. :))

2 hours ago, arsradu said:

Hi guys!

 

I saw a few "don't use vers.txt" commits. So...is this intended? Or are there going to be other commits to address this? I'm only curious. Cause right now it looks pretty strange. :))

 

1535870908_Screenshot2019-10-09at09_58_51.thumb.png.ad4e4cc87be6b9ce3e570dde440f0dab.png545604676_Screenshot2019-10-09at10_01_21.thumb.png.c4aec995106dcfb0381f37d2d11a97ec.png

 

 

 

I don't use Clover Updater, so I don't know if there is a mistake. No issues for Clover PKG r5095 + 3 commits

 

 

Capture d’écran 2019-10-09 à 11.48.59.png

4 minutes ago, Matgen84 said:

 

I don't use Clover Updater, so I don't know if there is a mistake. No issues for Clover PKG r5095 + 3 commits

 

 

Well, that's the thing... I didn't use the updater... I just built Clover from scratch. Hmmm.. something is odd.

 

Did you make a clean build (erasing and recreating the the work directory)?

Edited by arsradu
  • Like 1
21 minutes ago, arsradu said:

 

Well, that's the thing... I didn't use the updater... I just built Clover from scratch. Hmmm.. something is odd.

 

I just built Clover too but from update. Very strange: if I build again: I've the message "not a git repository build failed" despite of CloverPKG in /sym folder :wink_anim:

 

 

Capture d’écran 2019-10-09 à 12.19.27.png

Edited by Matgen84
  • Confused 1
18 minutes ago, Matgen84 said:

 

I just built Clover too but from update. Very strange: if I build again: I've the message "not a git repository build failed" despite of CloverPKG in /sym folder :wink_anim:

 

Yeah...I just built again (on another machine) and it was ok. Weird, indeed.

  • Like 1
51 minutes ago, arsradu said:

 

Yeah...I just built again (on another machine) and it was ok. Weird, indeed.

 

No git errors message when I use previous makepkg version

Of course no revision name :wink_anim:

 

 

Capture d’écran 2019-10-09 à 12.59.14.png

 

EDIT: Clean CloverBootLoader folder

 

Always Git errors messages, without Build failed this time

 

 

 

 

Edited by Matgen84
  • Like 1
3 minutes ago, Matgen84 said:

 

In GitHub Repo: release r5095 for example

 

Yes I know, I just wonder no longer be updated in SourceForge? I am already using the latest version from @Slice GitHub repo. But I think this repo doesn't compatible clover updater on the System Preferences.  

  • Like 1
9 minutes ago, telepati said:

 

Yes I know, I just wonder no longer be updated in SourceForge? I am already using the latest version from @Slice GitHub repo. But I think this repo doesn't compatible clover updater on the System Preferences.  

New Clover updater tuned for github.

  • Like 1
  • Thanks 1

Yeah, so I found the reason for the missing versions.

 

--depth 1

in 

git clone https://github.com/CloverHackyColor/CloverBootloader --depth 1

 

What does that parameter do again...? I don't remember having this issue before. :)

 

Anyway, removing that, Clover downloads and compiles correctly, with all the version information properly displayed.

 

Thought I'd mention it in case other people encounter the same issue.

1 hour ago, arsradu said:

Yeah, so I found the reason for the missing versions.

 


--depth 1

in 


git clone https://github.com/CloverHackyColor/CloverBootloader --depth 1

 

What does that parameter do again...? I don't remember having this issue before. :)

 

Anyway, removing that, Clover downloads and compiles correctly, with all the version information properly displayed.

 

Thought I'd mention it in case other people encounter the same issue.

--depth 1 command option save you some space when cloning but doesn't pull enough info from the github, and that info may contain latest release tag for example.

  • Like 2

still happen error. i tried to build clovergit. and using gcc

here is log

[GENFW] BiosVideo

test -f /Users/sherlocks/src/CloverBootloader/Build/Clover/RELEASE_GCC53/X64/CloverEFI/BiosVideo/BiosVideo/OUTPUT/BiosVideo.map && cp -f /Users/sherlocks/src/CloverBootloader/Build/Clover/RELEASE_GCC53/X64/CloverEFI/BiosVideo/BiosVideo/OUTPUT/BiosVideo.map /Users/sherlocks/src/CloverBootloader/Build/Clover/RELEASE_GCC53/FV/Ffs/29CF55F8-B675-4f5d-8F2F-B87A3ECFD063BiosVideo/29CF55F8-B675-4f5d-8F2F-B87A3ECFD063.map

test -e /Users/sherlocks/src/CloverBootloader/Build/Clover/RELEASE_GCC53/X64/CloverEFI/BiosVideo/BiosVideo/OUTPUT/BiosVideo.efi && GenSec -s EFI_SECTION_PE32 -o /Users/sherlocks/src/CloverBootloader/Build/Clover/RELEASE_GCC53/FV/Ffs/29CF55F8-B675-4f5d-8F2F-B87A3ECFD063BiosVideo/29CF55F8-B675-4f5d-8F2F-B87A3ECFD063SEC2.1.pe32 /Users/sherlocks/src/CloverBootloader/Build/Clover/RELEASE_GCC53/X64/CloverEFI/BiosVideo/BiosVideo/OUTPUT/BiosVideo.efi

GenSec -s EFI_SECTION_USER_INTERFACE -n BiosVideo -o /Users/sherlocks/src/CloverBootloader/Build/Clover/RELEASE_GCC53/FV/Ffs/29CF55F8-B675-4f5d-8F2F-B87A3ECFD063BiosVideo/29CF55F8-B675-4f5d-8F2F-B87A3ECFD063SEC3.ui

GenSec -s EFI_SECTION_VERSION -n 1.0 -o /Users/sherlocks/src/CloverBootloader/Build/Clover/RELEASE_GCC53/FV/Ffs/29CF55F8-B675-4f5d-8F2F-B87A3ECFD063BiosVideo/29CF55F8-B675-4f5d-8F2F-B87A3ECFD063SEC4.ver

GenFfs -t EFI_FV_FILETYPE_DRIVER -g 29CF55F8-B675-4f5d-8F2F-B87A3ECFD063 -o /Users/sherlocks/src/CloverBootloader/Build/Clover/RELEASE_GCC53/FV/Ffs/29CF55F8-B675-4f5d-8F2F-B87A3ECFD063BiosVideo/29CF55F8-B675-4f5d-8F2F-B87A3ECFD063.ffs -oi /Users/sherlocks/src/CloverBootloader/Build/Clover/RELEASE_GCC53/FV/Ffs/29CF55F8-B675-4f5d-8F2F-B87A3ECFD063BiosVideo/29CF55F8-B675-4f5d-8F2F-B87A3ECFD063SEC2.1.pe32 -oi /Users/sherlocks/src/CloverBootloader/Build/Clover/RELEASE_GCC53/FV/Ffs/29CF55F8-B675-4f5d-8F2F-B87A3ECFD063BiosVideo/29CF55F8-B675-4f5d-8F2F-B87A3ECFD063SEC3.ui -oi /Users/sherlocks/src/CloverBootloader/Build/Clover/RELEASE_GCC53/FV/Ffs/29CF55F8-B675-4f5d-8F2F-B87A3ECFD063BiosVideo/29CF55F8-B675-4f5d-8F2F-B87A3ECFD063SEC4.ver

[CC] Nvram

[NASM] AsmFuncsX64

[SLINK] OsxAptioFixDrv

[CC] PlatformDriverOverride

[CC] Pointer

[DLINK1] OsxAptioFixDrv

[OBJCOPY] OsxAptioFixDrv

[GENFW] OsxAptioFixDrv

[CC] Settings

sed-but-set-variable: In function 'StartupSoundPlay':

sed-but-set-variable:175:9: internal compiler error: Segmentation fault: 11

libbacktrace could not find executable to open

Please submit a full bug report,

with preprocessed source if appropriate.

See <https://gcc.gnu.org/bugs/> for instructions.

make: *** [/Users/sherlocks/src/CloverBootloader/Build/Clover/RELEASE_GCC53/X64/rEFIt_UEFI/refit/OUTPUT/Platform/StartupSound.obj] Error 1

 

 

build.py...

 : error 7000: Failed to execute command

make tbuild [/Users/sherlocks/src/CloverBootloader/Build/Clover/RELEASE_GCC53/X64/rEFIt_UEFI/refit]

 

 

build.py...

 : error F002: Failed to build module

/Users/sherlocks/src/CloverBootloader/rEFIt_UEFI/refit.inf [X64, GCC53, RELEASE]

 

- Failed -

Build end time: 09:30:50, Oct.12 2019

Build total time: 00:02:27

 

sherlocks@SherloccBookPro ~ % 

 

 

EDIT

when using xcode build with git, i found warning msg

Generating BootSectors

make: Nothing to be done for `all'.

Done!

TOOLCHAIN_DIR: /Users/sherlocks/src/opt/local

MTOC_PREFIX: /Users/sherlocks/src/opt/local/bin/

NASM_PREFIX: /Users/sherlocks/src/opt/local/bin/

NASM_VER: 2.14.02

Building from: /Users/sherlocks/src/CloverBootloader

 

Running edk2 build for CloverX64 using the command:

build  -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/sherlocks/src/CloverBootloader/Conf -D USE_LOW_EBDA -p Clover.dsc  -a X64 -b RELEASE -t XCODE8 -n 5 

 

Build environment: Darwin-19.0.0-x86_64-i386-64bit

Build start time: 09:40:01, Oct.12 2019

 

WORKSPACE        = /Users/sherlocks/src/CloverBootloader

EDK_TOOLS_PATH   = /Users/sherlocks/src/CloverBootloader/BaseTools

CONF_PATH        = /Users/sherlocks/src/CloverBootloader/Conf

 

 

 

Processing meta-data Architecture(s)  = X64

Build target     = RELEASE

.Toolchain        = XCODE8

 

Active Platform          = /Users/sherlocks/src/CloverBootloader/Clover.dsc

....build: : warning: Module MetaFile [Sources] is missing local header!

    Local Header: /users/sherlocks/src/cloverbootloader/include/library/devicetreelib.h not found in /Users/sherlocks/src/CloverBootloader/Library/DeviceTreeLib/DeviceTreeLib.inf

build: : warning: Module MetaFile [Sources] is missing local header!

    Local Header: /users/sherlocks/src/cloverbootloader/include/library/devicetreelib.h not found in /Users/sherlocks/src/CloverBootloader/Library/DeviceTreeLib/DeviceTreeLib.inf

build: : warning: Module MetaFile [Sources] is missing local header!

    Local Header: /users/sherlocks/src/cloverbootloader/include/library/ocguardlib.h not found in /Users/sherlocks/src/CloverBootloader/Library/OcGuardLib/OcGuardLib.inf

build: : warning: Module MetaFile [Sources] is missing local header!

    Local Header: /users/sherlocks/src/cloverbootloader/include/library/ocguardlib.h not found in /Users/sherlocks/src/CloverBootloader/Library/OcGuardLib/OcGuardLib.inf

.build: : warning: Module MetaFile [Sources] is missing local header!

    Local Header: /users/sherlocks/src/cloverbootloader/include/library/macholib.h not found in /Users/sherlocks/src/CloverBootloader/Library/MachoLib/MachoLib.inf

build: : warning: Module MetaFile [Sources] is missing local header!

    Local Header: /users/sherlocks/src/cloverbootloader/include/library/macholib.h not found in /Users/sherlocks/src/CloverBootloader/Library/MachoLib/MachoLib.inf

.. done!

Building ... /Users/sherlocks/src/CloverBootloader/MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint.inf [X64]

Building ... /Users/sherlocks/src/CloverBootloader/MdePkg/Library/UefiLib/UefiLib.inf [X64]

Building ... /Users/sherlocks/src/CloverBootloader/MdePkg/Library/UefiRuntimeServicesTableLib/UefiRuntimeServicesTableLib.inf [X64]

Building ... /Users/sherlocks/src/CloverBootloader/MdePkg/Library/UefiDevicePathLib/UefiDevicePathLib.inf [X64]

Building ... /Users/sherlocks/src/CloverBootloader/MdePkg/Library/UefiMemoryAllocationLib/UefiMemoryAllocationLib.inf [X64]

[CC] DriverEntryPoint

Edited by Sherlocks
Quote

internal compiler error: Segmentation fault: 11

It is wrong compilation of gcc with new Xcode 11.0. I see @vector sigma successfully fix the compilation. Ask him.

I was created gcc9.2 under Mojave with Xcode10.3 and I have good working GCC53 toolset.

 

Quote

....build: : warning: Module MetaFile [Sources] is missing local header!

    Local Header: /users/sherlocks/src/cloverbootloader/include/library/devicetreelib.h not found in /Users/sherlocks/src/CloverBootloader/Library/DeviceTreeLib/DeviceTreeLib.inf

This is wrong warning. I have no it.

It can be corrected if write full path for devicetreelib.h into the inf file. But it is designed to not have it as well as any other global included headers. May be this is python error? Did you updated BaseTools to recent version?

Other way may be create empty local devicetreelib.h in local folder and include a link to it. But the library is designed to have this header to be global.

33 minutes ago, Slice said:

It is wrong compilation of gcc with new Xcode 11.0. I see @vector sigma successfully fix the compilation. Ask him.

I was created gcc9.2 under Mojave with Xcode10.3 and I have good working GCC53 toolset.

 

This is wrong warning. I have no it.

It can be corrected if write full path for devicetreelib.h into the inf file. But it is designed to not have it as well as any other global included headers. May be this is python error? Did you updated BaseTools to recent version?

Other way may be create empty local devicetreelib.h in local folder and include a link to it. But the library is designed to have this header to be global.

okay

thanks alot.

 

if there is commit like update platformdata, i just commit in github?

if sf, automatically update revision. but now seems broken revision now after my commit in github.

how can i update revision like sf?

×
×
  • Create New...