Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
gcc upgrade
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2  
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
ONEEYEMAN
Advocate
Advocate


Joined: 01 Mar 2005
Posts: 2754

PostPosted: Sat Mar 17, 2018 5:07 am    Post subject: Reply with quote

Hu,
What I did is following:
I started Anjuta, created a project and couple of libraries projects.
Added the source code compiled it and then use the "Install" feature from Anjuta.
The Anjuta IDE was installed as is from the Portage and I would be surprised if it did something non-stanhdard.

Now back to my original question - I thought that in order to make baselayout happy and make it installed all I need to do is to create such a symlink.
If not - than I don't understand why the symlink is even popping up here.

Thank you.
Back to top
View user's profile Send private message
Tony0945
Advocate
Advocate


Joined: 25 Jul 2006
Posts: 2605
Location: Illinois, USA

PostPosted: Sat Mar 17, 2018 3:12 pm    Post subject: Reply with quote

Hu, I think he is saying that he is building and installing outside of portage. Many packages install into /usr/local/bin and /usr/local/lib instead of /usr/bin and /usr/lib if the distro's package manager isn't used. It may or may not be correct procedure but it is common.

ONEEYEDMAN, I strongly suggest building with portage from the beginning using an overlay in /usr/local/portage. If you don't, you wind up with conflicts because of install scripts spraying files all over. If you use portage, even if the files are misplaced, portage knows where it put them and can remove them.
Back to top
View user's profile Send private message
ONEEYEMAN
Advocate
Advocate


Joined: 01 Mar 2005
Posts: 2754

PostPosted: Sat Mar 17, 2018 3:47 pm    Post subject: Reply with quote

Tony0945,
As I said I am still developing and so this software is WIP. And so can't be installed thru the Portage.
Unfortunately it looks like an update somewhere broke the system and make it in an un-usable state, so that the next update is not possible. This is the only sane explanation I have right now. Because it seems that /usr/local/lib has to be a symlink to /usr/lib{64} and /usr/local/bin to /usr/bin. Because I check another install of Gentoo and this is the way it is set up
But the latest reply from Hu indicates that this is wrong fix.

I wonder why?

Thank you.
Back to top
View user's profile Send private message
John R. Graham
Administrator
Administrator


Joined: 08 Mar 2005
Posts: 10120
Location: Somewhere over Atlanta, Georgia

PostPosted: Sat Mar 17, 2018 4:00 pm    Post subject: Reply with quote

ONEEYEMAN wrote:
As I said I am still developing and so this software is WIP. And so can't be installed thru the Portage.
Why on earth would that be true? I have ebuilds for all of my in-development software. Here's what I do, including a sample ebuild.

- John
_________________
I can confirm that I have received between 0 and 499 National Security Letters.
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 12805

PostPosted: Sat Mar 17, 2018 5:07 pm    Post subject: Reply with quote

Tony0945 wrote:
Hu, I think he is saying that he is building and installing outside of portage. Many packages install into /usr/local/bin and /usr/local/lib instead of /usr/bin and /usr/lib if the distro's package manager isn't used. It may or may not be correct procedure but it is common.
Yes, I understood that, and for the reasons you gave in the second part of your post, I disapprove of the practice of installing system-wide outside Portage in almost all cases. Secondarily, if all the files shown in his output are owned by his in-development package, then I expect file collisions if/when he ever tries to manage it through Portage.
Back to top
View user's profile Send private message
ONEEYEMAN
Advocate
Advocate


Joined: 01 Mar 2005
Posts: 2754

PostPosted: Sat Mar 17, 2018 10:41 pm    Post subject: Reply with quote

Hi, guys,
@John,
So even on the early stages of your development you using the ebuild?
I'm trying to create a cross-platform DB handler software in C++.

@Hu,
For now I want my system to become sane. I can fix the names of the libraries later when the software is ready to be released.

Thank you.
Back to top
View user's profile Send private message
John R. Graham
Administrator
Administrator


Joined: 08 Mar 2005
Posts: 10120
Location: Somewhere over Atlanta, Georgia

PostPosted: Sat Mar 17, 2018 11:00 pm    Post subject: Reply with quote

