• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
UBports Robot Logo UBports Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Can not locate config makefile for product

Scheduled Pinned Locked Moved Porting
2 Posts 2 Posters 453 Views 1 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • U Offline
      unger
      last edited by 12 Mar 2024, 21:11

      Hello
      I'm using halium 7.1 to build ubuntu toch.
      When executing the command breakfast m31
      gives the error: *** Can not locate config makefile for product "lineage_m31". Stop.

      But I have a file called lineage_m31 in the /device/samsung/m31/ folder

      Why does this error occur?

      root@bd5509508ee9:/var/android# breakfast m31
      including vendor/cm/vendorsetup.sh
      build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_m31".  Stop.
      build/core/product_config.mk:249: *** Can not locate config makefile for product "cm_m31".  Stop.
      build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_m31".  Stop.
      Device m31 not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
      Repository for m31 not found in the LineageOS Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
      build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_m31".  Stop.
      build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_m31".  Stop.
      
      ** Don't have a product spec for: 'lineage_m31'
      ** Do you have the right repo manifest?
      
      1 Reply Last reply Reply Quote 0
      • F Offline
        Fray_Tormenta
        last edited by 31 Mar 2024, 06:01

        it's by bad repo manifest. See the paths maybe it's wrong formed

        1 Reply Last reply Reply Quote 0
        • First post
          Last post