First, the context : I am trying to install gentoo from a debian using the ia64-stage1.
Second, what was completed :
stage1: rsync complained about a missing library (libpopt.o) and then could not run. But I found a workaround, downloading the last portage snapshot with wget and uncompressing it to /usr/portage. Coooool
stage 2: coreutils compilation failed because of missing help2man (1 miss in coreutils deps ?). I emerged help2man, so that it could compile, and relaunched emerge system. Gooood
stage3: I am now confronted to a much bigger problem and cannot download the kernel. Here is the error I obtained :

# emerge -p sys-kernel/ia64-sources

These are the packages that I would merge, in order:

Calculating dependencies \
!!! all ebuilds that could satisfy "virtual/modutils" have been masked.
!!! (dependency required by "sys-kernel/ia64-sources-2.4.22" [ebuild])

!!! Error calculating dependencies. Please correct.
---------------------------
So, what to do ? I tried to add ACCEPT_KEYWORDS="~ia64" in make.conf, but that does not change anything. Do I have to add KEYWORDS="ia64" (or ~ia64) in modutils.ebuild ? Yes, that seems so, but I don't if it is really a good idea... and there is now a new iceberg named cset... I will have to try a few tricks.

I'm investigating the kernel issue and will put up another post about it soon.

I uploaded a stage1 with a fixed libpopt, by the way. It's datestamped 20031002. After emerge system you should be able to emerge sync - so if none of the module-init-tools ebuilds you have there have ia64 keywords (is the snapshot old?) you should be able to emerge sync again.

I tried to find the version of cset on the web: cset-1.1063.2.37-to-1.1088.txt.gz
And google gave me 2 answers, but I found it on none of them...
I can find often an empty cset--to-.txt.gz but do not know what to do with. Is there an tool for cset files auto-generation ?
Please Heeeeelp ?!?

I've modified the ebuild to instead use the latest diff against 2.4.22. Sync again in a half hour (and check the ChangeLog to make sure you have the right copy - I didn't bump the revision since if it worked for other people there's no reason to upgrade) and try it.

Well, thanks !
I re-did the install in a chroot from debian with the new stage1.
And that worked quite well. I've got a gentoo up and running, even if really minimalistic.

Now, I'd be glad if you could answer a few questions.
1-I first tried to compile the kernel with crypto support, but gcc complained about a missing file (must be include/asm/kmap_types.h), so I recompiled with crypto disabled. Then, I'd like to know if I may try copying the file from include/asm-i386 to include/asm-ia64, or if it is too 'hazardous' (?)...
2- A large number of ebuilds appear MASKED, due to lacking 'ia64' in the KEYWORDS list. Is it always safe to add it manually, or do I have to test for each package ? I do not have yet any cron or log daemon, and I also plan to emerge (and benefit of) X...

asm stuff is usually very processor-specific, so it probably wouldn't work.

Add keywords and compile - you'll probably want to stick it in an overlay directory - and if it works, feel free to file a bug assigned to ia64@gentoo.org asking for it to be unmasked on ia64 in the tree.

asm stuff is usually very processor-specific, so it probably wouldn't work.

Sure, but the concerned file is just a simple header file with simple declarations.
So, I will recompile and tell you if that works so easily...

[edit="result of the test"]
OK now we know how to recompile this kernel (2.4.22 from ia64-sources) with crypto support.
That was nothing harder than simply copy a missing file in the right include-dir.
Now, we can say that, copying <ksrcdir>/include/asm-i386/kmap_types.h in asm-ia64 allows us to (re-)compile our kernel with crypto support (but I did not test the new modules: they still may be buggy).
[/edit]
++

asm stuff is usually very processor-specific, so it probably wouldn't work.

Sure, but the concerned file is just a simple header file with simple declarations.
So, I will recompile and tell you if that works so easily...

[edit="result of the test"]
OK now we know how to recompile this kernel (2.4.22 from ia64-sources) with crypto support.
That was nothing harder than simply copy a missing file in the right include-dir.
Now, we can say that, copying <ksrcdir>/include/asm-i386/kmap_types.h in asm-ia64 allows us to (re-)compile our kernel with crypto support (but I did not test the new modules: they still may be buggy).
NB I found the same subject in the kernel mailing list...
[/edit]
++

Kudos, people. How is going the project? We are receiving three IA-64 that I suppose will come with Windows, and I was wondering if I could build Gentoo on them._________________"I'm just very selective about the reality I choose to accept." -- Calvin