ONEEYEMAN wrote:
So even on the early stages of your development you using the ebuild?
Well it depends on what you mean by early. If I'm just building it in and running it from my project directory, then maybe not. But if it's mature enough to be installing things in non-$HOME directories, then absolutely. I don't want my install polluted, even by my software. Also, as soon as I start using it on multiple machines, my personal overlay is a great way to distribute it.

- John
_________________
I can confirm that I have received between 0 and 499 National Security Letters.
Back to top
View user's profile Send private message
ONEEYEMAN
Advocate
Advocate


Joined: 01 Mar 2005
Posts: 2754

PostPosted: Sat Mar 17, 2018 11:29 pm    Post subject: Reply with quote

@John,
I was told that I can't run the software from Anjuta from the build directory.
Anjuta developers told me that I have to install the binary executable and all libraries I produce in order to run/debug the software from Anjuta.

I can try to dig up that E-mail if needed.

So I'm just following that suggestion.

Thank you.
Back to top
View user's profile Send private message
John R. Graham
Administrator
Administrator


Joined: 08 Mar 2005
Posts: 10120
Location: Somewhere over Atlanta, Georgia

PostPosted: Sun Mar 18, 2018 12:02 am    Post subject: Reply with quote

Then under those circumstances I would definitely create an ebuild to track the installation.

- John
_________________
I can confirm that I have received between 0 and 499 National Security Letters.
Back to top
View user's profile Send private message
Tony0945
Advocate
Advocate


Joined: 25 Jul 2006
Posts: 2605
Location: Illinois, USA

PostPosted: Sun Mar 18, 2018 1:53 am    Post subject: Reply with quote

I just took a look at the only anjuta ebuild in the tree. Nothing really weird. it should be easy to clone and modify.

EDIT:
As long as you type better than me!
Back to top
View user's profile Send private message
ONEEYEMAN
Advocate
Advocate


Joined: 01 Mar 2005
Posts: 2754

PostPosted: Sun Mar 18, 2018 5:48 pm    Post subject: Reply with quote

Hi,guys,
@Tony0945,
It is not about ebuild. As far as I understand Anjuta is written so that when you try to debug or run the binary you just build from inside Anjuta, it looks in the standard /usr/{local/}lib{64} tree for all so libraries it linked to. Simply because it probably relies on the lddconfig output.
That is my understanding.

So the ebuild is fine - its Anjuta source code that needs fixing.
Unfortunately I'm not really great with GTK+ programming to find where and what needs to be changed.

@John,
The problem at hand is not the {bad} names of the libraries - it is baselayout installation (see above). So this /usr/local/lib not being a symlink should be fixed somehow.
It is Hu who tried to move this thread away from the point/problem I'm trying to solve - make the system sane so that I can rebuild wx and my software and continue the development process.

Thank you.
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 12805

PostPosted: Sun Mar 18, 2018 7:57 pm    Post subject: Reply with quote

Strictly speaking, I tried to solve both your stated problem (and did), and your unreported problem (bad installation) which I expect will cause you trouble eventually.
Back to top
View user's profile Send private message
skellr
l33t
l33t


Joined: 18 Jun 2005
Posts: 815
Location: The Village, Portmeirion

PostPosted: Sun Mar 18, 2018 8:08 pm    Post subject: Reply with quote

ONEEYEMAN wrote:
Code:

IgorDellGentoo /home/igor/dbhandler # ls -la /usr/local
total 28
drwxr-xr-x  7 root root 4096 Mar 16  2016 .
drwxr-xr-x 14 root root 4096 Apr  7  2016 ..
drwxr-xr-x  2 root root 4096 Nov 25 05:32 bin
drwxr-xr-x 19 root root 4096 Jul 30  2016 include
drwxr-xr-x  2 root root 4096 Nov 25 05:32 lib
drwxr-xr-x  2 root root 4096 May 28  2014 sbin
drwxr-xr-x  7 root root 4096 Mar 16  2016 share

At least the baselayout issue seems an easy fix.
Code:
mv /usr/local/lib /usr/local/lib64
ln -s /usr/local/lib64 /usr/local/lib
Back to top
View user's profile Send private message
grumblebear
Tux's lil' helper
Tux's lil' helper


Joined: 26 Feb 2008
Posts: 116

PostPosted: Sun Mar 18, 2018 8:31 pm    Post subject: Reply with quote

/usr/local/lib should not be a symlink to /usr/lib but to /usr/local/lib64. Fortunately I switched to the 17.1 profile, and this annoyance is history. Personally I still do install certain things to /usr/local. You just have to know what you are doing.

