Jump to content

Build fails error: ‘YT_8531C_PHY_ID’ undeclared


mfreudenberg

Recommended Posts

Hi,

 

my current CI build fails, and i cannot make up, whats wrong with it. It was working previously until i moved my project within the GitLab instance to another folder. Now i'm getting the following errors:

 

tail output.log

OBJCOPY lib/efi_loader/dtbdump.efi
  CC      lib/vsprintf.o
  CC      lib/strto.o
  CC      lib/abuf.o
  OBJCOPY lib/efi_loader/initrddump.efi
  CC      lib/date.o
  CC      lib/rtc-lib.o
  CC      lib/elf.o
  AR      lib/built-in.o
[ error ] ERROR in function compile_uboot [ functions/cli/cli-entrypoint.sh:109 -> functions/main/build-tasks.sh:261 -> functions/main/build-tasks.sh:128 -> functions/compilation/uboot.sh:131 -> functions/logging/traps.sh:0 ]
[ error ] U-boot compilation failed
[ o.k. ] Process terminated

 

# somewhere in the middle of the compilation.log

CC      cmd/sf.o
  AR      drivers/nvme/built-in.o
  AR      drivers/power/battery/built-in.o
  AR      drivers/power/fuel_gauge/built-in.o
  CC      cmd/sysboot.o
drivers/net/phy/phy.c: In function get_phy_driver’:
drivers/net/phy/phy.c:652:15: error: YT_8531C_PHY_ID undeclared (first use in this function)
  652 |  if(phy_id == YT_8531C_PHY_ID)
      |               ^~~~~~~~~~~~~~~
drivers/net/phy/phy.c:652:15: note: each undeclared identifier is reported only once for each function >
  AR      drivers/power/mfd/built-in.o
make[3]: *** [scripts/Makefile.build:254: drivers/net/phy/phy.o] Error 1
make[2]: *** [scripts/Makefile.build:394: drivers/net/phy] Error 2
make[2]: *** Waiting for unfinished jobs....
  CC      drivers/pinctrl/pinctrl-uclass.o
  CC      drivers/power/pmic/pmic-uclass.o
  CC      drivers/power/regulator/regulator-uclass.o

 

 tail compilation.log
  CC      drivers/video/panel-uclass.o
  CC      drivers/video/simple_panel.o
  TTF     drivers/video/u_boot_logo.S
  OBJCOPY lib/efi_loader/initrddump.efi
  CC      drivers/video/dw_hdmi.o
  AR      lib/built-in.o
  AS      drivers/video/u_boot_logo.o
  AR      drivers/video/rockchip/built-in.o
  AR      drivers/video/built-in.o
make: *** [Makefile:1894: drivers] Error 2

 

I have tried to switch the repo mirrors, or different tags. I even deleted the entire checked out directory (build) and checked it out again. After cloning the repo and running the compile script with my config-default.config i'm ending up with the same error.

 

Any idea, what could be wrong? I already checked the permissions (actually I'm running the compile script as root).

It seems there is some issue with the network driver?

 

my config-default.conf

# Read build script documentation https://docs.armbian.com/Developer-Guide_Build-Options/
# for detailed explanation of these options and for additional options not listed here

# leave empty to select each time, set to "yes" or "no">
KERNEL_ONLY="no"
# leave empty to select each time, set to "yes" or "no" to skip>
KERNEL_CONFIGURE="no"

# comma-separated list of clean targets: "make" = make clean for select>
# "debs" = delete packages in "./output>
# "alldebs" = delete all packages in ".>
# "cache" = delete "./output/cache", "s>
# "oldcache" = remove old cached rootfs>
CLEAN_LEVEL="make,debs,cache"   

# yes: use kernel config file from previous compilation for the same branch, device family and version
# no: use default or user-provided config file
KERNEL_KEEP_CONFIG="yes"

# comma-separated list of core modules which will be installed >
# "u-boot", "kernel", "bsp", "armbian-config", "armbian-firmwar>
# leave empty to build from sources or use local cache
REPOSITORY_INSTALL=""                   

BUILD_DESKTOP="yes"
DEST_LANG="de_DE.UTF-8"

# advanced
# compile and install or install prebuilt additional packages
EXTERNAL_NEW="prebuilt"

# change to "branchname" to use any branch currently available.
LIB_TAG="v22.08"

# additions to compile 'unattended'
DESKTOP_ENVIRONMENT="xfce"
DESKTOP_APPGROUPS_SELECTED="editors, internet"
DESKTOP_ENVIRONMENT_CONFIG_NAME="config_base"

# additions to compile for the rock-pi4
BOARD="rockpi-4b"
BRANCH="current"
RELEASE="bullseye"

# yes: will stop the script and prompt for adding userpatches (kernel, u-boot)
CREATE_PATCHES="no"

# creates logs in output/debug
PROGRESS_LOG_TO_FILE="yes"

# set to yes, to prevent cloning from git
OFFLINE_WORK="no"
# provides a faster download
USE_MAINLINE_GOOGLE_MIRROR="yes"
USE_GITHUB_UBOOT_MIRROR="yes"
# create compressed archive with image file and GPG signature f>
# yes - compatibility shorcut for sha,gpg,7z
COMPRESS_OUTPUTIMAGE="yes"

 

Link to comment
Share on other sites

Hi,

 

thanks for the tip. Unfortunately, that seem not to work. I have done the following:

 

  • Switched to branch "v22.11" by setting it in the LIB_TAG variable of `config-default.conf`
  • I have forced my GitLab CI process to checkout the v22.11 tag by including git clone -b v22.11 ... into the script
  • I have set the BUILD_ONLY="" to empty (as recommended by the script)
  • I have installed another VM, with a gitlab-runner and attached this gitlab-runner to my instance.
  • I have removed any caching from my ci pipeline as i thought this might cause the issue.
    • previously i had a three stage build process, that had a checkout, build and cleanup stage.
    • the checkout stage, did the cloning of the armbian-build repo and stored it into a gitlab cache
    • the build stage used this cache and moved the userpatches folder to the build subfolder. The existing userpatches folder gets deleted every time.
    • the cleanup stage, deleted any built images from the cache to preserve some disk space, before storing the cache

 

I'm not sure, what happend, that my build suddenly fails. Right now, i'm falling back to building it semi-manual. I'm cloning my repo (containing the customization scripts) on a VM and merge it with a freshly cloned armbian-build repo.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines