Re: upgrade to 2.2.1pre4 compile failure

Chuck Campbell (campbell@neosoft.com)
Fri, 19 Feb 1999 11:21:26 -0600


On Fri, Feb 19, 1999 at 10:07:37AM -0600, Chuck Campbell wrote:
> I can't seem to find any info about this, but I suspect it is an order
> related issue.
>
> I tried to upgrade from a new plain vanilla RH5.2 install plus redhat posted
> upgrades, to the new kernel 2.2.1pre4-ac6
^^^^^^^^^^^^^
oops, I meant 2.2.2pre4-ac6

>
> I applied the pre4 patch, then the ac-6 patch. The latter resulted in a
> number of REVERSED PATCH or PATCH ALREADY APPLIED messages. I looked at
> some of those, and I didn't see any problems so I went on (Maybe my first
> mistake).
>
> During the kernel build, I got the following:
>
> make[1]: Entering directory `/rh52_usr_alt/src/linux/mm'
> make all_targets
> make[2]: Entering directory `/rh52_usr_alt/src/linux/mm'
> gcc -D__KERNEL__ -I/rh52_usr_alt/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -pipe -fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=586 -c -o memory.o memory.c
> gcc -D__KERNEL__ -I/rh52_usr_alt/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -pipe -fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=586 -c -o mmap.o mmap.c
> gcc -D__KERNEL__ -I/rh52_usr_alt/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -pipe -fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=586 -c -o filemap.o filemap.c
> filemap.c: In function `generic_file_write':
> filemap.c:1523: warning: passing arg 3 makes pointer from integer without a cast
> filemap.c:1523: too few arguments to function
> make[2]: *** [filemap.o] Error 1
> make[2]: Leaving directory `/rh52_usr_alt/src/linux/mm'
> make[1]: *** [first_rule] Error 2
> make[1]: Leaving directory `/rh52_usr_alt/src/linux/mm'
> make: *** [_dir_mm] Error 2
>
> I suspect I needed to upgrade some things (I grabbed all of those items in
> DOCUMENTATION/CHANGES) before I started, but I wasn't sure WHEN to upgrade all
> of them.
>
> Will the old kernel (2.0.36) run with everything in the changes file upgraded,
> or do I upgrade some of them first, build the kernel and then upgrade the rest?
> If the latter, which are required BEFORE I build the kernel?
>
> I was trying to build everything here, and not use any binary rpm's.
>
> thanks,
> -chuck
>
> --
> ACCEL Services, Inc.| Specialists in Gravity, Magnetics | 1(713)993-0671 ph.
> 1980 Post Oak Blvd. | and Integrated Interpretation | 1(713)960-1157 fax
> Suite 2050 | |
> Houston, TX, 77056 | Chuck Campbell | campbell@neosoft.com
> | President & Senior Geoscientist |
>
> "Integration means more than having all the maps at the same scale!"

-- 
ACCEL Services, Inc.| Specialists in Gravity, Magnetics |  1(713)993-0671 ph.
1980 Post Oak Blvd. |   and Integrated Interpretation   |  1(713)960-1157 fax
    Suite 2050      |                                   |
 Houston, TX, 77056 |          Chuck Campbell           | campbell@neosoft.com
                    |  President & Senior Geoscientist  |

"Integration means more than having all the maps at the same scale!"

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/