To come back to your original problem: The latest change of math.h indicates that the change of the default C++ mode in gcc-6 is the cause of your problem.
Back to top
View user's profile Send private message
ONEEYEMAN
Advocate
Advocate


Joined: 01 Mar 2005
Posts: 2754

PostPosted: Sun Mar 18, 2018 8:59 pm    Post subject: Reply with quote

Hi,
skellr wrote:

ONEEYEMAN wrote:

Code:

IgorDellGentoo /home/igor/dbhandler # ls -la /usr/local
total 28
drwxr-xr-x  7 root root 4096 Mar 16  2016 .
drwxr-xr-x 14 root root 4096 Apr  7  2016 ..
drwxr-xr-x  2 root root 4096 Nov 25 05:32 bin
drwxr-xr-x 19 root root 4096 Jul 30  2016 include
drwxr-xr-x  2 root root 4096 Nov 25 05:32 lib
drwxr-xr-x  2 root root 4096 May 28  2014 sbin
drwxr-xr-x  7 root root 4096 Mar 16  2016 share


At least the baselayout issue seems an easy fix.
Code:
mv /usr/local/lib /usr/local/lib64
ln -s /usr/local/lib64 /usr/local/lib



At the very least you have an error.
The last line should be:

Code:

ln -s /usr/local/lib /usr/local/lib64


However, after doing this, I still got an issue:

Code:

gorDellGentoo /usr/local # emerge baselayout                   
 * Last emerge --sync was 118d 20h 14m 21s ago.
Calculating dependencies... done!

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) sys-apps/baselayout-2.4.1-r2::gentoo
 * baselayout-2.4.1.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ...                                                                      [ ok ]
 * Converting /usr/local/lib from a dir to a symlink
 * ERROR: sys-apps/baselayout-2.4.1-r2::gentoo failed (setup phase):
 *   non-empty dir found where we needed a symlink: /usr/local/lib
 *
 * Call stack:
 *                    ebuild.sh, line 124:  Called pkg_setup
 *   baselayout-2.4.1-r2.ebuild, line  18:  Called multilib_layout
 *   baselayout-2.4.1-r2.ebuild, line  67:  Called die
 * The specific snippet of code:
 *                                      die "non-empty dir found where we needed a symlink: ${prefix}lib"
 *
 * If you need support, post the output of `emerge --info '=sys-apps/baselayout-2.4.1-r2::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/baselayout-2.4.1-r2::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-apps/baselayout-2.4.1-r2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/baselayout-2.4.1-r2/temp/die.env'.
 * Working directory: '/var/tmp/portage/sys-apps/baselayout-2.4.1-r2/homedir'
 * S: '/var/tmp/portage/sys-apps/baselayout-2.4.1-r2/work/baselayout-2.4.1'

>>> Failed to emerge sys-apps/baselayout-2.4.1-r2, Log file:

>>>  '/var/tmp/portage/sys-apps/baselayout-2.4.1-r2/temp/build.log'

 * Messages for package sys-apps/baselayout-2.4.1-r2:

 * Converting /usr/local/lib from a dir to a symlink
 * ERROR: sys-apps/baselayout-2.4.1-r2::gentoo failed (setup phase):
 *   non-empty dir found where we needed a symlink: /usr/local/lib
 *
 * Call stack:
 *                    ebuild.sh, line 124:  Called pkg_setup
 *   baselayout-2.4.1-r2.ebuild, line  18:  Called multilib_layout
 *   baselayout-2.4.1-r2.ebuild, line  67:  Called die
 * The specific snippet of code:
 *                                      die "non-empty dir found where we needed a symlink: ${prefix}lib"
 *
 * If you need support, post the output of `emerge --info '=sys-apps/baselayout-2.4.1-r2::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/baselayout-2.4.1-r2::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-apps/baselayout-2.4.1-r2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/baselayout-2.4.1-r2/temp/die.env'.
 * Working directory: '/var/tmp/portage/sys-apps/baselayout-2.4.1-r2/homedir'
 * S: '/var/tmp/portage/sys-apps/baselayout-2.4.1-r2/work/baselayout-2.4.1'

