Hello,

the issue was in my rmakerc file that's located on the build server.

So problem solved.

// Tomas Forsman

On Sun, 1 Jun 2014 20:20:32 -0400
Tomas Forsman <[email protected]> wrote:

> Hello again,
> 
> The issue is only when building with rmake.
> 
> If i cook it on my own with cvc cook kernel.recipe, then everything
> goes as expected.
> 
> this is what i want and expects when seeing it build:
> 
> + cd '/home/tforsman/conary/builds/kernel/linux-3.10.17/'; CFLAGS="-O2
>   -g -D_FORTIFY_SOURCE=2 -fstack-protector" CXXFLAGS="-O2 -g
>   -D_FORTIFY_SOURCE=2 -fstack-protector " CPPFLAGS="" CLASSPATH=""
>   LDFLAGS="-g -O1 " CC=gcc CXX=g++  make    -s
>   INSTALL_MOD_PATH=/home/tforsman/conary/builds/kernel/_ROOT_
>   modules_install KERNELRELEASE=2.6.50.17-3-foresight.x86_64 mod-fw=
> + copying /home/tforsman/conary/builds/kernel/linux-3.10.17/System.map
>   to 
> /home/tforsman/conary/builds/kernel/_ROOT_/boot/System.map-2.6.50.17-3-foresight.x86_64
> 
> 
> In rmake with same recipe, i see this instead:
> 
> + cd '/tmp/rmake/builds/kernel/linux-3.10.17/'; CFLAGS="-O2 -g
>   -D_FORTIFY_SOURCE =2 -fstack-protector" CXXFLAGS="-O2 -g
>   -D_FORTIFY_SOURCE=2 -fstack-protector " C PPFLAGS="" CLASSPATH=""
>   LDFLAGS="-g -O1 " CC=gcc CXX=g++  make   -j6 -s INSTALL
>   _MOD_PATH=/tmp/rmake/builds/kernel/_ROOT_ modules_install
>   KERNELRELEASE=2.6.35.1 0-4-fl.smp.gcc4.4.x86_64 mod-fw=
> + copying /tmp/rmake/builds/kernel/linux-3.10.17/System.map
>   to /tmp/rmake/builds 
> /kernel/_ROOT_/boot/System.map-2.6.35.10-4-fl.smp.gcc4.4.x86_64
> 
> 
> So, no issue with locally builds with cvc cook, only with rmake....
> 
> 
> // Tomas Forsman
> 
> 
> On Sun, 1 Jun 2014 18:35:05 -0400
> Tomas Forsman <[email protected]> wrote:
> 
> > Hello,
> > 
> > Been struggling with another issue whole weekend and still isn't
> > solved yet.
> > 
> > no matter how I build it, it gets wrong version string in module
> > folder. It ends up like this:
> > 
> > /lib/modules/2.6.35.10-4-fl.smp.gcc4.4.x86_64/kernel/sound/usb/usx2y/snd-usb-us122l.ko
> > 
> > As you see, the version gets 2.6.35.10, it should be 2.6.50.17
> > as im trying to build 3.10.17 version.
> > 
> > We got today 2.6.44.** (3.4 kernel)
> > /lib/modules/2.6.44.45-1-foresight.x86_64/build/include/sound/wm2200.h
> > 
> > 
> > Iv'e been looking everywhere in kernel source to find the issue of
> > it, and I can't find anywhere were it picks up the version
> > 2.6.35.10.
> > 
> > The only thing I can think of, is that it calculates wrong
> > somewhere. as 2.6.35.10 is wrong in many places. As it would be
> > 2.6.**.17 today. As im trying to build 3.10.17
> > 
> > So i'm stuck at this moment.
> > 
> > If someone got time to explain where it picks up the fake version
> > and why it gets so wrong today, that would be nice.
> > 
> > 
> > 
> > We got a working version of this version at:
> > kernel=reloaded.rpath.org@kernel:latest, we are using same kernel
> > recipe too, so I think the issue isn't in kernel package, it's
> > located somewhere else.
> > If you look how the path is in that kernel, it looks sane:
> > /lib/modules/2.6.50.17-1-foresight.x86_64/kernel/sound/ac97_bus.ko
> > 
> > 
> > So I really hope someone got time to help out and point me to the
> > right direction of this issue.
> > 
> > 
> > 
> > // Tomas Forsman
> > 
> > 
> > 
> > 
> > On Fri, 30 May 2014 00:10:25 +0200
> > Foresight <[email protected]> wrote:
> > 
> > > On Fri May 30 05:21:44 2014 Tomas Forsman
> > > <[email protected]> wrote:
> > > > 
> > > > Hello,
> > > 
> > > Hi,
> > > > Probably solved now. rebuilt every package that are involved
> > > > with kernel.
> > > > 
> > > > Hopefully in few hours, we got a new rebuild of groups with some
> > > > updates of common packages.
> > > 
> > > Thanks for picking up where I had to leave off.
> > > I just didn't find the time yesterday.
> > > 
> > > > // Tomas Forsman
> > > > 
> > > > 
> > > > 
> > > > On Wed, 28 May 2014 22:43:48 -0400
> > > > Tomas Forsman <[email protected]> wrote:
> > > > 
> > > > > Hello,
> > > > > 
> > > > > I'm trying to close up the groups in fl:2-devel but seems it
> > > > > still pulls in older kernel and makes it impossible to build
> > > > > groups at the moment.
> > > > > 
> > > > > The issue I see when building groups is:
> > > > > 
> > > > > group-lxde-dist=/foresight.rpath.org@fl:devel//2-devel/2.5.4+2014.05.27-0.2-1[~!bootstrap,~buildtests,~!cross,desktop,~!dom0,~!domU,~!gcc.core,gnome,~grub.static,ipv6,~kernel.debugdata,krb,ldap,pam,readline,ssl,tcl,tk,~!vmware,~!xen
> > > > > is: x86(i486,i586,i686,sse,sse2) x86_64]
> > > > > kernel=/foresight.rpath.org@fl:2-devel-kernel/3.4.67-1-1[~kernel.debugdata,~!xen
> > > > > is: x86_64]
> > > > > kernel:configs=/foresight.rpath.org@fl:2-devel-kernel/3.4.67-1-1[~kernel.debugdata,~!xen
> > > > > is: x86_64]
> > > > > 
> > > > > kernel:configs=/foresight.rpath.org@fl:2-devel-kernel/3.4.67-1-1[~kernel.debugdata,~!xen
> > > > > is: x86_64]: (Added directly)
> > > > > 
> > > > > 
> > > > > I assume it should use atleast 3.10 version that is in
> > > > > fl:2-devel-kernel.
> > > > > 
> > > > > 
> > > > > It was built like this:
> > > > > rmake build --context=fl:2-devel
> > > > > {ati-fglrx-kernel,broadcom-wl-kmod,kernel,ndiswrapper-kernel,nvidia-kernel,rt2870-kernel,tp_smapi-kernel,virtualbox-kernel}=@fl:2-devel-kernel{{x86,x86_64}}
> > > > > 
> > > > > Also changed in one place in group-desktop-platform to match
> > > > > the right version of kernel.
> > > > > 
> > > > > 
> > > > > So what did I miss?
> > > > > Anyone got a clue....Antonio maybe?
> > > > > 
> > > > > 
> > > > > // Tomas Forsman
> > > > > 
> > > > > _______________________________________________
> > > > > Foresight-devel mailing list
> > > > > [email protected]
> > > > > https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
> > > > > 
> > > > _______________________________________________
> > > > Foresight-devel mailing list
> > > > [email protected]
> > > > https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
> > > > 
> > > 
> > > _______________________________________________
> > > Foresight-devel mailing list
> > > [email protected]
> > > https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
> > > 
> > 
> > _______________________________________________
> > Foresight-devel mailing list
> > [email protected]
> > https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
> > 
> 
> _______________________________________________
> Foresight-devel mailing list
> [email protected]
> https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
> 

_______________________________________________
Foresight-devel mailing list
[email protected]
https://lists.foresightlinux.org/mailman/listinfo/foresight-devel

Reply via email to