[yocto] DEVTOOL doesn't upgrade glibc as expected
Randy MacLeod
randy.macleod at windriver.com
Wed Feb 13 08:35:20 PST 2019
Adding the list back.
On 1/31/19 12:56 PM, Dhanush K.S wrote:
> Hi Randy,
(back from vacation).
>
> No. Not actually, as we upgraded to Sumo recently and would probably
> jump straight to Warrior if need be.
Warrior is still in development so keep that in mind.
> Wanted to get the time_t functionality for 32 bit arch due to the
> current Y2038 bug. But it seems like GNU has postponed it to future release.
As you can see be reading the Jan 2019 article:
https://lwn.net/Articles/776435/
the Linux Y2038 work is ongoing. Even once it's 'finished', it's
unlikely that you won't have to upgrade your deployed systems to
fix one or two defects so I'm confused about why you seem need/want
this right now rather than in months or a year or more.
>
> Yeah! Would agree with having a combo that no one probably would be
> having. But what I don't get is why the incompatibility with of v2.28
> with Yocto 2.5? Is it inherent with all yocto releases or something to
> do just with sumo?
I don't work on the glibc upgrades so I'm not sure.
There's nothing unique going on in Yocto but rather
changing glibc versions is often lots of work that requires
both broad and deep OS knowledge.
../Randy
>
> Look forward to your views on this.
> Thanks!
>
>
> On Wed, 30 Jan 2019 at 21:10, Randy MacLeod <randy.macleod at windriver.com
> <mailto:randy.macleod at windriver.com>> wrote:
>
> On 1/30/19 8:42 AM, Burton, Ross wrote:
> > No doubt devtool should handle this better, but upgrading glibc is
> > *not easy*. If you can't do it manually then I wouldn't recommend
> > doing it at all.
> >
> > A better start would be to copy the recipes from git for the version
> > you want, and then you'll be able to pick up all of the patches to
> > other recipes that you'll also need.
>
> Have you seriously considered upgrading to Thud/2.6.x?
>
> What feature(s) do you want that makes you feel that an
> upgrade it to v2.28 is worth the effort? If you put the
> work in to do the update, you'll have a YP-based combo that
> no one else is using. While that may get you exactly what you want,
> there will be costs involved in maintaining it so I'm curious
> about your motivation and thoughts about maintenance.
>
> ../Randy
>
> >
> > Ross
> >
> > On Wed, 30 Jan 2019 at 13:35, Dhanush K.S <dhanush.ks at gmail.com
> <mailto:dhanush.ks at gmail.com>> wrote:
> >>
> >> Hi,
> >>
> >> I'm currently using Yocto Sumo 2.5 release with the glibc
> version 2.27 and would like to upgrade it to v2.28.
> >> Using the devtool upgrade glibc -V 2.28 -S
> 044c96f0d5595aeb0bb4e79355081c5a7f4faca5 doesn't work as expected.
> >> In turn it creates the workspace/recipes/glibc_2.28.bb
> <http://glibc_2.28.bb> recipe with the contents and SRC_URI of v2.27.
> >>
> >> devtool upgrade glibc -S 044c96f0d5595aeb0bb4e79355081c5a7f4faca5
> >> NOTE: Starting bitbake server...
> >> NOTE: Creating workspace layer in
> /source/yocto/build_arm-cortex-a8/workspace
> >>
> >> NOTE: Extracting current version source...
> >> NOTE: Resolving any missing task queue dependencies
> >>
> >> Build Configuration:
> >> BB_VERSION = "1.37.0"
> >> BUILD_SYS = "x86_64-linux"
> >> NATIVELSBSTRING = "universal-4.8"
> >> TARGET_SYS = "arm-poky-linux-gnueabi"
> >> MACHINE = "arm-cortex-a8"
> >> DISTRO = "poky"
> >> DISTRO_VERSION = "2.5"
> >> TUNE_FEATURES = "arm armv7a vfp neon callconvention-hard
> cortexa8"
> >> TARGET_FPU = "hard"
> >> meta
> >> meta-poky
> >> meta-yocto-bsp
> >> meta-oe =
> "master:45ee3c0e98bd3ed81419aaeae1e7324e486161a2"
> >> workspace = "<unknown>:<unknown>"
> >>
> >> NOTE: Executing RunQueue Tasks
> >> NOTE: Tasks Summary: Attempted 3 tasks of which 0 didn't need to
> be rerun and all succeeded.
> >> NOTE: Writing buildhistory
> >> NOTE: Adding local source files to srctree...
> >> NOTE: Extracting upgraded version source...
> >> WARNING: Command 'git rebase
> 044c96f0d5595aeb0bb4e79355081c5a7f4faca5' failed:
> >> First, rewinding head to replay your work on top of it...
> >> Applying: sparc: Check PIC instead of SHARED in start.S [BZ #22638]
> >> error: Failed to merge in the changes.
> >> Using index info to reconstruct a base tree...
> >> M ChangeLog
> >> M sysdeps/sparc/sparc32/start.S
> >> M sysdeps/sparc/sparc64/start.S
> >> Falling back to patching base and 3-way merge...
> >> Auto-merging ChangeLog
> >> CONFLICT (content): Merge conflict in ChangeLog
> >> Patch failed at 0001 sparc: Check PIC instead of SHARED in
> start.S [BZ #22638]
> >> The copy of the patch that failed is found in:
> .git/rebase-apply/patch
> >>
> >> Resolve all conflicts manually, mark them as resolved with
> >> "git add/rm <conflicted_files>", then run "git rebase --continue".
> >> You can instead skip this commit: run "git rebase --skip".
> >> To abort and get back to the state before "git rebase", run "git
> rebase --abort".
> >>
> >> You will need to resolve conflicts in order to complete the upgrade.
> >> Traceback (most recent call last):
> >> File "/source/yocto/poky-sumo-19.0.0/scripts/devtool", line
> 344, in <module>
> >> ret = main()
> >> File "/source/yocto/poky-sumo-19.0.0/scripts/devtool", line
> 331, in main
> >> ret = args.func(args, config, basepath, workspace)
> >> File
> "/source/yocto/poky-sumo-19.0.0/scripts/lib/devtool/upgrade.py",
> line 559, in upgrade
> >> rf, copied = _create_new_recipe(args.version, md5, sha256,
> args.srcrev, srcbranch, srcsubdir1, srcsubdir2,
> config.workspace_path, tinfoil, rd, license_diff, new_licenses)
> >> File
> "/source/yocto/poky-sumo-19.0.0/scripts/lib/devtool/upgrade.py",
> line 344, in _create_new_recipe
> >> scheme, network, path, user, passwd, params =
> bb.fetch2.decodeurl(entry)
> >> File
> "/source/yocto/poky-sumo-19.0.0/bitbake/lib/bb/fetch2/__init__.py",
> line 368, in decodeurl
> >> raise MalformedUrl(url)
> >> bb.fetch2.MalformedUrl: The URL:
> '${GLIBC_GIT_URI};branch=${SRCBRANCH};name=glibc' is invalid and
> cannot be interpreted.
> >>
> >> Need help with this one.
> >>
> >> Thanks,
> >> Dhanush
> >> --
> >> _______________________________________________
> >> yocto mailing list
> >> yocto at yoctoproject.org <mailto:yocto at yoctoproject.org>
> >> https://lists.yoctoproject.org/listinfo/yocto
>
>
> --
> # Randy MacLeod
> # Wind River Linux
>
--
# Randy MacLeod
# Wind River Linux
More information about the yocto
mailing list