IgorDellGentoo /usr/local # ls -la /usr/local/lib
total 8
drwxr-xr-x 2 root root 4096 Mar 18 21:45 .
drwxr-xr-x 7 root root 4096 Mar 18 21:49 ..
lrwxrwxrwx 1 root root   16 Mar 18 21:45 lib64 -> /usr/local/lib64

IgorDellGentoo /usr/local # ls -la /usr/local
total 28
drwxr-xr-x  7 root root 4096 Mar 18 21:49 .
drwxr-xr-x 14 root root 4096 Apr  7  2016 ..
drwxr-xr-x  2 root root 4096 Nov 25 05:32 bin
drwxr-xr-x 19 root root 4096 Jul 30  2016 include
drwxr-xr-x  2 root root 4096 Mar 18 21:45 lib
lrwxrwxrwx  1 root root   14 Mar 18 21:49 lib64 -> /usr/local/lib
drwxr-xr-x  2 root root 4096 May 28  2014 sbin
drwxr-xr-x  7 root root 4096 Mar 16  2016 share



Should I do the same with /usr/local/bin?

Thank you.
Back to top
View user's profile Send private message
skellr
l33t
l33t


Joined: 18 Jun 2005
Posts: 815
Location: The Village, Portmeirion

PostPosted: Sun Mar 18, 2018 9:10 pm    Post subject: Reply with quote

ONEEYEMAN wrote:
Hi,
At the very least you have an error.
The last line should be:

Code:

ln -s /usr/local/lib /usr/local/lib64



No, sorry. lib64 is the "real" directory and lib is the symlink.
Code:

skellr@quark ~ $ ls -l /usr/local/
total 4
drwxr-xr-x 1 root root  60 Mar 15 21:23 bin
drwxr-xr-x 1 root root  20 Mar 14 18:59 include
lrwxrwxrwx 1 root root   5 Feb  6 21:49 lib -> lib64
drwxr-xr-x 1 root root 166 Mar 15 21:23 lib64
drwxr-xr-x 1 root root  56 Mar 15 19:42 junk
drwxr-xr-x 1 root root  10 Feb  6 21:51 sbin
drwxr-xr-x 1 root root  36 Mar 14 18:59 share



...

error wrote:
die "non-empty dir found where we needed a symlink: ${prefix}lib"
Back to top
View user's profile Send private message
ONEEYEMAN
Advocate
Advocate


Joined: 01 Mar 2005
Posts: 2754

PostPosted: Mon Mar 19, 2018 7:35 pm    Post subject: Reply with quote

Hi,
OK, I pass baselayout, but now have a different issue:

Code:

gorDellGentoo /usr/local # emerge linux-firmware
Calculating dependencies... done!

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) sys-kernel/linux-firmware-20170314::gentoo
>>> Downloading 'http://distfiles.gentoo.org/distfiles/linux-firmware-20170314.tar.xz'
--2018-03-19 20:30:54--  http://distfiles.gentoo.org/distfiles/linux-firmware-20170314.tar.xz
Resolving distfiles.gentoo.org... 2600:3404:200:237::2, 2600:3402:200:227::2, 2605:bc80:3010::134, ...
Connecting to distfiles.gentoo.org|2600:3404:200:237::2|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2018-03-19 20:30:55 ERROR 404: Not Found.

>>> Downloading 'https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-e39f0e3e6897ad865b3704f61218ae83f98a85da.tar.xz'
--2018-03-19 20:30:55--  https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-e39f0e3e6897ad865b3704f61218ae83f98a85da.tar.xz
Resolving git.kernel.org... 2604:1380:4020:600::1, 147.75.58.133
Connecting to git.kernel.org|2604:1380:4020:600::1|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-e39f0e3e6897ad865b3704f61218ae83f98a85da.tar.xz [following]
--2018-03-19 20:30:55--  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-e39f0e3e6897ad865b3704f61218ae83f98a85da.tar.xz
Reusing existing connection to [git.kernel.org]:443.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://git.kernel.org//pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-e39f0e3e6897ad865b3704f61218ae83f98a85da.tar.gz [following]
--2018-03-19 20:30:55--  https://git.kernel.org//pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-e39f0e3e6897ad865b3704f61218ae83f98a85da.tar.gz
Reusing existing connection to [git.kernel.org]:443.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/x-gzip]
Saving to: '/usr/portage/distfiles/linux-firmware-20170314.tar.xz'

/usr/portage/distfi     [ <=>                ]  91.62M  3.26MB/s    in 42s     

2018-03-19 20:31:46 (2.18 MB/s) - '/usr/portage/distfiles/linux-firmware-20170314.tar.xz' saved [96072698]

!!! Fetched file: linux-firmware-20170314.tar.xz VERIFY FAILED!
!!! Reason: Filesize does not match recorded size
!!! Got:      96072698
!!! Expected: 43175092
Refetching... File renamed to '/usr/portage/distfiles/linux-firmware-20170314.tar.xz._checksum_failure_.LUuct1'

!!! Couldn't download 'linux-firmware-20170314.tar.xz'. Aborting.
 * Fetch failed for 'sys-kernel/linux-firmware-20170314', Log file:
 *  '/var/tmp/portage/sys-kernel/linux-firmware-20170314/temp/build.log'

>>> Failed to emerge sys-kernel/linux-firmware-20170314, Log file:

>>>  '/var/tmp/portage/sys-kernel/linux-firmware-20170314/temp/build.log'

 * Messages for package sys-kernel/linux-firmware-20170314:

 * Fetch failed for 'sys-kernel/linux-firmware-20170314', Log file:
 *  '/var/tmp/portage/sys-kernel/linux-firmware-20170314/temp/build.log'


Thank you.
Back to top
View user's profile Send private message
skellr
l33t
l33t


Joined: 18 Jun 2005
Posts: 815
Location: The Village, Portmeirion

PostPosted: Mon Mar 19, 2018 7:47 pm    Post subject: Reply with quote

ONEEYEMAN wrote:
Hi,
OK, I pass baselayout, but now have a different issue:

Code:

gorDellGentoo /usr/local # emerge linux-firmware
Calculating dependencies... done!

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) sys-kernel/linux-firmware-20170314::gentoo
>>> Downloading 'http://distfiles.gentoo.org/distfiles/linux-firmware-20170314.tar.xz'
--2018-03-19 20:30:54--  http://distfiles.gentoo.org/distfiles/linux-firmware-20170314.tar.xz
Resolving distfiles.gentoo.org... 2600:3404:200:237::2, 2600:3402:200:227::2, 2605:bc80:3010::134, ...
Connecting to distfiles.gentoo.org|2600:3404:200:237::2|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2018-03-19 20:30:55 ERROR 404: Not Found.

>>> Downloading 'https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-e39f0e3e6897ad865b3704f61218ae83f98a85da.tar.xz'
--2018-03-19 20:30:55--  https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-e39f0e3e6897ad865b3704f61218ae83f98a85da.tar.xz
Resolving git.kernel.org... 2604:1380:4020:600::1, 147.75.58.133
Connecting to git.kernel.org|2604:1380:4020:600::1|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-e39f0e3e6897ad865b3704f61218ae83f98a85da.tar.xz [following]
--2018-03-19 20:30:55--  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-e39f0e3e6897ad865b3704f61218ae83f98a85da.tar.xz
Reusing existing connection to [git.kernel.org]:443.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://git.kernel.org//pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-e39f0e3e6897ad865b3704f61218ae83f98a85da.tar.gz [following]
--2018-03-19 20:30:55--  https://git.kernel.org//pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-e39f0e3e6897ad865b3704f61218ae83f98a85da.tar.gz
Reusing existing connection to [git.kernel.org]:443.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/x-gzip]
Saving to: '/usr/portage/distfiles/linux-firmware-20170314.tar.xz'

/usr/portage/distfi     [ <=>                ]  91.62M  3.26MB/s    in 42s     

2018-03-19 20:31:46 (2.18 MB/s) - '/usr/portage/distfiles/linux-firmware-20170314.tar.xz' saved [96072698]

!!! Fetched file: linux-firmware-20170314.tar.xz VERIFY FAILED!
!!! Reason: Filesize does not match recorded size
!!! Got:      96072698
!!! Expected: 43175092
Refetching... File renamed to '/usr/portage/distfiles/linux-firmware-20170314.tar.xz._checksum_failure_.LUuct1'

!!! Couldn't download 'linux-firmware-20170314.tar.xz'. Aborting.
 * Fetch failed for 'sys-kernel/linux-firmware-20170314', Log file:
 *  '/var/tmp/portage/sys-kernel/linux-firmware-20170314/temp/build.log'

>>> Failed to emerge sys-kernel/linux-firmware-20170314, Log file:

>>>  '/var/tmp/portage/sys-kernel/linux-firmware-20170314/temp/build.log'

 * Messages for package sys-kernel/linux-firmware-20170314:

 * Fetch failed for 'sys-kernel/linux-firmware-20170314', Log file:
 *  '/var/tmp/portage/sys-kernel/linux-firmware-20170314/temp/build.log'


Thank you.

I would emerge --sync
The Manifest I have for sys-kernel/linux-firmware-20170314 says the file size should be 96072698, which is the file size that was downloaded. For some reason the Manifest you have thinks it should be 43175092
Back to top
View user's profile Send private message
Tony0945
Advocate
Advocate


Joined: 25 Jul 2006
Posts: 2605
Location: Illinois, USA

PostPosted: Mon Mar 19, 2018 7:50 pm    Post subject: Reply with quote

skellr wrote:
I would emerge --sync
The Manifest I have for sys-kernel/linux-firmware-20170314 says the file size should be 96072698, which is the file size that was downloaded. For some reason the Manifest you have thinks it should be 43175092


IIRC, his last emerge --sync was a couple of years ago. It will be a project in itself.
Back to top
View user's profile Send private message
fedeliallalinea
Bodhisattva
Bodhisattva


Joined: 08 Mar 2003
Posts: 19619
Location: here

PostPosted: Mon Mar 19, 2018 7:51 pm    Post subject: Reply with quote

skellr wrote:
The Manifest I have for sys-kernel/linux-firmware-20170314 says the file size should be 96072698, which is the file size that was downloaded. For some reason the Manifest you have thinks it should be 43175092

And also want download an xz package instead of gz
linux-firmware-20170314.ebuild:
        SRC_URI="https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-${GIT_COMMIT}.tar.gz -> ${P}.tar.gz"

_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
skellr
l33t
l33t


Joined: 18 Jun 2005
Posts: 815
Location: The Village, Portmeirion

PostPosted: Mon Mar 19, 2018 7:55 pm    Post subject: Reply with quote

fedeliallalinea wrote:
skellr wrote:
The Manifest I have for sys-kernel/linux-firmware-20170314 says the file size should be 96072698, which is the file size that was downloaded. For some reason the Manifest you have thinks it should be 43175092

And also want download an xz package instead of gz
linux-firmware-20170314.ebuild:
        SRC_URI="https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-${GIT_COMMIT}.tar.gz -> ${P}.tar.gz"

Good eye.
https://gitweb.gentoo.org/repo/gentoo.git/commit/sys-kernel/linux-firmware/Manifest?id=6e154f3a3f382fac85d31f496563c67b89afdb67
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 12805

PostPosted: Tue Mar 20, 2018 1:56 am    Post subject: Reply with quote

Tony0945 wrote:
skellr wrote:
I would emerge --sync
The Manifest I have for sys-kernel/linux-firmware-20170314 says the file size should be 96072698, which is the file size that was downloaded. For some reason the Manifest you have thinks it should be 43175092
IIRC, his last emerge --sync was a couple of years ago. It will be a project in itself.
His earlier message says 112 days.
ONEEYEMAN wrote:
Code:
IgorDellGentoo /home/igor/dbhandler # emerge baselayout
 * Last emerge --sync was 112d 4h 51m 19s ago.
I started this response to remark on the oddity of having a 2017xxxx firmware in a two year old tree, but decided to keep the message after I tracked down the actual value. 112 days is still a bit on the long side, but it's not quite as painful.
Back to top
View user's profile Send private message
Tony0945
Advocate
Advocate


Joined: 25 Jul 2006
Posts: 2605
Location: Illinois, USA

PostPosted: Tue Mar 20, 2018 1:51 pm    Post subject: Reply with quote

Hu wrote:
His earlier message says 112 days.

I confused him with someone else. I'm following around five threads.

Yes, four months is doable. I would still look for a earlier snapshot. I see the Dec-01-2017 is available but only as squashfs. If his kernel doesn't support squashfs, there seems to be no choice but the snapshots from the last few days, so it might as well be the latest. I have an older snapshot on my system. I see I should probably set a cronjob to tar up /usr/portage once a month and once a quarter drop two.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Goto page Previous  1, 2
Page 2 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum